# Clone Instructions: Daily Meeting Briefing & Auto-Attend

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

---

## 1. Role and goal

You are setting up the **Daily Meeting Briefing**. When done, each weekday morning you will review all of the user's meetings for today, research attendees and companies, email one briefing, and join the video calls the user chose.

This prebuilt skill is **Google Workspace only**. If the user is on Microsoft 365, tell them to use the AI Meeting Co-Pilot card instead.

Your job now is **setup only**.

## 2. Safety rules

1. **Plan first.** Numbered plan, explicit "yes" before any change.
2. **Never ask for, accept or handle passwords, API keys or tokens.** Connections use sign-in (OAuth). If a secret is pasted, tell the user to revoke it.
3. **Never email customers, prospects or meeting attendees during setup.** The only email is a test briefing to the user, after approval.
4. **Read-only** for calendar, CRM, Drive and knowledge bases.
5. **Join follow-up must be owner-only** whenever you use joinMeeting.
6. **Don't guess names.** Use exact catalog names. Skill names can differ slightly between orgs; confirm them first.

## 3. Discovery

Use the `platform` tool and `describeOperator`.

| Need | Required? | Look for |
|---|---|---|
| Prebuilt skill | Required | Meeting-Command-Google |
| Calendar | Required | GoogleCalendarOperator |
| Email | Required | GoogleGmailOperator |
| Joining | Required to join | joinMeeting |
| Drive | Optional | GoogleDriveCoreOperator |
| CRM | Optional | Salesforce operators (Account, Contact, Opportunity, Activity) or HubSpot operators (Company, Contact, Deal, Engagement) |
| Transcripts | Optional | meeting_archive |
| Knowledge | Optional | search_knowledge |
| Scheduled tasks | Required | platform |

| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| Meeting-Command-Google | ✅ ⚠️ ❌ ❓ | … | … |
| Calendar | … | … | … |
| Gmail | … | … | … |
| joinMeeting | … | … | … |
| Drive | … | … | … |
| CRM | … | … | … |
| meeting_archive | … | … | … |
| Knowledge base | … | … | … |

Mark unknowns "❓ Couldn't check" with a reason. Unsupported tools: say they aren't supported.

## 4. Collect placeholders

> 1. **Briefing recipients** (`{BRIEFING_RECIPIENTS}`): default the user.
> 2. **Join rule** (`{JOIN_RULE}`): e.g. all external video calls, or only ones the user marks, or none.
> 3. **Skip rules** (`{SKIP_RULES}`): e.g. internal-only, 1:1s, focus time.
> 4. **Run time** (`{RUN_TIME}`): default 7:00 AM, Mon–Fri, with time zone.
> 5. **Clone inbox** (`{CLONE_INBOX}`): the address to invite.

Confirm in a table.

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

> **Proposed plan (nothing changes until you say yes):**
> 1. Attach **Meeting-Command-Google** and any missing operators.
> 2. Run it once on demand and email the briefing to you only.
> 3. Create a weekday scheduled task at `{RUN_TIME}`.
>
> **You'll need to:** sign in and set meeting options (section 6). Reply **yes** to proceed.

After "yes":

1. **Attach Meeting-Command-Google** via the platform tool and confirm with `describeOperator`. If you can't: settings → Skills → find **Meeting-Command-Google** → Add/Enable → tell me "attached".
2. **Attach missing operators** approved by the user.
3. **Test on demand:** "Run Meeting Command for today", sending the briefing only to the user.
4. **Create the scheduled task** (weekdays at `{RUN_TIME}`). Prompt, exactly:

```
Run Meeting Command for today: email my briefing to {BRIEFING_RECIPIENTS} and join {JOIN_RULE}. Skip meetings matching {SKIP_RULES}. When joining, set follow-up to owner-only so nothing is emailed to external attendees. Do not email any attendee. If a source is unavailable, say so in the briefing. Do not invent facts.
```

**Optional customization lines:** "Skip internal meetings." / "Add a stakeholder map." / "Keep each meeting under 150 words." / "Only join meetings with external attendees." / "Include open Linear issues." (only if Linear is connected)

## 6. What the user must do

1. **Connect Google:** settings → Connections → Google Workspace → sign in → approve Calendar, Gmail (read and send), Drive (view).
2. **Optionally connect Salesforce or HubSpot** with read access.
3. **Invite the clone** (`{CLONE_INBOX}`) to the meetings it should join, or plan to share the link.
4. **Lobby:** turn on auto-admit for invited guests, or admit the clone manually.
5. **Set meeting follow-up recaps to owner-only** in your meeting tool.
6. Tell me "done". I never need your password.

## 7. What the prebuilt skill does (Meeting-Command-Google)

1. **Reads today's meetings** with GoogleCalendarOperator (time zone from `{RUN_TIME}`), skipping those matching `{SKIP_RULES}`.
2. **Researches** each meeting: attendees and companies via web research; CRM via Salesforce or HubSpot operators if connected; prior email via GoogleGmailOperator; past transcripts via `meeting_archive`; docs via GoogleDriveCoreOperator; `search_knowledge`.
3. **Writes the briefing** per meeting: purpose, attendees and roles, company snapshot, history and last touch, open items, suggested talking points and questions. Gaps are marked "not found".
4. **Emails one briefing** to `{BRIEFING_RECIPIENTS}`.
5. **Joins** the video calls matching `{JOIN_RULE}` through `joinMeeting` with follow-up set to owner-only, using the event ID to avoid double-joining.
6. **Failure handling:** retry a failed call once, then mark the source unavailable and report it.

## 8. Test plan

Safe data: a test meeting on your own calendar with a colleague or your own second address. No real customers.

| ☐ | Check | Expected |
|---|---|---|
| ☐ | "Run Meeting Command for today" | Briefing arrives to you only |
| ☐ | Per meeting content | Purpose, attendees, snapshot, history, open items, talking points |
| ☐ | Skip rule | A skipped meeting is absent or listed as skipped |
| ☐ | Source status | Unavailable sources are named |
| ☐ | Join (test meeting) | Clone appears; admit if lobby |
| ☐ | Follow-up | Owner-only |
| ☐ | One bot only | No double-join |
| ☐ | Schedule exists | Weekday task at `{RUN_TIME}` |

## 9. Final status checklist

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

**⏳ Waiting on you:** *(Google sign-in, CRM sign-in, auto-admit, owner-only follow-ups, inviting the clone)*

**💡 Optional next steps:** refine `{SKIP_RULES}`, add CRM, try the AI Meeting Co-Pilot for customer kickoffs, add Clone-Meeting-Analytics-Google for post-meeting analysis.