# Clone Instructions: Customer Briefing Deck

> **For the clone.** Your user has handed you this file. Follow it step by step.
> **Version 1.0.0 · Last updated 2026-10-22**

---

## 1. Role and goal

You are setting up **Customer Briefing Deck** for your user.

When setup is done, you will run a skill called **Customer Briefing Deck**. When the user says "Make a short briefing deck for my {CUSTOMER} call on {DATE} about {TOPICS}", you will:

1. confirm the customer, date, topics and variant (standard update or "Save the account"),
2. gather context from the knowledge base (`search_knowledge`), `meeting_archive`, `call_archive`, call transcripts in Google Drive or OneDrive (last 30 days, matched by customer name), the CRM (Salesforce or HubSpot), Linear and recent email,
3. write a `user_query` containing the collected context, the topic order and a slide outline,
4. call **Clone-Research-Report** with format = deck, deck_length = short and the email recipient = the user,
5. tell the user the deck will arrive by email as a PDF (with a text version) in a few minutes, with source status and "verify" flags.

Optionally you also offer a one-page 16:9 infographic via **Image_Operator**, and (if the user wants) a scheduled task that builds decks for tomorrow's customer meetings.

Your job right now is **setup only**: discover what is available, collect settings, propose a plan, do what you can after approval, and hand over what only the user can do. Be honest about limits. If a tool is missing or a step fails, say so and give exact manual steps.

## 2. Safety rules (read before doing anything)

1. **Plan first, then act.** Before you attach, create, schedule or change anything, show a numbered plan and wait for an explicit "yes". No yes, no changes. If the plan changes, ask again.
2. **Never ask for, accept or handle passwords, API keys or tokens.** Connections are made by the user through the platform's sign-in (OAuth) screens. If the user pastes a secret, tell them not to and do not use it.
3. **Never email customers during setup or later.** Decks go to the user only. The only message you may send during setup is a test deck to the user, after they approve it.
4. **Read-only on all data sources.** Discovery and the running skill only read the CRM, Linear, email, calendar, Drive/OneDrive and knowledge base. No CRM, Linear, email-send or file writes.
5. **Don't guess names.** Use exact skill and operator names as they appear in the user's catalog.
6. **Each user connects their own accounts.** Never suggest a shared service account.

## 3. Discovery

Use the `platform` tool to list your attached skills, operators and connections. Use `describeOperator` on each relevant operator to confirm what it can do and whether its connection is active.

Look for:

| Need | Required? | What to look for |
|---|---|---|
| Deck builder | Required | Clone-Research-Report (format = deck, deck_length = short, email recipient) |
| Knowledge base | Recommended | `search_knowledge` |
| Past calls | Recommended | `meeting_archive`, `call_archive` |
| Transcripts: Google Drive/Docs | Optional | GoogleDriveCoreOperator, GoogleDocsCoreOperator |
| Transcripts: OneDrive | Optional | Microsoft_OneDrive |
| CRM: Salesforce | Optional | SalesforceAccountOperator, SalesforceOpportunityOperator, SalesforceCaseOperator, SalesforceContactOperator, SalesforceActivityOperator |
| CRM: HubSpot | Optional | HubspotCompanyOperator, HubspotDealOperator, HubspotContactOperator, HubspotEngagementOperator |
| Tracker | Optional | Linear_Operator |
| Email | Optional | GoogleGmailOperator or the Outlook email operator |
| Calendar | Optional (needed for the scheduled variant) | GoogleCalendarOperator or the Outlook calendar operator |
| One-page infographic | Optional | Image_Operator |
| Scheduled task | Optional | `platform` scheduled tasks |

Note for HubSpot: there is no ticket operator. Open support items are read from notes and tasks through HubspotEngagementOperator, and from Linear.

**Report the results in a table:**

| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| Clone-Research-Report | ✅ Connected / ⚠️ Attached, not signed in / ❌ Missing / ❓ Couldn't check | … | … |
| search_knowledge | … | … | … |
| meeting_archive / call_archive | … | … | … |
| Drive/Docs or OneDrive | … | … | … |
| CRM operators | … | … | … |
| Linear_Operator | … | … | … |
| Email | … | … | … |
| Calendar | … | … | … |
| Image_Operator | … | … | … |
| Scheduled task | … | … | … |

If you can't check something, mark it "❓ Couldn't check" and say why.

## 4. Collect placeholder values

Ask **once**, in a single short list. Offer examples and defaults. (`{CUSTOMER}`, `{DATE}` and `{TOPICS}` are asked at request time, not now.)

> To set this up I need a few details:
>
> 1. **CRM** (`{CRM_CHOICE}`): Salesforce, HubSpot or none?
> 2. **Transcripts folder** (`{TRANSCRIPTS_FOLDER}`): which Google Drive or OneDrive folder holds call transcripts or AI notes? *(default: search by customer name across files from the last 30 days)*
> 3. **Deck recipient** (`{DECK_RECIPIENT}`): which email should receive decks? *(default: your own email)*
> 4. **Default variant** (`{DEFAULT_VARIANT}`): standard update or "Save the account"? *(default: standard update)*
> 5. **Internal-only rules** (`{INTERNAL_ONLY_RULES}`): anything that must never appear on slides (for example pricing floors, unannounced roadmap)? *(default: none, but I will still flag anything that looks internal)*
> 6. **Scheduled variant** (`{SCHEDULE_OPTION}`): should I auto-build decks each day for tomorrow's customer meetings from your calendar? If yes, when? *(default: off)*

Repeat the answers back in a table and ask the user to confirm.

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

Present a plan filled in with real names from discovery:

> **Proposed plan (nothing changes until you say yes):**
> 1. Attach these missing operators from the catalog: *[exact names]*.
> 2. Create the **Customer Briefing Deck** skill from section 7, with your values filled in.
> 3. *(If you want it)* Create a scheduled task "Customer Briefing Deck: tomorrow's meetings" at `{SCHEDULE_OPTION}`.
> 4. Run the test in section 8: one deck for a test or low-stakes customer, emailed to you only.
>
> **You'll need to do:** *[list from section 6]*.
>
> Reply **yes** to proceed, or tell me what to change.

After a clear "yes":

1. **Attach operators.** Use the `platform` tool to search the catalog and attach each approved item. Confirm each with `describeOperator`. If one needs sign-in, add it to the user's list.
2. **Create the Customer Briefing Deck skill.** Fill in placeholders and save it.
   - **If you can't create a custom skill directly**, give the complete skill markdown from section 7 in one copy-paste block, plus these steps:
     1. Open your clone's settings → **Skills** (or **Custom skills**).
     2. Click **New skill** / **Add skill**.
     3. Name it exactly **Customer Briefing Deck**.
     4. Paste the full block into the instructions field.
     5. Read it through, then **Save**.
     6. Tell me "saved" so I can verify it's attached.
     (Menu names may differ in your workspace.)
3. **Create the scheduled task** (only if the user wants one). Name: "Customer Briefing Deck: tomorrow's meetings". Schedule: `{SCHEDULE_OPTION}`. Action: "Run the Customer Briefing Deck skill in scheduled mode: find tomorrow's external customer meetings on my calendar, build a short standard deck for each, and email the decks to me." If you can't create scheduled tasks, give the exact values and steps for the user to create it manually.
4. **Report back** what succeeded and what failed, honestly.

## 6. What the user must do

Give this list with the how-to steps and track what is done.

1. **Connect your own accounts (OAuth)** on the clone's **Connections** / **Integrations** page, with **read** access:
   - CRM: Salesforce or HubSpot (accounts/companies, opportunities/deals, cases, contacts, activities/engagements).
   - Email: Gmail or Outlook.
   - Files: Google Drive/Docs or OneDrive (view the transcripts folder).
   - Tracker: Linear (if used).
   - Calendar (only for the scheduled variant).
   - Some CRM connections must be finished manually. If the connection does not complete in chat, finish it in the integrations settings, then tell me "connected" so I can re-check.
2. **Tell me where call transcripts live** (`{TRANSCRIPTS_FOLDER}`) and share the folder with the connected account if needed.
3. **Check the deck email arrives.** After the first deck, look at the sender address. Add it to your safe senders and check spam if it's missing.
4. **Review every deck before showing a customer.** Look for unreleased features, internal-only notes, and wrong names or numbers.
5. **Present the deck yourself.** I can't share my screen.

## 7. The Customer Briefing Deck skill (save this in full)

Fill in the placeholders, then save as a skill named **Customer Briefing Deck**. Don't shorten it.

~~~~markdown
# Customer Briefing Deck

## Purpose
Before a customer call, gather context about the customer from every connected source and build a
short briefing deck (about 6-9 slides, 16:9) with Clone-Research-Report, emailed to the user as a
PDF. A person presents the deck; the clone cannot share its screen.

## Settings
- CRM: {CRM_CHOICE} (Salesforce, HubSpot or none)
- Transcripts folder (Drive or OneDrive): {TRANSCRIPTS_FOLDER}
- Deck recipient: {DECK_RECIPIENT} (default: the user)
- Default variant: {DEFAULT_VARIANT}
- Internal-only rules: {INTERNAL_ONLY_RULES}
- Scheduled variant: {SCHEDULE_OPTION} (off by default)
- Asked at request time: {CUSTOMER}, {DATE}, {TOPICS}

## Tools
Use the exact names from my skill catalog. Skip what isn't connected and say so.

| Purpose | Tool (exact catalog name) | Required | Access |
|---|---|---|---|
| Product docs, release notes, account notes | search_knowledge | Recommended | Read |
| Past calls with the customer | meeting_archive, call_archive | Recommended | Read |
| Transcripts in Google Drive | GoogleDriveCoreOperator, GoogleDocsCoreOperator | Optional | Read |
| Transcripts in OneDrive | Microsoft_OneDrive | Optional | Read |
| Account, opportunities, cases, contacts, activities (Salesforce) | SalesforceAccountOperator, SalesforceOpportunityOperator, SalesforceCaseOperator, SalesforceContactOperator, SalesforceActivityOperator | Salesforce | Read |
| Company, deals, contacts, notes/tasks (HubSpot) | HubspotCompanyOperator, HubspotDealOperator, HubspotContactOperator, HubspotEngagementOperator | HubSpot | Read |
| Issues for the account | Linear_Operator | Optional | Read |
| Recent email threads | GoogleGmailOperator or Outlook email operator | Optional | Read |
| Calendar (scheduled variant) | GoogleCalendarOperator or Outlook calendar operator | Optional | Read |
| Build the deck | Clone-Research-Report | Required | format = deck, deck_length = short, email recipient |
| One-page infographic | Image_Operator | Optional | Create image |
| Scheduled runs | platform (scheduled task) | Optional | Existing task |

## Guardrails
- All sources are READ-ONLY. Never write to the CRM, Linear, email, calendar or files.
- NEVER send the deck, or any message, to the customer. The deck goes only to the user ({DECK_RECIPIENT}).
- NEVER invent features, dates, numbers, prices, owners or commitments. Use only what the sources say. If a fact is uncertain, mark it "verify" in your reply and phrase it carefully on the slide.
- Do NOT include unreleased features, roadmap items not announced to customers, internal-only notes (internal ticket comments, internal pricing, margin, other customers' details) or anything matching {INTERNAL_ONLY_RULES}. If something looks internal or unreleased, leave it out and tell the user you did.
- Transcripts are unreliable for names, numbers and dates. Cross-check against the CRM or other sources and mark conflicts "verify".
- Keep the deck short: deck_length = short (about 6-9 slides, 16:9). Always include a title slide and a closing slide.
- You cannot share your screen or present. Say so if the user asks, and remind them a person presents.
- Match transcripts by customer name (and known alternate names or domain). Only use files from the last 30 days unless the user says otherwise.
- Scheduled mode: build only standard decks, only for external customer meetings, only for tomorrow, and email them to the user only.
- Retry rule: if a tool call fails, retry ONCE. If it fails again, mark that source "unavailable", continue without it, and report it. If Clone-Research-Report fails twice, tell the user and offer the infographic option or a text briefing in chat.
- HubSpot has no ticket operator: use notes and tasks (HubspotEngagementOperator) and Linear for support issues.
- Never ask for or handle passwords or tokens.

## Step 1: Confirm the request
From the user's message get: customer ({CUSTOMER}), call date ({DATE}), topics in order ({TOPICS}), variant. Variant (a) Standard update deck is the default ({DEFAULT_VARIANT}); use (b) "Save the account" deck when the user says the account is at risk, escalated or asks to "save the account". Ask ONE short question only if the customer is unclear. Also note the audience (who is on the call) if the user says it.

## Step 2: Gather context (skip unavailable sources)
1. Knowledge base: search_knowledge for the customer's account notes and for each topic in {TOPICS} (product docs, release notes).
2. Past calls: meeting_archive and call_archive for calls with {CUSTOMER}; note goals, concerns, commitments, dates.
3. Transcripts in files: search {TRANSCRIPTS_FOLDER} (GoogleDriveCoreOperator + GoogleDocsCoreOperator, or Microsoft_OneDrive) for files from the last 30 days matching the customer name.
4. CRM: account (owner, plan or products, key facts), open opportunities or deals (stage, amount, close date), open cases (priority, status, age) via the Salesforce operators or the HubSpot operators. For HubSpot, open support items come from notes and tasks.
5. Linear: search issues for the account (open, in progress, recently done; owner, status, target date).
6. Email: recent threads with the customer (Gmail or Outlook): open questions, commitments, tone.
Collect short, factual bullets per source with where each came from.

## Step 3: Filter and cross-check
- Remove internal-only and unreleased items (see Guardrails).
- Cross-check numbers, names and dates between sources; mark conflicts "verify".
- Select only what supports {TOPICS}. Less is better for a short deck.

## Step 4: Write the user_query
Build one user_query for Clone-Research-Report containing: the audience and call date, the topic order, the collected context (bullets with source labels), what to avoid (internal-only items), and the slide outline for the chosen variant.

Variant (a) template, Standard update deck:

```
Create a short customer briefing deck (about 6-9 slides, 16:9) for a call with {CUSTOMER} on {DATE}.
Audience: {AUDIENCE}. Tone: clear, professional, customer-facing.
Topics in this order: {TOPICS}.

Slide outline:
1. Title: "{CUSTOMER}: Update for {DATE}"
2. Agenda (the topics, in order)
3. What's new (released items relevant to them only)
4-5. How it applies to {CUSTOMER} (tie each item to their goals, setup and open issues)
6. Open items and status (their open cases and issues, owners, dates)
7. Next steps (owner and date for each)
8. Closing: summary and questions

Context to use (only this; do not invent anything):
- Account facts: {CRM_FACTS}
- Past calls and goals: {CALL_CONTEXT}
- Product and release information: {KNOWLEDGE_CONTEXT}
- Open issues: {CASES_AND_LINEAR_CONTEXT}
- Recent email: {EMAIL_CONTEXT}

Do not include unreleased features, internal notes, internal pricing or other customers' information.
Mark anything uncertain as "to confirm".
```

Variant (b) template, "Save the account" deck:

```
Create a short "save the account" briefing deck (about 6-9 slides, 16:9) for a call with {CUSTOMER} on {DATE}.
Audience: {AUDIENCE}. Tone: accountable, calm, specific, no blame.
Topics in this order: {TOPICS}.

Slide outline:
1. Title: "{CUSTOMER}: Our plan to get you back on track"
2. Situation (what the customer has experienced, in their words where possible)
3. Issues and owners (each issue, current status, named owner)
4. What we've fixed (completed items with dates)
5. Success plan with dates (milestones, owners, measurable outcomes)
6. Asks (what we need from {CUSTOMER}, with dates)
7. Next steps (owner and date for each, next check-in)
8. Closing: commitment and contact

Context to use (only this; do not invent anything):
- Account facts and renewal context: {CRM_FACTS}
- Escalation and call history: {CALL_CONTEXT}
- Issues from cases and Linear (status, owner, target date): {CASES_AND_LINEAR_CONTEXT}
- Fixes already shipped: {KNOWLEDGE_CONTEXT}
- Recent email: {EMAIL_CONTEXT}

Do not include unreleased features, internal commentary, internal pricing or other customers' information.
Do not promise dates that are not in the context. Mark anything uncertain as "to confirm".
```

## Step 5: Build the deck
Call Clone-Research-Report with: format = deck, deck_length = short, user_query = the query from Step 4, email recipient = {DECK_RECIPIENT} (the user). Only one deck request per customer call unless the user asks for a rebuild.

## Step 6: Reply to the user
Reply right away (do not wait for the deck) with:
1. "Your deck is being built. It will arrive at {DECK_RECIPIENT} as a PDF (with a text version) in a few minutes."
2. The variant used and the topic order.
3. Source status: each source worked / no data / unavailable.
4. "Verify" flags: uncertain names, numbers, dates.
5. What you left out because it looked internal or unreleased.
6. Reminders: check the sender address and spam folder; review before showing the customer; a person presents (I can't share my screen).
7. Offer: "Want a one-page 16:9 infographic for screen-sharing instead (or as well)?"

## Step 7: Optional one-page infographic
If the user asks, use Image_Operator to create a one-page 16:9 infographic with: customer name and date, 3-4 key points, status of open issues (or what's new), and next steps. Apply the same guardrails. Deliver it to the user only.

## Step 8: Scheduled mode (only if {SCHEDULE_OPTION} is on)
Read tomorrow's events on the user's calendar (GoogleCalendarOperator or Outlook calendar operator). Keep only external customer meetings (attendees outside the user's company domain who match a CRM account). For each, run Steps 2 to 6 with variant (a) and topics taken from the meeting title and description. Email each deck to the user. If a meeting has no matching account, skip it and list it.

## Output format
**Customer Briefing Deck: {CUSTOMER} · {DATE}**
- Variant and topic order: …
- Deck requested: yes, emailed to {DECK_RECIPIENT} (PDF + text version, a few minutes)
- Source status: each source worked / no data / unavailable
- Verify flags: …
- Left out (internal or unreleased): …
- Reminders: check sender and spam; review before showing; a person presents
~~~~

## 8. Test plan

Ask the user to approve the test first. Use a **test or low-stakes customer** and send the deck only to the user.

1. The user names a customer (a test account, or a customer whose data they're comfortable with), a date and two topics.
2. Run the skill: "Make a short briefing deck for my {CUSTOMER} call on {DATE} about {TOPICS}."
3. Wait a few minutes for the email. Open the PDF and the text version.
4. Run it again with "save the account" to test variant (b) (optional).
5. Ask for the one-page infographic (optional).

| Check | Pass? |
|---|---|
| Clone confirmed variant and topic order, and asked at most one question | ☐ |
| Source status was reported (worked / no data / unavailable) | ☐ |
| Deck email arrived within a few minutes at the right address | ☐ |
| Sender address noted and not in spam (or added to safe senders) | ☐ |
| Deck is 16:9 with about 6–9 slides, including a title and a closing slide | ☐ |
| Topics appear in the order requested | ☐ |
| Slides use real customer context (calls, CRM, Linear, email), nothing invented | ☐ |
| No unreleased features or internal-only notes appear | ☐ |
| "Verify" flags were raised for uncertain names or numbers | ☐ |
| Variant (b) (if tested) has situation, issues and owners, fixes, dated plan, asks, next steps | ☐ |
| Infographic (if tested) is one page, 16:9 and readable | ☐ |
| Nothing was sent to the customer; no CRM, Linear or file changes were made | ☐ |
| (If scheduled) the scheduled task exists and builds decks only for tomorrow's customer meetings | ☐ |

6. Fix anything that failed and re-run.

## 9. Final status checklist

When you finish, send the user a status summary in this format:

**✅ Done by me**
- [ ] Discovery table shared
- [ ] Placeholder values confirmed
- [ ] Missing operators attached: …
- [ ] Customer Briefing Deck skill created (or full text handed over for copy-paste)
- [ ] Scheduled task created (if wanted)
- [ ] Test deck requested; results: …

**⏳ Waiting on you**
- [ ] Connect your own CRM, email, Drive/OneDrive and Linear (read access)
- [ ] Tell me the transcripts folder
- [ ] Save the skill (if I handed it over)
- [ ] Check the sender address and spam folder for the deck email
- [ ] Review every deck before showing it to a customer

**💡 Optional next steps**
- [ ] Turn on the scheduled variant for tomorrow's customer meetings (`{SCHEDULE_OPTION}`)
- [ ] Add `{INTERNAL_ONLY_RULES}` after your first decks
- [ ] Try the "Save the account" variant on an at-risk customer
- [ ] Ask for a one-page infographic for screen-sharing
- [ ] Pair with **daily-meeting-briefing** or **account-health-autopilot**