Walk into every meeting prepared, without the prep
Each morning your clone researches today's meetings, emails one briefing and joins the calls you pick.
Every weekday your clone looks at today's Google Calendar, researches the people and companies you're meeting from the web, your CRM, past email, transcripts and docs, and sends one briefing with context and talking points. It can also join the calls you choose. Google Workspace only.
What your clone does
Prepping every meeting by hand eats an hour a day, and skipping it shows. Your clone does the homework before you're out of bed.
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
Join Meeting), 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 (Google Gmail Operator), past transcripts (Meeting Archive), docs (Google Drive Core Operator), 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.
Who it helps
- Sales reps with back-to-back external calls.
- Leadership with many meetings and little prep time.
- Customer Success managers across many accounts.
How it runs
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 preparedSet it up, step by step
- Check requirements (5 min)
- Hand CLONE-INSTRUCTIONS.md to your clone"Set this up. Show me a plan first."
- Approve the planThe clone attaches Meeting Command Google via the platform.
- Connect Google(Calendar, Gmail, Drive) and optionally Salesforce or HubSpot. You sign in; the clone needs no passwords.
- Test on demand"Run Meeting Command for today."
- Schedulea weekday morning task (prompt in CLONE-INSTRUCTIONS.md, for example: Run Meeting Command for today: email my briefing to {BRIEFINGRECIPIENTS} and join {JOINRULE}).
- Join setup invite the clone to the meetings it should join, or let it join by link. Set meeting follow-ups to owner-only.
The README has the full walkthrough. The Clone Instructions tell your clone exactly what to do.
Before you start
| # | Skill / operator (exact name) | Used for | Required? |
|---|---|---|---|
| 1 | Meeting Command Google (prebuilt skill) | The daily briefing and joining | Required |
| 2 | Google Calendar Operator | Today's meetings and attendees | Required |
| 3 | Google Gmail Operator | Prior email context; sends the briefing | Required |
| 4 | Join Meeting | Joining calls (follow-up owner-only) | Required to join |
| 5 | Google Drive Core Operator | Related docs | Optional |
| 6 | Salesforce operators (Salesforce Account Operator, Salesforce Contact Operator, Salesforce Opportunity Operator, Salesforce Activity Operator) or HubSpot operators (HubSpot Company Operator, HubSpot Contact Operator, HubSpot Deal Operator, HubSpot Engagement Operator) | Company, contact and deal context | Optional |
| 7 | Meeting Archive | Past transcripts | Optional |
| 8 | Search Knowledge | Knowledge base | Optional |
| 9 | platform | Attach the skill, schedule | Required |
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.
Good to know
- 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.
Questions, answered
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 {JOINRULE}.
Does it change my calendar?
No.
Ready when you are. So is your clone.
Build your clone, paste in the Daily Meeting Briefing & Auto-Attend instructions, and approve the plan it shows you.