Clone Support
Use case

Daily Meeting Briefing & Auto-Attend

Every morning your clone preps all of today's meetings, emails one briefing, and joins the calls you choose.

The problem

Walking into meetings without context hurts credibility, and prepping every meeting by hand takes an hour a day.

Daily Meeting Briefing & Auto-Attend

Version 1.0.0 · Last updated 2026-10-22 · Difficulty: Beginner · Setup time: 20–40 minutes

🧩 Based on the prebuilt skill Meeting-Command-Google. You attach it; you don't have to write it.

Every morning your clone reviews all of today's meetings, researches the people and companies, emails you one briefing, and joins the video calls you choose.


1. Overview and value

Walking into a meeting without context costs credibility. Prepping every meeting by hand costs an hour a day.

Each weekday morning, the clone:

  • reviews all of today's meetings on your Google Calendar,
  • researches attendees and companies,
  • emails you one briefing,
  • joins the video calls you choose (via joinMeeting), with follow-up set to owner-only.

Per meeting, the briefing includes: purpose, attendees and roles, company snapshot, history and last touch, open items, and suggested talking points and questions.

Research sources (whatever is connected): web research, Salesforce or HubSpot, prior email (GoogleGmailOperator), past transcripts (meeting_archive), docs (GoogleDriveCoreOperator), and search_knowledge.

Microsoft 365 users: this prebuilt skill is Google-only. Use the custom-skill pattern in the AI Meeting Co-Pilot card instead.

How it differs from AI Meeting Co-Pilot: Co-Pilot is for customer-meeting kickoffs with an infographic. Daily Meeting Briefing is broad prep for all your meetings.


2. Who it's for

  • Sales reps with back-to-back external calls.
  • Leadership with many meetings and little prep time.
  • Customer Success managers across many accounts.

3. How it works

code
 Weekday morning (scheduled task)
              │
              ▼
 ┌──────────────────────────────────────────────────────────┐
 │ Meeting-Command-Google                                   │
 │  1. Read today's meetings (GoogleCalendarOperator)       │
 │  2. Skip any matching {SKIP_RULES}                       │
 │  3. Research each: web · CRM · Gmail · meeting_archive · │
 │     Drive · search_knowledge                             │
 │  4. Email ONE briefing to {BRIEFING_RECIPIENTS}          │
 │  5. joinMeeting for calls matching {JOIN_RULE}           │
 │     (follow-up = owner only)                             │
 └──────────────────────────────────────────────────────────┘
              │
              ▼
   You skim the email, then walk in prepared

4. What the clone does (and never does)

Does: reads your calendar, researches, emails one briefing, joins chosen calls, keeps recaps owner-only.

Never: emails external attendees; edits calendar events, CRM or docs; invents facts (it marks gaps as "not found"); commits to anything in a meeting.

5. Setup walkthrough

  1. Check requirements (5 min).
  2. Hand CLONE-INSTRUCTIONS.md to your clone: "Set this up. Show me a plan first."
  3. Approve the plan. The clone attaches Meeting-Command-Google via the platform.
  4. Connect Google (Calendar, Gmail, Drive) and optionally Salesforce or HubSpot. You sign in; the clone needs no passwords.
  5. Test on demand: "Run Meeting Command for today."
  6. Schedule a weekday morning task (prompt in CLONE-INSTRUCTIONS.md, for example: Run Meeting Command for today: email my briefing to {BRIEFING_RECIPIENTS} and join {JOIN_RULE}).
  7. Join setup: invite the clone to the meetings it should join, or let it join by link. Set meeting follow-ups to owner-only.

6. Placeholders to decide

PlaceholderMeaningExample
{BRIEFING_RECIPIENTS}Who gets the emailyou@yourcompany.com
{JOIN_RULE}Which calls to joinall external video calls; or only meetings I mark "join"
{SKIP_RULES}Meetings to skipinternal-only, 1:1s, focus time, titles containing "Lunch"
{RUN_TIME}Weekday schedule with time zone7:00 AM America/New_York, Mon–Fri
{CLONE_INBOX}Clone's own email to inviteclone@yourcompany.com

7. What to expect

  • Weekday morning: a briefing email with one section per meeting in time order.
  • At meeting time: the clone appears (admit it if there's a lobby).
  • After: any recap goes to the meeting owner only.
  • No meetings today: a short "no meetings" note.

8. Customizing

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

9. Known gotchas

  • The clone must be invited to join, or join via link. If it's not on the invite and no link is available, it can't attend.
  • Waiting room or lobby: admit the clone, or enable auto-admit for invited guests.
  • Owner-only follow-up: keep it that way so externals don't get emails.
  • Double-join: an invite plus a scheduled join can create two bots. Use one method per meeting.
  • Thin research on personal-domain attendees (gmail.com and similar): little can be found reliably.
  • Internal meetings can be skipped with {SKIP_RULES}.
  • Google only. Microsoft 365 users: see AI Meeting Co-Pilot.

10. FAQ

Does it email attendees? No, only your briefing.

Is the CRM required? No, it's optional and adds context.

Can I choose which calls it joins? Yes, via {JOIN_RULE}.

Does it change my calendar? No.

11. Troubleshooting

SymptomLikely causeFix
No briefingTask paused or wrong time zoneCheck the scheduled task
Clone didn't joinNot invited, no link, or lobbyInvite it or admit it
Two bots joinedInvite plus scheduled joinUse one method
Thin research on an attendeePersonal-domain emailAdd context in the CRM or notes
Internal meeting preppedSkip rule missingUpdate {SKIP_RULES}
"CRM unavailable"Connection expiredRe-sign in

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

Paste these instructions into clone chat

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

Requirements

Requirements: Daily Meeting Briefing & Auto-Attend

Version 1.0.0 · Last updated 2026-10-22 · Estimated setup time: 20–40 minutes

🧩 Based on the prebuilt skill Meeting-Command-Google. You attach it; you don't have to write it.


1. Required skills / operators

#Skill / operator (exact name)Used forRequired?
1Meeting-Command-Google (prebuilt skill)The daily briefing and joiningRequired
2GoogleCalendarOperatorToday's meetings and attendeesRequired
3GoogleGmailOperatorPrior email context; sends the briefingRequired
4joinMeetingJoining calls (follow-up owner-only)Required to join
5GoogleDriveCoreOperatorRelated docsOptional
6Salesforce operators (SalesforceAccountOperator, SalesforceContactOperator, SalesforceOpportunityOperator, SalesforceActivityOperator) or HubSpot operators (HubspotCompanyOperator, HubspotContactOperator, HubspotDealOperator, HubspotEngagementOperator)Company, contact and deal contextOptional
7meeting_archivePast transcriptsOptional
8search_knowledgeKnowledge baseOptional
9platformAttach the skill, scheduleRequired

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

Microsoft 365 users: this prebuilt is Google-only. Use the AI Meeting Co-Pilot custom skill pattern.

2. Connections and minimum permissions

ConnectionMinimum permissionWhy
Google CalendarReadToday's meetings
GmailRead + SendContext; send the briefing to {BRIEFING_RECIPIENTS} only
Google DriveViewRelated docs
Salesforce or HubSpotReadContext only, no writes
Knowledge basesView (shared with clone)Notes

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

3. Optional add-ons and CRM mapping

ConceptSalesforceHubSpot
CompanyAccount (SalesforceAccountOperator)Company (HubspotCompanyOperator)
ContactSalesforceContactOperatorHubspotContactOperator
DealOpportunity (SalesforceOpportunityOperator)Deal (HubspotDealOperator)
ActivitySalesforceActivityOperatorHubspotEngagementOperator

4. Data prerequisites

  • Meetings are on the Google Calendar the clone can read.
  • Video meetings have a link (Meet, Zoom or Teams).
  • You decided {JOIN_RULE} and {SKIP_RULES}.
  • The clone has its own inbox {CLONE_INBOX} (to be invited).
  • Meeting follow-up recaps can be set to owner-only.
  • CRM records have domains (optional).

5. Roles and permissions

WhoNeeds to
Clone adminAttach the skill, approve the plan, create the schedule
Connection ownerSign in to Google (and CRM)
Meeting platform adminAllow auto-admit for invited guests, if org-controlled

6. Estimated setup time

StepTime
Pre-flight5 min
Discovery and plan5–10 min
Sign-ins5–15 min
Test and schedule10 min
Total20–40 min

7. Pre-flight checklist

  • I use Google Workspace
  • Meeting-Command-Google is in my catalog
  • I can sign in to Google Calendar, Gmail and Drive
  • joinMeeting is available
  • (Optional) Salesforce or HubSpot can be connected
  • I've chosen {BRIEFING_RECIPIENTS}, {JOIN_RULE}, {SKIP_RULES}, {RUN_TIME}

8. You're ready when…

  • ✅ Meeting-Command-Google is attached and Google is connected.
  • ✅ A test run emailed you a briefing.
  • ✅ Joining works on a test meeting with owner-only follow-up.
  • ✅ The weekday schedule is created.

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

Was this use case helpful?