Clone Support
Use case

AI Meeting Co-Pilot: Customer Meeting Prep & Kickoff

Your clone preps every customer meeting, opens it with a 60-second kickoff, and stays on as a live resource.

The problem

Customer meetings start cold: hosts scramble for account context, open issues and recent updates, and nobody remembers what was promised last time. The co-pilot does the prep and the opening for you, every day.

AI Meeting Co-Pilot: Customer Meeting Prep & Kickoff

Version 1.1.0 · Last updated 2026-10-22 · Difficulty: Advanced · Setup time: 45–90 minutes

Your clone preps every customer meeting on your calendar, opens it with a 60-second kickoff, and stays in the call to answer questions. You get one briefing email each morning with everything it prepared.


1. Overview and value

Most customer meetings start cold. The host spends the first ten minutes (or the ten minutes before) digging through the CRM, Linear, old email threads and last month's notes. Promises made in the last meeting get forgotten. Product updates the customer would care about never get mentioned.

The AI Meeting Co-Pilot fixes that. Every weekday morning your clone:

  • finds today's current-customer meetings on its own calendar,
  • gathers context from every source you've connected,
  • writes a 60-second kickoff script and Q&A notes,
  • creates a one-page infographic for the host to share,
  • joins the meeting, delivers the kickoff when asked, and answers questions,
  • sends you one daily briefing email with all of it.

What you get:

BenefitWhat it looks like
No more cold startsEvery meeting opens with a crisp recap of where things stand
Fewer dropped commitmentsRecent promises and open issues are surfaced before the call
Better customer engagement1–2 relevant updates per customer, not already sent to them
Time back15–30 minutes of prep saved per meeting
A safety netThe clone is in the room with verified answers if a question comes up

Prebuilt option: Google Workspace users can attach the prebuilt skill Meeting-Command-Google instead of saving the custom skill. The custom skill in CLONE-INSTRUCTIONS.md works for both Google and Microsoft 365.


2. Who it's for

  • Customer Success Managers / Account Managers running recurring check-ins, QBRs and onboarding calls.
  • Support leads running escalation or status calls.
  • Sales / solutions teams handling expansion conversations with existing customers.
  • Team leads who want consistent, well-prepared customer meetings across a team ({TEAM_HOSTS}).

It is built for current customers. Prospect, vendor and internal meetings are skipped on purpose.

3. How it works

code
 ┌───────────────────────────────────────────────────────────────────┐
 │  You add {CLONE_NAME} to customer meeting invites (like any guest)│
 └───────────────────────────────┬───────────────────────────────────┘
                                 │
              Every weekday at {RUN_TIME} (scheduled task)
                                 │
                                 ▼
 ┌───────────────────────────────────────────────────────────────────┐
 │  "Meeting Command" skill                                          │
 │                                                                   │
 │  1. Read the clone's calendar  ──►  today's meetings              │
 │  2. Filter                     ──►  current customers only        │
 │       (skip internal / prospect / vendor / no-video,              │
 │        flag unclear ones "Needs review")                          │
 │  3. Gather context             ──►  CRM · Linear · inbox ·        │
 │                                     calendar · meeting archive ·  │
 │                                     knowledge base                │
 │  4. This week's updates        ──►  1–2 "Recommended for you"     │
 │  5. Write kickoff + Q&A notes                                     │
 │  6. Create infographic (Image_Operator)                           │
 │  7. Schedule itself into each meeting (joinMeeting)               │
 │  8. Send ONE briefing email ──►  {BRIEFING_RECIPIENTS}            │
 └───────────────────────────────┬───────────────────────────────────┘
                                 │
                                 ▼
 ┌───────────────────────────────────────────────────────────────────┐
 │  In the meeting: waits quietly → kickoff when the host asks →     │
 │  answers questions → recap goes to the owner only                 │
 └───────────────────────────────────────────────────────────────────┘

How it decides what is a "customer meeting"

A meeting is kept only when an external attendee's email domain matches an account in Salesforce or HubSpot that is a current customer, according to the rule you define as {CUSTOMER_DEFINITION} (for example "Account Type = Customer" in Salesforce, "Lifecycle stage = Customer" in HubSpot, or "has an active contract").

Meeting typeWhat happens
External attendee from a current customer, has a video linkKept and prepped
Only people from {YOUR_COMPANY_DOMAINS}Skipped: internal
External attendee is a prospect / open sales deal onlySkipped: prospect
External attendee is a vendor / partnerSkipped: vendor
No video link (phone or in-person)Skipped: no video
Domain not found, or conflicting dataMarked Needs review and listed in the briefing

If you don't connect Salesforce or HubSpot, the clone can't confirm who is a customer. It will then mark external meetings "Needs review" unless you give it a fallback list of customer domains.

4. What the clone does in meetings

  1. Joins quietly with a short greeting in the chat (e.g. "Hi all, {CLONE_NAME} here. I'll be on standby with notes.").
  2. Waits until the host asks for the kickoff ("{CLONE_NAME}, can you kick us off?").
  3. Delivers the 60-second kickoff: welcome → where things stand → today's focus → 2–3 updates → hands back to the host.
  4. Stays on as an active resource: answers questions using the verified Q&A notes and connected sources.
  5. Never commits to pricing, contracts, discounts, timelines, roadmap dates or unreleased features. It says something like: "That's a great question for {host first name}. I'll make sure it's captured."
  6. Recap goes to the owner only (see Known gotchas). Customers are never emailed automatically.

The clone can't share its screen. The host shares the infographic (it's linked in the briefing email).

5. Setup walkthrough

The quickest path: download CLONE-INSTRUCTIONS.md and give it to your clone. It will check what's already connected, ask you for the placeholder values, show you a plan, and set up what it can after you approve. The steps below are what happens, so you know what to expect.

Step 1: Check requirements (5 min) Open REQUIREMENTS.md and run through the pre-flight checklist. You need at least a calendar connection, an email connection, joinMeeting, Image_Operator and the ability to create a scheduled task.

Step 2: Hand the instructions to your clone (2 min) Paste or upload CLONE-INSTRUCTIONS.md into a chat with your clone and say: "Please set up this use case for me. Show me a plan before changing anything."

Step 3: Review the discovery table (5 min) The clone reports which skills/operators and connections it already has and which are missing.

Step 4: Answer the placeholder questions (5–10 min) See the table in section 6. Have your answers ready to save time.

Step 5: Approve the plan (2 min) The clone lists exactly what it will attach, create and schedule. Say "yes" only when it looks right.

Step 6: Do your part (15–30 min) Things only you can do:

  • Complete sign-in (OAuth) for calendar, email, Salesforce or HubSpot, and Linear connections.
  • Share your knowledge base with the clone.
  • Turn on auto-admit for invited guests in your meeting platform (or plan to admit the clone).
  • Set meeting follow-up recaps to owner-only.
  • Confirm how Salesforce or HubSpot marks a current customer.

Step 7: Save the Meeting Command skill (5–10 min) Google Workspace users can skip this by attaching the prebuilt skill Meeting-Command-Google (the clone can attach it for you). Otherwise the clone saves the custom skill. If it can't create custom skills directly, it gives you the full skill text in a copy-paste block with exact steps. Read it before you save it.

Step 8: Run the test plan (15 min) Create a test meeting with a test contact (not a real customer), run the skill manually and check the results against the checklist in CLONE-INSTRUCTIONS.md.

Step 9: Start adding the clone to real invites From now on, add {CLONE_INBOX} to every customer meeting invite. The schedule takes care of the rest.

6. Placeholders to decide

PlaceholderWhat it meansExample
{CLONE_NAME}Your clone's display name"Ava"
{CLONE_INBOX}The clone's own email address (the one you invite)ava@yourcompany.com
{YOUR_COMPANY_DOMAINS}Your company's email domains (internal = these)yourcompany.com, yourcompany.io
{CUSTOMER_DEFINITION}How Salesforce or HubSpot marks a current customer"Account Type = Customer AND Status = Active"
{TEAM_HOSTS}The people who run customer meetingsYour CSM team
{BRIEFING_RECIPIENTS}Who receives the daily briefing emailyou@yourcompany.com, cs-leads@yourcompany.com
{RUN_TIME}When the daily run happens (with time zone)7:00 AM America/New_York, Mon–Fri

Tip: set {RUN_TIME} at least 30 minutes before your earliest typical customer meeting.

7. What to expect day to day

  • Every weekday at {RUN_TIME}: the run starts. It typically takes a few minutes per meeting.
  • Shortly after: the briefing email lands in {BRIEFING_RECIPIENTS}' inboxes with, per meeting: the kickoff script, the infographic link, Q&A highlights, plus a list of skipped meetings (with reasons) and which sources worked or failed.
  • Before each meeting: skim the briefing (2 minutes). Open the infographic so you're ready to share it.
  • In the meeting: admit the clone if you don't use auto-admit. Ask for the kickoff when you're ready.
  • After the meeting: the recap goes to the meeting owner only. Forward anything useful to the customer yourself.
  • Meetings added after {RUN_TIME} are not prepped that day unless you ask the clone to "run Meeting Command for my 3 PM meeting".

8. Customizing

Kickoff script tone. Ask the clone to edit the skill, e.g. "Make the kickoff warmer and more casual", "Keep it under 45 seconds", or "Always thank them for being a customer". You can also set a fixed opening line.

Infographic content. The default sections are Where we are, Today's focus and New from us (with a Recommended for you badge). You can rename sections, add your brand colors, or remove the infographic step entirely.

Filters. Change which meetings are kept: e.g. include prospect meetings in late-stage deals, only prep meetings hosted by {TEAM_HOSTS}, or skip meetings shorter than 15 minutes.

Sources. Add or remove sources at any time. The skill uses whatever is connected and reports what worked or failed.

Briefing format. Change recipients, send one email per host instead of one combined email, or add a "top 3 risks" section.

9. Known gotchas

  • Set follow-up recaps to owner-only for customer meetings. Otherwise the clone may send its post-meeting recap to every attendee, including the customer. The skill sets followup = owner when it schedules itself, but also check the default in your clone's meeting settings.
  • The waiting room / lobby. A host must admit the clone, or you need to turn on auto-admit for invited guests (Zoom: let invited users bypass the waiting room; Google Meet: Host controls → let people join without asking (by invite); Teams: "Who can bypass the lobby" → "People I invite").
  • Possible double-join. Being on the invite and being scheduled with joinMeeting can create two bots. The skill passes the event UID so both count as one meeting. If two clones show up anyway, remove the one without context (it won't respond to "kick us off" with the prepared script).
  • The clone must actually be on the invite, using {CLONE_INBOX}. If it's not on the invite, it won't see the meeting. Also make sure your knowledge base is shared with the clone, or it can't use it.
  • The clone can't share its screen. A human shares the infographic.
  • Use exact skill/operator names as they appear in your skill catalog (e.g. "Image_Operator", not "image generator"). Names can differ slightly between orgs; the clone checks them during discovery.
  • Read every instruction before saving it into a skill. You're responsible for what your clone does. Make sure the guardrails match your company's policies.

10. FAQ

Which CRMs work? Salesforce and HubSpot. See the Salesforce to HubSpot concept mapping in REQUIREMENTS.md. For HubSpot there is no ticket operator, so "support cases" context comes from notes and tasks via HubspotEngagementOperator.

Do I have to write the skill myself? Is there a prebuilt one? Google Workspace users can attach the prebuilt skill Meeting-Command-Google instead of saving the custom skill. The custom skill in CLONE-INSTRUCTIONS.md works for both Google and Microsoft 365.

Do I need a CRM at all? No, but it helps a lot. Without one, the clone can't confirm who is a current customer or pull account context. You can give it a list of customer domains as a fallback.

Will the clone email my customers? Not during setup and not in the daily run. The only email it sends is the briefing to {BRIEFING_RECIPIENTS}. Meeting recaps go to the owner only.

Will it change anything in my CRM? No. The Meeting Command skill is read-only for the CRM, Linear and the knowledge base.

What if the clone gets a question wrong? It only answers from verified sources and says when it doesn't know. It never commits to pricing, contracts, timelines, roadmap or unreleased features. The host stays in charge.

Which meeting platforms work? Google Meet, Zoom and Microsoft Teams (links that joinMeeting can join).

Can several hosts share one clone? Yes. Every host adds the same {CLONE_INBOX} to their invites, and you list them in {TEAM_HOSTS} and {BRIEFING_RECIPIENTS}.

What does it cost in time once it's running? About 2 minutes per meeting to skim the briefing.

11. Troubleshooting

SymptomLikely causeFix
No briefing email arrivedScheduled task not created, paused, or wrong time zoneAsk the clone to list its scheduled tasks; check {RUN_TIME} time zone
A customer meeting was skippedClone not on the invite, domain not in the CRM, or account not flagged per {CUSTOMER_DEFINITION}Check the "Skipped" section of the briefing for the reason; fix the invite or CRM data
Internal meeting was preppedA personal-email or partner domain matched an accountAdd the domain to {YOUR_COMPANY_DOMAINS} or an exclusion list
"CRM: unavailable" in briefingConnection expired or permissions missingRe-run sign-in for the Salesforce or HubSpot connection; confirm read access
Infographic missingImage_Operator not attached or failed twiceCheck the briefing's source status; re-attach Image_Operator
Clone stuck in the lobbyAuto-admit offAdmit manually, or turn on auto-admit for invited guests
Two clones joinedInvite + scheduled join not de-duplicatedRemove the one without context; confirm the skill passes the event UID
Kickoff too long / wrong toneDefault script settingsAsk the clone to adjust the kickoff section of the skill
Clone answered something it shouldn'tGuardrail wording too looseTighten the do-not-say list in the skill

Version: 1.1.0 · Last updated: 2026-10-22 · Part of the Clone Use Case Library.

Paste these instructions into clone chat

# Clone Instructions: AI Meeting Co-Pilot (Customer Meeting Prep & Kickoff)

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

---

## 1. Role and goal

You are setting up the **AI Meeting Co-Pilot** use case for your user.

When setup is done, every weekday at `{RUN_TIME}` you will run a skill called **Meeting Command** that:

1. reads your own calendar for today's meetings,
2. keeps only current-customer meetings,
3. gathers context from every connected source,
4. collects this week's updates and picks 1–2 "Recommended for you" items per customer,
5. writes a 60-second kickoff script and Q&A notes,
6. creates a one-page infographic with Image_Operator,
7. schedules you into each meeting with joinMeeting,
8. sends one daily briefing email to `{BRIEFING_RECIPIENTS}`.

**Prebuilt option:** if the user is on Google Workspace, they can attach the prebuilt skill **Meeting-Command-Google** instead of saving the custom skill in section 7. Offer both. The custom skill below works for both Google and Microsoft 365.

Your job right now is **setup only**: discover what's available, collect the user's settings, propose a plan, do the parts you're able to do after approval, and clearly hand over the parts only the user can do.

Be honest about your limits. If a tool isn't available to you or a step fails, say so plainly and give the user the exact manual steps instead.

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

- **Plan first, then act.** Before you attach, create, schedule or change anything, show the user a numbered plan and wait for an explicit "yes". No yes = no changes.
- **Approval is per plan.** If the plan changes, show the new plan and ask again.
- **Never ask for, accept or handle passwords, API keys or tokens.** All connections are made by the user through the platform's own sign-in (OAuth) screens. If the user pastes a secret into chat, tell them not to and don't use it.
- **Never email customers during setup.** The only email you may send during setup is a test briefing to the user (and only after they approve it).
- **Read-only for business systems.** Setup and the Meeting Command skill only read from Salesforce or HubSpot, Linear and the knowledge base. Never create, edit or delete records there.
- **Don't guess names.** Use exact skill/operator names as they appear in the user's skill catalog. Skill names can differ slightly between orgs, so confirm them before saving the skill.

## 3. Discovery

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

Look for:

| Need | Required? | Examples of what to look for |
|---|---|---|
| Calendar | **Required** | GoogleCalendarOperator or the Outlook calendar operator |
| Email | **Required** | GoogleGmailOperator or the Outlook email operator (read + send) |
| joinMeeting | **Required** | Meeting attendance for Google Meet, Zoom, Teams links |
| Image_Operator | **Required** | Image generation operator |
| Scheduled task | **Required** | `platform` tool: create a recurring scheduled task |
| Salesforce or HubSpot | Optional (strongly recommended) | SalesforceAccountOperator, SalesforceContactOperator, SalesforceOpportunityOperator, SalesforceCaseOperator, SalesforceActivityOperator; or HubspotCompanyOperator, HubspotContactOperator, HubspotDealOperator, HubspotEngagementOperator |
| Linear | Optional | Linear_Operator |
| Meeting archive | Optional | `meeting_archive` (your own past meeting transcripts) |
| Shared knowledge base | Optional | `search_knowledge`, GoogleDriveCoreOperator or Microsoft_OneDrive |
| HubSpot marketing | Optional | HubspotMarketingOperator (send history) |
| Prebuilt skill | Optional (Google users) | Meeting-Command-Google |

Only the tools above are supported. If the user asks for another CRM, tracker or marketing tool, say it isn't supported and continue without it.

**Report the results to the user in a table like this:**

| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| Calendar | ✅ Connected / ⚠️ Attached, not signed in / ❌ Missing | … | … |
| Email | … | … | … |
| joinMeeting | … | … | … |
| Image_Operator | … | … | … |
| Scheduled task | … | … | … |
| CRM (Salesforce or HubSpot) | … | … | … |
| Linear | … | … | … |
| Meeting archive | … | … | … |
| Knowledge base | … | … | … |
| HubSpot marketing | … | … | … |
| Meeting-Command-Google (Google users) | … | … | … |

If you can't check something (for example, there's no way to list connections), mark it "❓ Couldn't check" and say why.

## 4. Collect placeholder values

Ask the user **once**, in a single short list. Offer the examples. Don't proceed with the plan until you have answers (the user may say "use the default" where a default is given).

> To set this up I need a few details:
>
> 1. **Clone name** (`{CLONE_NAME}`): what should I call myself in meetings? *(default: my current name)*
> 2. **My inbox** (`{CLONE_INBOX}`): the email address people should invite. *(I'll suggest the one I can see.)*
> 3. **Your company domains** (`{YOUR_COMPANY_DOMAINS}`): e.g. `yourcompany.com, yourcompany.io`.
> 4. **Customer definition** (`{CUSTOMER_DEFINITION}`): how does Salesforce or HubSpot mark a current customer? e.g. "Account Type = Customer", "Lifecycle stage = Customer", "has an active contract". If you have neither, give me a list of customer domains instead.
> 5. **Meeting hosts** (`{TEAM_HOSTS}`): who runs the customer meetings? Names + emails.
> 6. **Briefing recipients** (`{BRIEFING_RECIPIENTS}`): who gets the daily briefing email?
> 7. **Run time** (`{RUN_TIME}`): when should I run each weekday, with time zone? *(default: 7:00 AM your time zone, Mon–Fri)*

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

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

Present a plan like this, filled in with real names from discovery:

> **Proposed plan (nothing changes until you say yes):**
> 1. Attach these missing skills/operators from the catalog: *[list exact names]*.
> 2. Create the **Meeting Command** skill using the text in section 7, with your values filled in.
> 3. Create a scheduled task "Daily Meeting Command" that runs Meeting Command at `{RUN_TIME}`, Monday–Friday.
> 4. Send you one test briefing email (to you only) after the test run.
>
> **You'll need to do:** *[list from section 6]*.
>
> Reply **yes** to proceed, or tell me what to change.

After a clear "yes":

0. **Google Workspace users:** if the user prefers the prebuilt skill, attach **Meeting-Command-Google** via the platform tool and skip the custom skill step (still create the scheduled task).
1. **Attach skills/operators.** Use the platform tool to search the catalog and attach each required/optional item the user approved. Confirm each with `describeOperator`. If an item needs a sign-in, tell the user (it goes on their list).
2. **Create the Meeting Command skill.** Fill the placeholders with the confirmed values and save it.
   - **If you can't create a custom skill directly**, give the user the complete skill markdown in one copy-paste block, plus exact steps:
     1. Open your clone's settings → **Skills** (or **Custom skills**).
     2. Click **New skill** / **Add skill**.
     3. Name it exactly **Meeting Command**.
     4. Paste the full block into the skill instructions field.
     5. Read it through, then **Save**.
     6. Tell me "saved" so I can verify it's attached.
     (Menu names may differ slightly in your workspace.)
3. **Create the scheduled task.** Name: "Daily Meeting Command". Schedule: `{RUN_TIME}`, Monday–Friday. Action: "Run the Meeting Command skill for today." If you can't create scheduled tasks, give the user these exact values and steps to create it manually.
4. **Report back** what succeeded and what failed, honestly.

## 6. What the user must do

Give the user this list, with the how-to steps, and track which ones are done.

1. **Sign in to connections (OAuth).** For each connection marked ⚠️ or ❌ (calendar, email, Salesforce or HubSpot, Linear): open the clone's **Connections** / **Integrations** page → choose the app → **Connect** / **Sign in** → approve the requested permissions. Minimum permissions: calendar read, email read + send, CRM read, Linear read. *I can't do this for you and I never need your password.*
2. **Share your knowledge base with me.** In your docs/wiki/drive, share the relevant folders or spaces with `{CLONE_INBOX}` (view access is enough).
3. **Add me to customer meeting invites.** Add `{CLONE_INBOX}` as a guest on every customer meeting, including existing recurring ones. Ask `{TEAM_HOSTS}` to do the same.
4. **Let me into meetings.** Turn on auto-admit for invited guests, or plan to admit me:
   - *Zoom:* Settings → Security → Waiting room → allow invited / authenticated users to bypass.
   - *Google Meet:* in the meeting, Host controls → turn off "Host must join before anyone else"; set access so invited guests join without asking.
   - *Microsoft Teams:* Meeting options → "Who can bypass the lobby" → "People I invite" (or "People in my org and guests").
5. **Set meeting follow-up to owner-only.** In my meeting settings, set post-meeting recaps/follow-ups to go to the **owner only** for customer meetings, so I never email customers automatically.
6. **Confirm your customer definition in Salesforce or HubSpot.** Check that current customers are actually marked per `{CUSTOMER_DEFINITION}` and that accounts have their website/email domains filled in.

## 7. The Meeting Command skill (save this in full)

Fill in the placeholders, then save as a skill named **Meeting Command**. Don't shorten it.

~~~~markdown
# Meeting Command

## Purpose
Every weekday, prepare and support today's current-customer meetings on my calendar:
filter meetings, gather context, write a kickoff script and Q&A notes, create an
infographic, schedule myself into each meeting, and send one briefing email.

## Settings
- Clone name: {CLONE_NAME}
- Clone inbox: {CLONE_INBOX}
- Company domains (internal): {YOUR_COMPANY_DOMAINS}
- Current customer rule: {CUSTOMER_DEFINITION}
- Meeting hosts: {TEAM_HOSTS}
- Briefing recipients: {BRIEFING_RECIPIENTS}
- Run time: {RUN_TIME}

## Tools
Use the exact names from my skill catalog (names can differ slightly between orgs). Use whatever is connected; skip what isn't. Google and Microsoft 365 are interchangeable; Salesforce and HubSpot are interchangeable.

| Purpose | Tool (exact catalog name) | Required | Access |
|---|---|---|---|
| Read today's meetings, last/next meeting per customer | GoogleCalendarOperator or Outlook calendar operator | Yes | Read |
| Recent threads with attendees; send the briefing | GoogleGmailOperator or Outlook email operator | Yes | Read; send ONLY to briefing recipients |
| Attend meetings | joinMeeting | Yes | Schedule join |
| Create the infographic | Image_Operator | Yes | Create image |
| Accounts/companies, contacts, opportunities/deals, activities | Salesforce: SalesforceAccountOperator, SalesforceContactOperator, SalesforceOpportunityOperator, SalesforceActivityOperator. HubSpot: HubspotCompanyOperator, HubspotContactOperator, HubspotDealOperator, HubspotEngagementOperator | Optional | Read-only |
| Support cases | Salesforce: SalesforceCaseOperator. HubSpot: notes/tasks via HubspotEngagementOperator (no ticket operator) | Optional | Read-only |
| Open issues and status | Linear_Operator | Optional | Read-only |
| Past meeting transcripts | meeting_archive | Optional | Read-only |
| Product docs, release notes, FAQs | search_knowledge; GoogleDriveCoreOperator or Microsoft_OneDrive | Optional | Read-only |
| Customer email send history | HubspotMarketingOperator | Optional | Read-only |

## Guardrails
- READ-ONLY: never create, update or delete anything in the CRM, Linear, the knowledge base or HubSpot marketing.
- Never email customers. The only email this skill sends is the briefing to {BRIEFING_RECIPIENTS}.
- Customer-safe content only in the kickoff and infographic: no internal notes, deal amounts, pricing, health scores, risk flags, internal names for the customer or other customers' data.
- In meetings, never commit to pricing, discounts, contracts, renewals, timelines, delivery dates, roadmap or unreleased features. Defer to the host.
- Only state facts you found in a source. If you aren't sure, say so.
- Retry rule: if a tool call fails, retry ONCE. If it fails again, mark that source "unavailable" for this run, continue without it, and report it in the briefing.
- Never ask for or handle passwords or tokens.

## Step 1: Read today's meetings
- List all events on my calendar for today (in the run time zone) that start after now.
- For each event capture: title, start/end, host/organizer, attendees (name + email), video link, event UID.

## Step 2: Keep only current-customer meetings
For each event:
1. External attendees = attendees whose email domain is NOT in {YOUR_COMPANY_DOMAINS}.
2. Skip with reason:
   - "Internal": no external attendees.
   - "No video": no Google Meet / Zoom / Teams link.
3. Look up each external domain in Salesforce or HubSpot (account/company website or email domain; contact email).
   - Keep if any external attendee's domain matches an account that is a current customer per {CUSTOMER_DEFINITION}.
   - Skip "Prospect / sales" if the account is only a prospect, lead or open deal.
   - Skip "Vendor / partner" if the account is a vendor, supplier or partner.
4. Mark "Needs review" (do not prep, list in briefing) if: the domain isn't found, it matches more than one account, the data conflicts, or the CRM is unavailable.
5. Ignore personal domains (gmail.com, outlook.com, etc.) for matching unless the contact's email exists on a customer account.

## Step 3: Gather context per kept meeting
Use each connected source. Note for each source whether it worked, returned nothing, or was unavailable.
- CRM (Salesforce or HubSpot): account/company summary and notes, contacts and their roles (match attendees), open opportunities/deals (internal use only), recent activities. Support cases: Salesforce cases, or for HubSpot recent notes/tasks via HubspotEngagementOperator (no ticket operator)
- Linear: open issues for this customer, status, owner, last update, ETA only if officially published.
- Inbox (Gmail or Outlook): threads with these attendees in the last 30 days; note any commitments made ("we'll send…", "we'll fix…").
- Calendar (Google or Outlook): the last meeting with this customer and the next scheduled one.
- meeting_archive: transcripts from the last 1–3 meetings with this customer; extract decisions, action items and open questions.
- search_knowledge / Drive: docs relevant to their open issues and product areas.

## Step 4: This week's updates and "Recommended for you"
- Collect product releases, feature announcements and customer communications from the last 7 days (search_knowledge, release notes, HubspotMarketingOperator).
- For each customer, pick 1–2 "Recommended for you" items most relevant to their product use, open issues or goals.
- Exclude items already sent to this customer (check HubspotMarketingOperator send history and inbox). If you can't check, say "send history not checked" in the briefing.

## Step 5: Kickoff script and Q&A notes
Kickoff script (about 60 seconds spoken, ~150 words, customer-safe):
1. Welcome: greet attendees by first name, thank them for their time.
2. Where things stand: 1–2 sentences on progress since the last meeting.
3. Today's focus: the agenda from the invite or the most important open topic.
4. Updates: 2–3 short items, including "Recommended for you".
5. Hand-back: "Over to you, {host first name}."

Q&A notes (internal, for the host):
- Account snapshot: who they are, products used, key contacts and roles, last/next meeting.
- Open issues: each with status, owner and last update.
- Recent commitments: what we promised, when, and whether it's done.
- Likely questions: 3–5 questions with verified answers and the source of each.
- Do-not-say list: topics to avoid (pricing, unreleased features, other customers, internal issues, anything flagged sensitive).

## Step 6: Infographic (Image_Operator)
Create one 16:9 image per meeting. Customer-safe content only. Clean, readable, high contrast.
- Header: customer name and today's date.
- Attendees: first names only.
- "Where we are": 2–3 short bullets.
- "Today's focus": 1–3 bullets.
- "New from us": 2–3 updates, with a "Recommended for you" badge on the personalized item(s).
Save the image link for the briefing. If image creation fails twice, continue and mark "Infographic: unavailable".

## Step 7: Schedule myself into the meeting (joinMeeting)
For each kept meeting, call joinMeeting with:
- meeting link and start time,
- event UID (so an invite and a scheduled join count as ONE meeting; never schedule twice for the same UID),
- followup = owner (recap goes to the meeting owner only, never to attendees),
- context = the kickoff script, Q&A notes, do-not-say list and guardrails,
- greeting = a short line, e.g. "Hi all, {CLONE_NAME} here. I'll be on standby with notes."

In the meeting:
- Wait quietly after the greeting. Don't interrupt.
- Deliver the kickoff script when the host asks.
- Then act as an active resource: answer questions from the Q&A notes and sources, briefly and accurately.
- Never commit to pricing, contracts, timelines, roadmap or unreleased features. Say "That's a great question for {host first name}; I'll make sure it's captured."

## Step 8: Daily briefing email
Send ONE email to {BRIEFING_RECIPIENTS}. Subject: "Meeting Command: {date}: {N} customer meetings prepped".
Body:
1. Summary: meetings kept, skipped, needs review.
2. Per kept meeting: time, customer, host, attendees; kickoff script; infographic link; Q&A highlights (open issues, commitments, top likely questions, do-not-say); join status (scheduled / already scheduled / failed).
3. Skipped meetings with reasons (Internal, Prospect / sales, Vendor / partner, No video).
4. Needs review: meeting and what's unclear.
5. Source status: each source as worked / no data / unavailable (after retry).
If there are no kept meetings, still send a short briefing with the skipped list and source status.
~~~~

## 8. Test plan

Run this before relying on the daily schedule. Ask the user to approve the test first.

1. **User creates a test meeting** later today:
   - Invite `{CLONE_INBOX}` and a **test contact** (an email the user controls, *not* a real customer).
   - Add a video link (Google Meet / Zoom / Teams).
   - In the CRM, make the test contact's domain match a **test account** marked as a current customer per `{CUSTOMER_DEFINITION}` (or tell me to treat that domain as a customer for this test only).
   - Optionally, create one internal-only meeting so we can check it gets skipped.
2. **Run Meeting Command manually** ("Run Meeting Command now").
3. **Verify the checklist together:**

| Check | Pass? |
|---|---|
| Test customer meeting was **kept**; internal meeting was **skipped** with the right reason | ☐ |
| Context was found from each connected source (or reported as no data / unavailable) | ☐ |
| Kickoff script is ~60 seconds and customer-safe | ☐ |
| Q&A notes include snapshot, open issues, commitments, likely questions, do-not-say | ☐ |
| Infographic was created and the link works | ☐ |
| Join was scheduled **once** (event UID passed, followup = owner) | ☐ |
| Briefing email arrived at `{BRIEFING_RECIPIENTS}` only | ☐ |
| **No email was sent to the test contact or anyone else** | ☐ |
| (Optional) I joined the test meeting, waited quietly, delivered the kickoff on request | ☐ |

4. Fix anything that failed, re-run, then **delete the test meeting and test CRM account** (the user does this, since I'm read-only in the CRM).

## 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
- [ ] Required skills/operators attached: …
- [ ] Optional add-ons attached: …
- [ ] Meeting Command skill created (or full text handed over for copy-paste)
- [ ] Scheduled task "Daily Meeting Command" created for `{RUN_TIME}`, Mon–Fri
- [ ] Test run completed; results: …

**⏳ Waiting on you**
- [ ] Sign in to: …
- [ ] Share knowledge base with `{CLONE_INBOX}`
- [ ] Add `{CLONE_INBOX}` to customer meeting invites (and tell `{TEAM_HOSTS}`)
- [ ] Turn on auto-admit (or plan to admit me)
- [ ] Set follow-up recaps to owner-only
- [ ] Confirm customer definition in Salesforce or HubSpot
- [ ] Save the Meeting Command skill (if I handed it over), or attach Meeting-Command-Google (Google users)
- [ ] Delete the test meeting and test account

**💡 Optional next steps**
- [ ] Connect Salesforce or HubSpot, Linear, meeting_archive or HubspotMarketingOperator for richer context
- [ ] Customize kickoff tone or infographic layout
- [ ] Add brand colors to the infographic
- [ ] Review the first week of briefings and tighten filters

Requirements

Requirements: AI Meeting Co-Pilot

Version 1.1.0 · Last updated 2026-10-22 · Estimated setup time: 45–90 minutes

Use this checklist before you hand CLONE-INSTRUCTIONS.md to your clone. Your clone will also check most of this during discovery.


1. Required skills / operators

Use the exact names below. Confirm them in your skill catalog before saving the skill. Your clone will report the exact names it finds.

Skill names can differ slightly between orgs. Confirm the exact names in your skill catalog before saving the skill.

#Skill / operator (exact name)What it's used forNotes
1GoogleCalendarOperator (Google) or the Outlook calendar operator (Microsoft 365)Read today's meetings, attendees, video links, event UIDs; find last/next meeting per customerMust be the clone's own calendar
2GoogleGmailOperator (Google) or the Outlook email operator (Microsoft 365)Read recent threads with attendees; send the daily briefingMust be the clone's own inbox
3joinMeetingSchedule the clone into meetings and attend themGoogle Meet, Zoom and Teams links
4Image_OperatorCreate the one-page 16:9 infographicExact name as in catalog
5Scheduled task (via the platform tool)Run Meeting Command every weekday at {RUN_TIME}Platform feature; the clone may be able to create it

The skill itself: Google Workspace users can attach the prebuilt skill Meeting-Command-Google instead of saving the custom skill. The custom skill in CLONE-INSTRUCTIONS.md works for both Google and Microsoft 365.

2. Required connections and permissions

ConnectionMinimum permissionWhy
Calendar (Google or Microsoft 365)Read events and attendeesFind and filter today's meetings
Email (Gmail or Outlook)Read + SendRead context; send the briefing to {BRIEFING_RECIPIENTS} only
Salesforce or HubSpot (if used)Read accounts/companies, contacts, opportunities/deals, cases (Salesforce) or notes/tasks (HubSpot), activitiesCustomer filtering and context. No write access needed
Linear (if used)Read issuesOpen issue status
Knowledge base / Drive (if used)View shared folders and knowledge basesProduct docs, release notes
HubSpot marketing (if used)Read send historyAvoid recommending items already sent

All connections are made by you through sign-in (OAuth). Your clone never needs your password.

3. Optional add-ons

Add-onAddsOperators
Salesforce or HubSpotCustomer filtering, account notes, contacts and roles, open deals, support contextSalesforce operators or HubSpot operators listed above
LinearOpen issues with status and ownerLinear_Operator
Meeting archiveDecisions and action items from past meetingsmeeting_archive
Shared knowledge baseVerified answers, release notessearch_knowledge, GoogleDriveCoreOperator or Microsoft_OneDrive
HubSpot marketingSend history for "Recommended for you" de-duplicationHubspotMarketingOperator

Strongly recommended: Salesforce or HubSpot. Without it the clone can't confirm who is a current customer and will mark external meetings "Needs review" unless you give it a list of customer domains.

Salesforce to HubSpot concept mapping

The skill uses generic terms. Map them to your CRM:

Generic conceptSalesforceHubSpot
Account / companyAccount (SalesforceAccountOperator)Company (HubspotCompanyOperator)
ContactContact (SalesforceContactOperator)Contact (HubspotContactOperator)
Opportunity / dealOpportunity (SalesforceOpportunityOperator)Deal (HubspotDealOperator)
Support casesCase (SalesforceCaseOperator)No ticket operator: notes and tasks via HubspotEngagementOperator
ActivityTask / Event (SalesforceActivityOperator)Engagement (HubspotEngagementOperator)
Current customer flag ({CUSTOMER_DEFINITION})e.g. Account Type = Customere.g. Lifecycle stage = Customer

Field names vary by setup. Write your own rule for {CUSTOMER_DEFINITION} in plain words.

Google to Microsoft 365 mapping

ConceptGoogle WorkspaceMicrosoft 365
CalendarGoogle Calendar (GoogleCalendarOperator)Outlook calendar operator
EmailGmail (GoogleGmailOperator)Outlook email operator
FilesGoogle Drive (GoogleDriveCoreOperator)OneDrive (Microsoft_OneDrive)
Event UIDiCalUIDiCalUId
Video linkGoogle Meet (or Zoom/Teams link in the event)Teams (or Zoom/Meet link in the event)
Prebuilt skillMeeting-Command-GoogleUse the custom skill

4. Data prerequisites

  • CRM accounts have domains. Each customer account has a website or email domain filled in, and contacts have email addresses.
  • Clear customer flag. Current customers are consistently marked (your {CUSTOMER_DEFINITION}), and prospects/vendors are distinguishable.
  • The clone has its own calendar and inbox ({CLONE_INBOX}), separate from any person's.
  • Knowledge base shared with the clone, including release notes / "what's new" content for the weekly updates.
  • Team habit: hosts ({TEAM_HOSTS}) always add {CLONE_INBOX} to customer meeting invites, including recurring series.
  • Customer meetings include a video link (phone-only and in-person meetings are skipped).

5. Supported meeting platforms

PlatformNotes
Google MeetAllow invited guests to join without asking, or admit manually
ZoomLet invited/authenticated users bypass the waiting room, or admit manually
Microsoft Teams"Who can bypass the lobby" → People I invite, or admit manually

Confirm in your catalog that joinMeeting supports the platform you use.

6. Roles and permissions

WhoNeeds to
Clone admin (owner of the clone in the Clone platform)Attach skills/operators, approve the plan, save the Meeting Command skill, create/approve the scheduled task, set follow-up to owner-only
Connection owner(s)Complete OAuth sign-in for calendar, email, Salesforce or HubSpot, and Linear (often the clone admin; the CRM may require a CRM admin to grant a read-only user/app)
Knowledge base ownerShare the relevant folders/spaces with the clone
Meeting platform adminEnable auto-admit for invited guests if it's controlled org-wide
Meeting hosts ({TEAM_HOSTS})Add the clone to invites; admit it if needed; share the infographic

7. Estimated setup time

StepTime
Pre-flight check (this doc)5–10 min
Clone discovery + placeholders + plan10–15 min
Your sign-ins, sharing and meeting settings15–30 min
Save skill + scheduled task5–10 min
Test run15 min
Total45–90 min

8. Pre-flight checklist

  • I'm the clone admin (or have one available)
  • My clone has its own calendar and inbox
  • Calendar operator (Google or Outlook) attached (or can be)
  • Email operator (Gmail or Outlook) attached (or can be), with send permission
  • joinMeeting available in my catalog
  • Image_Operator available in my catalog
  • I can create scheduled tasks (or the clone can)
  • (Optional) Salesforce or HubSpot operators available and I can sign in with read access
  • (Optional) Linear_Operator available
  • (Google users) Know that Meeting-Command-Google can be attached instead of the custom skill
  • (Optional) Knowledge base ready to share with the clone
  • I know my {CUSTOMER_DEFINITION}
  • I've decided {BRIEFING_RECIPIENTS} and {RUN_TIME}
  • I can change auto-admit / lobby settings (or know who can)
  • I have a test contact email (not a real customer) for the test run

9. You're ready when…

  • ✅ Every required item in section 1 is attached and its connection is signed in.
  • ✅ You have answers for all seven placeholders.
  • ✅ Salesforce or HubSpot (or a fallback domain list) clearly identifies current customers.
  • ✅ You know how the clone will get into meetings (auto-admit or manual admit).
  • ✅ Follow-up recaps are set to owner-only.
  • ✅ You've set aside ~15 minutes today for the test run.

Then download CLONE-INSTRUCTIONS.md and give it to your clone.

Was this use case helpful?