Pressing Items: What Needs My Attention Right Now
Ask "What's pressing?" and get a ranked triage of the last 12 hours across email, calendar, files, CRM and Linear.
The problem
Small fires hide across five tools. Escalations, overdue promises and people blocked on you get missed until it's too late.
Pressing Items: What Needs My Attention Right Now
Version 1.0.0 · Last updated 2026-10-22 · Difficulty: Beginner · Setup time: 15–30 minutes
🧩 Based on the prebuilt skill
Clone-Pressing-Items. You attach it; you don't have to write it.
Ask your clone "What's pressing?" and get a ranked triage of everything that needs you in the last 12 hours, as a Slack/Teams message and a branded HTML email.
1. Overview and value
Your inbox, calendar, files, CRM and Linear all produce small fires. Most are noise. A few are real: a customer who is losing patience, a deadline that passed, a colleague blocked on your approval. Finding them means checking five tools.
The Pressing Items skill does that sweep for you. It looks at exactly the last 12 hours (anchored to the real current time), across every source you've connected, and returns a short ranked list of what needs you now.
| Benefit | What it looks like |
|---|---|
| One sweep instead of five tabs | Email, calendar, files, CRM, Linear and knowledge bases checked together |
| Ranked, not dumped | A "Top Pressing Items" list ordered by severity, time pressure, blast radius and who's waiting |
| Honest | It never pads the list or invents urgency. Nothing pressing? It says "your plate is clear" |
| Two formats | A short Slack/Teams message plus a branded HTML email |
| Safe | It delivers only after you confirm the channel and recipients |
What it looks for:
| Class | Meaning |
|---|---|
| 🔴 Emergency | Outage, security, legal, or a customer-facing failure happening now |
| ⏰ Overdue | A promised or due date has passed |
| ⏳ Due Soon | A deadline or meeting coming up that needs something from you |
| 🙋 Frustrated/Escalating | Tone is getting sharper, repeated follow-ups, "any update?" |
| 🤝 Awaiting You | Others are blocked until you reply, approve or decide |
| 📨 Direct Ask | Someone asked you something directly and it's unanswered |
| 🔁 Dropped Thread | A conversation you were part of went quiet with an open item |
It also reads meeting-recap emails and pulls out action items assigned to you.
2. Who it's for
- Leadership who need a "what do I deal with first" view between meetings.
- Ops leads who field requests from many directions.
- Sales reps and managers watching deals, replies and follow-ups.
- Customer Success managers tracking escalations and promised follow-ups.
3. How it works
You: "What's pressing?" (or a scheduled run at 7 AM / 1 PM)
│
▼
┌────────────────────────────────────────────────────────────┐
│ Clone-Pressing-Items │
│ 1. Get the real current time ──► window = last 12 hours │
│ 2. Sweep sources (whatever is connected): │
│ Email (primary) · Calendar · Files · CRM · │
│ Linear · Knowledge bases · meeting-recap emails │
│ 3. Classify: 🔴 ⏰ ⏳ 🙋 🤝 📨 🔁 │
│ 4. Rank: severity · time pressure · blast radius · │
│ who's waiting │
│ 5. Draft: Slack/Teams message + branded HTML email │
│ 6. Show both in chat │
└──────────────────────────┬─────────────────────────────────┘
│
You confirm channel + recipients
│
▼
Delivered to Slack/Teams and/or email4. What the clone does (and never does)
Does
- Anchors to the real current time and reviews only the last 12 hours.
- Reports which sources were checked, which weren't connected, and which failed.
- Ranks items and says why each one is pressing.
- Shows both drafts in chat first.
Never
- Pads the list or invents urgency. A clear plate is a valid result.
- Sends anything before you confirm the channel and recipients.
- Replies to, edits or closes anything in your email, CRM, Linear or files. It is read-only.
- Reads Slack or Teams as a source (not supported yet; delivery only).
5. Setup walkthrough
The quickest path: give CLONE-INSTRUCTIONS.md to your clone and say "Please set this up. Show me a plan first."
- Check requirements (5 min): open REQUIREMENTS.md.
- Hand over the instructions (2 min).
- Review the discovery table (3 min).
- Attach the skill (2 min): the clone attaches Clone-Pressing-Items via the platform after you approve.
- Connect sources (5–15 min): email first, then calendar, files, CRM, Linear. You sign in (OAuth); the clone never needs a password.
- Run it: say "What's pressing?" Check the results.
- Optional schedule: for example 7 AM and 1 PM on weekdays. The prompt must state the delivery channel and email (exact text is in CLONE-INSTRUCTIONS.md).
6. Placeholders to decide
| Placeholder | What it means | Example |
|---|---|---|
{DELIVERY_CHANNEL} | Slack or Teams channel or DM for the message | #my-pressing-items (Slack) |
{EMAIL_RECIPIENTS} | Who gets the HTML email | you@yourcompany.com |
{SCHEDULE_TIMES} | When scheduled runs happen (with time zone) | 7:00 AM and 1:00 PM America/New_York, Mon–Fri |
{TIME_ZONE} | Your time zone | America/New_York |
7. What to expect
- On demand: a few minutes, then both drafts appear in chat with a source-status line.
- After you confirm channel and recipients, it delivers and tells you what was sent where.
- Busy day: a ranked list with the top items first. Quiet day: "Your plate is clear" plus the sources checked.
- Scheduled: arrives at the stated times in the stated destination.
8. Customizing
- Ask for fewer or more items in the Top list ("top 5 only").
- Ask it to ignore certain senders, labels or projects ("ignore newsletters and Linear project X").
- Change the email branding (name, colors, logo) by telling the clone.
- Run on different days or times by editing the scheduled task.
9. Known gotchas
- Email is the most important source. Connect it first. Without it, the sweep misses most direct asks, escalations and dropped threads.
- Slack/Teams can't be read as a source yet. They are delivery only. Messages sent to you there won't appear in the sweep.
- Scheduled runs need the destination in the prompt. A scheduled run can't ask you to confirm, so the prompt must name the channel and email recipients.
- 12 hours only, by design. Anything older is out of scope. For a broader view, use a different card (for example Customer Pulse for accounts).
- It only knows connected sources. The report tells you which were checked.
10. FAQ
Will it reply to people for me? No. It is read-only and only delivers the summary.
Can it look back 24 hours? Not in this card. The 12-hour window is deliberate so the list stays short and fresh.
Which CRM? Salesforce or HubSpot. HubSpot has no ticket operator, so support items appear as notes/tasks via HubspotEngagementOperator.
What if nothing is pressing? You get "your plate is clear" and the sources checked.
Does it need all sources? No. Email alone works; more sources make it better.
11. Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Very few items | Email not connected | Connect Gmail or Outlook first |
| Scheduled run didn't deliver | Destination missing in prompt | Edit the scheduled task and add channel and recipients |
| "CRM not connected" in status | Connection not signed in | Re-run sign-in for Salesforce or HubSpot |
| Items older than 12 hours | Window drift (rare) | Ask it to re-anchor to the current time and re-run |
| Nothing posted to Slack/Teams | Channel not confirmed or no access | Confirm the channel and check the messaging integration |
| Slack messages missing from the sweep | Slack/Teams aren't readable sources | Expected; forward key items to email |
Version: 1.0.0 · Last updated: 2026-10-22 · Part of the Clone Use Case Library.
Paste these instructions into clone chat
# Clone Instructions: Pressing Items (What Needs My Attention Right Now)
> **For the clone.** Your user has handed you this file. Follow it step by step.
> **Version 1.0.0 · Last updated 2026-10-22**
> 🧩 **Based on the prebuilt skill `Clone-Pressing-Items`.** You attach it; you don't have to write it.
---
## 1. Role and goal
You are setting up **Pressing Items** for your user. When done, the user can say **"What's pressing?"** and you will:
1. take the real current time and review exactly the **last 12 hours**,
2. sweep email (primary), calendar, files, CRM, Linear and knowledge bases,
3. classify and rank what needs the user,
4. show a Slack/Teams message and a branded HTML email in chat,
5. deliver only after the user confirms channel and recipients.
Your job now is **setup only**: discover, collect settings, show a plan, attach the prebuilt skill, optionally create a schedule, and test.
## 2. Safety rules
1. **Plan first.** Show a numbered plan and wait for an explicit "yes" before attaching, creating or changing anything.
2. **Never ask for, accept or handle passwords, API keys or tokens.** Connections are made by the user via sign-in (OAuth) screens. If a secret is pasted, tell the user to revoke it.
3. **Never email customers or prospects during setup.** Test emails go only to the user, after approval.
4. **Read-only.** Never reply to, send from, edit, archive or delete anything in email, calendar, files, CRM or Linear. The only outputs are the summary message and email to confirmed recipients.
5. **Don't guess names.** Use exact catalog names. Skill names can differ slightly between orgs; confirm them first.
6. **Never pad or invent urgency.**
## 3. Discovery
Use the `platform` tool to list attached skills, operators and connections. Use `describeOperator` on each relevant operator.
| Need | Required? | Look for |
|---|---|---|
| Prebuilt skill | Required | Clone-Pressing-Items |
| Email | Required (most important) | GoogleGmailOperator or Outlook email operator |
| Calendar | Recommended | GoogleCalendarOperator or Outlook calendar operator |
| Files | Optional | GoogleDriveCoreOperator or Microsoft_OneDrive |
| CRM | Optional | Salesforce operators (Account, Contact, Opportunity, Case, Activity) or HubSpot operators (Contact, Company, Deal, Engagement) |
| Linear | Optional | Linear_Operator |
| Knowledge bases | Optional | search_knowledge |
| Slack/Teams delivery | Required for message | Messaging integration |
| Scheduled tasks | Optional | platform |
Report:
| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| Clone-Pressing-Items | ✅ ⚠️ ❌ ❓ | … | … |
| Email | … | … | … |
| Calendar | … | … | … |
| Files | … | … | … |
| CRM | … | … | … |
| Linear | … | … | … |
| Knowledge bases | … | … | … |
| Slack/Teams delivery | … | … | … |
Mark anything you can't check "❓ Couldn't check" and say why. If the user asks for an unsupported tool, say it isn't supported and move on. Remind them Slack/Teams are delivery only, not a source.
## 4. Collect placeholders
Ask once:
> 1. **Delivery channel** (`{DELIVERY_CHANNEL}`): which Slack or Teams channel or DM?
> 2. **Email recipients** (`{EMAIL_RECIPIENTS}`): who gets the HTML email? *(default: you)*
> 3. **Schedule** (`{SCHEDULE_TIMES}`): none, or e.g. 7:00 AM and 1:00 PM weekdays?
> 4. **Time zone** (`{TIME_ZONE}`).
Repeat the answers in a table and ask the user to confirm.
## 5. What you can do yourself (after approval)
> **Proposed plan (nothing changes until you say yes):**
> 1. Attach **Clone-Pressing-Items** (and any missing operators) via the platform.
> 2. Run "What's pressing?" once and show both drafts in chat.
> 3. After you confirm channel and recipients, deliver the test.
> 4. (Optional) Create a scheduled task at `{SCHEDULE_TIMES}` with the prompt below.
>
> **You'll need to:** sign in to the connections listed in section 6.
>
> Reply **yes** to proceed.
After a clear "yes":
1. **Attach the skill** with the platform tool: search the catalog for **Clone-Pressing-Items**, attach it, confirm with `describeOperator`. If it can't be attached by you, tell the user: settings → Skills → find **Clone-Pressing-Items** → Add/Enable → tell me "attached".
2. **Attach missing operators** the user approved.
3. **Create the schedule (optional)** with the platform tool. The destination must be inside the prompt, because a scheduled run can't ask for confirmation.
**Scheduled-task prompt (paste exactly, fill in the braces):**
```
Run Clone-Pressing-Items now. Review exactly the last 12 hours from the current time in {TIME_ZONE} across email, calendar, files, CRM, Linear and knowledge bases, including action items from meeting-recap emails. Rank the Top Pressing Items. The destination is already confirmed: post the short message to {DELIVERY_CHANNEL} and email the branded HTML version to {EMAIL_RECIPIENTS}. Do not ask for confirmation. If nothing is pressing, send "Your plate is clear" with the sources checked. Do not invent urgency. Include a source status line (checked, not connected, failed).
```
Schedule: `{SCHEDULE_TIMES}`, for example 7:00 AM and 1:00 PM, Mon–Fri.
**Optional customization lines** (append to the prompt if the user wants): "Show only the top 5 items." / "Ignore newsletters and automated notifications." / "Skip Linear." / "Use our brand color {BRAND_COLOR} in the email."
## 6. What the user must do
1. **Connect email first** (Gmail or Outlook): settings → Connections → choose the provider → sign in → approve read and send. This is the most important source.
2. **Connect calendar, then files** (Google Drive or OneDrive): same path.
3. **Connect CRM** (Salesforce or HubSpot) with read access, and **Linear** with read access.
4. **Allow Slack or Teams posting** to `{DELIVERY_CHANNEL}` (invite the clone or approve the integration).
5. Tell me "done" when each is finished. I never need your password.
## 7. What the prebuilt skill does (Clone-Pressing-Items)
You don't write this skill. For your understanding, it works like this:
1. **Anchors time.** Gets the real current time and sets the window to exactly the last 12 hours. Nothing older.
2. **Sweeps sources** (those connected): email (primary signal), calendar (upcoming and missed meetings), files (Drive/OneDrive comments and shares), CRM (Salesforce or HubSpot deals, cases/engagements, tasks), Linear (assigned, blocked), and `search_knowledge`. It also finds meeting-recap emails and extracts action items for the user.
3. **Classifies** each item: 🔴 Emergency, ⏰ Overdue, ⏳ Due Soon, 🙋 Frustrated/Escalating, 🤝 Awaiting You (blocking others), 📨 Direct Ask, 🔁 Dropped Thread.
4. **Ranks** by severity, time pressure, blast radius and who's waiting.
5. **Drafts** a Slack/Teams message and a branded HTML email and shows both in chat.
6. **Waits** for the user to confirm channel and recipients (unless the scheduled prompt already states them), then delivers.
7. **Empty state:** "Your plate is clear", with the sources checked. Never pads.
8. **Failure handling:** retry a failed call once, then mark the source unavailable and report it.
## 8. Test plan
Use safe data: your own mailbox and a private test channel or DM. Don't email anyone else.
| ☐ | Check | Expected |
|---|---|---|
| ☐ | "What's pressing?" runs | Window stated as the last 12 hours from now |
| ☐ | Source status line | Lists checked, not connected, failed |
| ☐ | Items are real | Each links to a real email, event, record or issue |
| ☐ | Ranking | Highest severity and most blocking first |
| ☐ | Both drafts shown | Slack/Teams message and HTML email |
| ☐ | No send before confirm | Nothing delivered until you confirm |
| ☐ | Delivery | Arrives in the chosen channel and inbox |
| ☐ | Empty state | On a quiet window, "your plate is clear" |
| ☐ | Scheduled run (if set) | Delivers with no prompt for confirmation |
## 9. Final status checklist
**✅ Done by me:** *(list: skill attached, operators attached, schedule created, test run)*
**⏳ Waiting on you:** *(sign-ins, channel access, confirmation of the first delivery)*
**💡 Optional next steps:** add a second daily run, tune ignore rules, add brand colors, try Customer Pulse for account-level activity.
Requirements
Requirements: Pressing Items
Version 1.0.0 · Last updated 2026-10-22 · Estimated setup time: 15–30 minutes
🧩 Based on the prebuilt skill
Clone-Pressing-Items. You attach it; you don't have to write it.
1. Required skills / operators
| # | Skill / operator (exact name) | What it's used for | Required? |
|---|---|---|---|
| 1 | Clone-Pressing-Items (prebuilt skill) | The 12-hour triage sweep and drafts | Required |
| 2 | GoogleGmailOperator or the Outlook email operator | Primary signal: asks, escalations, dropped threads, meeting-recap action items; sends the HTML email | Required (strongly) |
| 3 | GoogleCalendarOperator or the Outlook calendar operator | Upcoming and just-missed meetings | Recommended |
| 4 | GoogleDriveCoreOperator or Microsoft_OneDrive | Recently shared or commented files | Optional |
| 5 | Salesforce operators or HubSpot operators | Deals, cases, activities needing attention | Optional |
| 6 | Linear_Operator | Issues assigned to or blocked on you | Optional |
| 7 | search_knowledge | Knowledge base notes | Optional |
| 8 | platform | Attach the skill, create scheduled tasks | Required |
Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.
2. Connections and minimum permissions
| Connection | Minimum permission | Why |
|---|---|---|
| Read + Send | Read the last 12 hours; send the briefing to confirmed recipients | |
| Calendar | Read | Upcoming meetings and recent invites |
| Drive / OneDrive | View | Recent files and comments |
| Salesforce or HubSpot | Read | Deals, cases/engagements, activities |
| Linear | Read | Assigned and blocked issues |
| Slack or Teams messaging | Post to the chosen channel or DM | Delivery |
All connections are made by you through sign-in (OAuth). Your clone never needs your password.
3. Optional add-ons
| Add-on | Adds |
|---|---|
| Calendar | "Due Soon" meeting prep needs |
| Files | Review requests and comments awaiting you |
| CRM | Stalled deals, new cases, overdue tasks |
| Linear | Blocked issues and review requests |
| Knowledge bases | Related notes and commitments |
Salesforce to HubSpot mapping
| Concept | Salesforce | HubSpot |
|---|---|---|
| Deal | Opportunity (SalesforceOpportunityOperator) | Deal (HubspotDealOperator) |
| Support item | Case (SalesforceCaseOperator) | Notes/tasks via HubspotEngagementOperator (no ticket operator) |
| Activity/task | SalesforceActivityOperator | HubspotEngagementOperator |
| Account | SalesforceAccountOperator | HubspotCompanyOperator |
4. Data prerequisites
- Email is connected for the mailbox you want triaged.
- You know the Slack or Teams channel (or DM) for delivery.
- You know who should receive the HTML email (usually just you).
- CRM and Linear connections (if used) are signed in with read access.
5. Roles and permissions
| Who | Needs to |
|---|---|
| Clone admin | Attach the skill, approve the plan, create the scheduled task |
| Connection owner (you) | Sign in to email, calendar, files, CRM, Linear |
| Slack/Teams admin | Allow the clone to post to the channel, if restricted |
6. Estimated setup time
| Step | Time |
|---|---|
| Pre-flight | 5 min |
| Discovery and plan | 5 min |
| Sign-ins | 5–15 min |
| First run and check | 5 min |
| Optional schedule | 5 min |
| Total | 15–30 min |
7. Pre-flight checklist
- I'm the clone admin (or have one)
- Clone-Pressing-Items is in my skill catalog
- I can sign in to my email (Gmail or Outlook)
- (Optional) I can sign in to calendar, Drive/OneDrive, Salesforce or HubSpot, Linear
- I know my
{DELIVERY_CHANNEL}and{EMAIL_RECIPIENTS} - (Optional) I've picked
{SCHEDULE_TIMES}and{TIME_ZONE}
8. You're ready when…
- ✅ Clone-Pressing-Items is attached.
- ✅ Email is connected (the most important source).
- ✅ You've run "What's pressing?" and seen both drafts in chat.
- ✅ You confirmed a channel and recipients and the delivery arrived.
- ✅ (Optional) The scheduled task prompt names the channel and email.
Then download CLONE-INSTRUCTIONS.md and give it to your clone.
Was this use case helpful?
Thanks!