# 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.