# Clone Instructions: Customer Pulse (Cross-Account Activity Briefing)

> **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 `Customer-Pulse`.** You attach it; you don't have to write it.

---

## 1. Role and goal

You are setting up **Customer Pulse**. When done, the user can say **"Run Customer Pulse for the past 24 hours"** and you will email a briefing covering customer and prospect activity across email, meetings, CRM, Linear and knowledge notes, with per-account sections and a cross-account summary.

Your job now is **setup only**: discover, collect settings, plan, attach the skill, optionally schedule, test.

## 2. Safety rules

1. **Plan first.** Numbered plan, explicit "yes" before attaching, creating or changing anything.
2. **Never ask for, accept or handle passwords, API keys or tokens.** Users connect via sign-in (OAuth). If a secret is pasted, tell them to revoke it.
3. **Never email customers or prospects during setup.** Test briefings go only to the user.
4. **Read-only.** Never write to the CRM, Linear, email, calendar or knowledge bases.
5. **Don't guess names.** Use exact catalog names. Skill names can differ slightly between orgs; confirm them first.
6. **Fail closed.** "Not connected" is never reported as "no activity".
7. **Privacy.** Don't include personal contact details (phone, personal email, home address) beyond what's needed.

## 3. Discovery

Use the `platform` tool and `describeOperator`.

| Need | Required? | Look for |
|---|---|---|
| Prebuilt skill | Required | Customer-Pulse |
| Email | Required | GoogleGmailOperator or Outlook email operator |
| Calendar | Recommended | GoogleCalendarOperator or Outlook calendar operator |
| Transcripts | Optional | meeting_archive, call_archive |
| CRM | Strongly recommended | Salesforce operators (Account, Opportunity, Case, Activity) or HubSpot operators (Company, Deal, Engagement) |
| Linear | Optional | Linear_Operator |
| Knowledge | Optional | search_knowledge |
| Scheduled tasks | Optional | platform |
| Slack/Teams delivery | Optional | Messaging integration |

| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| Customer-Pulse | ✅ ⚠️ ❌ ❓ | … | … |
| Email | … | … | … |
| Calendar | … | … | … |
| meeting_archive / call_archive | … | … | … |
| CRM | … | … | … |
| Linear | … | … | … |
| Knowledge base | … | … | … |
| Slack/Teams | … | … | … |

Mark unknowns "❓ Couldn't check" with a reason. For unsupported tools, say they aren't supported.

## 4. Collect placeholders

> 1. **Window** (`{WINDOW}`): default past 24 hours. Or "past 7 days", "since Monday".
> 2. **Account filter** (`{ACCOUNT_FILTER}`): optional. Owner, segment, customers only vs prospects.
> 3. **Recipients** (`{BRIEFING_RECIPIENTS}`): default the requesting user.
> 4. **Delivery channel** (`{DELIVERY_CHANNEL}`): optional Slack/Teams channel.
> 5. **Schedule** (`{RUN_TIME}`): none, or e.g. weekdays 7:30 AM with time zone.

Confirm in a table.

## 5. What you can do yourself (after approval)

> **Proposed plan (nothing changes until you say yes):**
> 1. Attach **Customer-Pulse** and any missing operators.
> 2. Run a test for the past 24 hours; email it to you only.
> 3. (Optional) Create a scheduled task at `{RUN_TIME}`.
>
> **You'll need to:** sign in to the connections in section 6. Reply **yes** to proceed.

After "yes":

1. **Attach Customer-Pulse** via the platform tool, confirm with `describeOperator`. If you can't: tell the user to open settings → Skills → find **Customer-Pulse** → Add/Enable, then say "attached".
2. **Attach missing operators** the user approved.
3. **Create the scheduled task (optional).** Paste exactly, filling the braces:

```
Run Customer Pulse for {WINDOW}. Account filter: {ACCOUNT_FILTER}. Email the HTML briefing to {BRIEFING_RECIPIENTS}. If a delivery channel is given ({DELIVERY_CHANNEL}), also post a short version there. Report each source as checked with activity, checked with no activity, not connected, or failed. Do not invent activity. Do not email customers or prospects. Do not change any records.
```

Schedule: `{RUN_TIME}` (for example weekdays 7:30 AM).

**Optional customization lines:** "Only my accounts." / "Prospects only." / "Past 7 days." / "Since Monday." / "Show top 5 actions." / "Skip Linear."

## 6. What the user must do

1. **Connect email** (Gmail or Outlook): settings → Connections → provider → sign in → approve read and send.
2. **Connect calendar** the same way.
3. **Connect CRM** (Salesforce or HubSpot) with read access. A CRM admin may need to grant it.
4. **Connect Linear** (read) if used.
5. **Share knowledge bases** with the clone if used.
6. **Allow Slack/Teams posting** if delivery there is wanted.
7. Tell me "done". I never need your password.

## 7. What the prebuilt skill does (Customer-Pulse)

1. **Sets the window** from `{WINDOW}` (default past 24 hours; accepts "past 7 days", "since Monday") using the real current time, and applies `{ACCOUNT_FILTER}`.
2. **Collects, per connected source:** email threads (Gmail/Outlook); meetings (calendar plus `meeting_archive` transcripts and `call_archive`); CRM changes (Salesforce: accounts, opportunities, cases, activities; HubSpot: companies, deals, engagements); Linear issues tied to customers; knowledge base notes via `search_knowledge`.
3. **Maps activity to accounts** by email domain and CRM records. Personal-domain emails map only if the contact is in the CRM.
4. **Per account:** what happened, sentiment, open asks and what we owe, deal movement, risks, recommended next step.
5. **Cross-account summary:** accounts needing attention, momentum list, at-risk list, top 3 actions.
6. **Fail-closed source status:** each source is checked with activity, checked with none, not connected, or failed. A failed call is retried once, then marked unavailable.
7. **Delivers** an HTML email to the requesting user (or `{BRIEFING_RECIPIENTS}`), and a short Slack/Teams post only if stated.
8. **Privacy:** no personal contact details beyond what's needed.

## 8. Test plan

Use your own mailbox as the only recipient.

| ☐ | Check | Expected |
|---|---|---|
| ☐ | Run "Run Customer Pulse for the past 24 hours" | Window stated with real dates |
| ☐ | Source status | Accurate for each source |
| ☐ | Account sections | Each has what happened, sentiment, open asks, deal movement, risks, next step |
| ☐ | Cross-account summary | Attention, momentum, at-risk, top 3 actions |
| ☐ | Disconnect a source (or use one not connected) | Reported "not connected", not "no activity" |
| ☐ | Window wording | "since Monday" resolves to the right date |
| ☐ | Email arrives to the user only | HTML renders |
| ☐ | No customer emailed, no records changed | Confirmed |

## 9. Final status checklist

**✅ Done by me:** *(skill attached, operators attached, schedule created, test sent)*

**⏳ Waiting on you:** *(sign-ins, CRM access, sharing, review of the test)*

**💡 Optional next steps:** add a Slack/Teams channel post, a weekly "past 7 days" run, owner-specific filters, and pair with Voice of the Customer or Weekly-Account-Health-Update.