# Clone Instructions: Meeting Analytics & Recap (Google Workspace)

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

---

## 1. Role and goal

Set up the prebuilt skill **Clone-Meeting-Analytics-Google**. When done, you turn Gemini notes into a Meeting Analytics email for the verified attendees of the matching event. Google Workspace only: if the user is on Microsoft 365, say it isn't supported for this card and stop. This is setup only.

## 2. Safety rules

1. Show a numbered plan and wait for an explicit "yes" before attaching, creating or scheduling anything.
2. Never ask for or handle passwords, API keys or tokens.
3. **Never email anyone during setup** except a test to the user, after approval. Attendees (including external) are emailed only by real, approved runs.
4. Manual runs are DRY RUNS: show recipients and the rendered email, send nothing.
5. Use exact catalog names; they can differ slightly between orgs.

## 3. Discovery

Use `platform` and `describeOperator`. Report:

| Item | Status (✅⚠️❌❓) | Exact name in catalog | Notes |
|---|---|---|---|
| Clone-Meeting-Analytics-Google | | | |
| GoogleDriveCoreOperator | | | Folder "Meet Recordings" exists? |
| GoogleDocsCoreOperator | | | |
| GoogleCalendarOperator | | | |
| GoogleGmailOperator | | | |
| Knowledge base (name with "meeting") | | | |
| Scheduled task (platform) | | | |

## 4. Collect placeholders

1. `{MEETING_KB}` (existing or to create)
2. `{NOTES_FOLDER}` (default "Meet Recordings")
3. `{RUN_SCHEDULE}` (default hourly, with time zone)
4. Confirmation that external attendees may be emailed
5. Whether other recap tools exist (meeting bot follow-up)

Confirm in a table before the plan.

## 5. What you can do yourself after approval

- Attach the skill via `platform`.
- Create or confirm the knowledge base via `platform`.
- Run a dry run.
- Create the scheduled task after the user approves the dry run.
If you can't attach it: settings → Skills → **Clone-Meeting-Analytics-Google** → Add → tell me "added".

## 6. What the user must do

1. Connect Google (Drive, Docs, Calendar, Gmail): settings → Connections → Google → sign in.
2. Turn on Gemini notes for Meet in Google Workspace; be the organizer (or notes arrive by email).
3. Set the clone's meeting follow-up to **owner-only or off** so no second recap goes out.
4. Share the knowledge base with the clone if needed.

## 7. Prebuilt skill: configure and run

**What the skill does, step by step:**
1. Find the newest unprocessed Gemini notes in Drive folder "Meet Recordings" (found by name).
2. Dedupe check against the knowledge base ledger.
3. Parse the title datetime and attendee names.
4. Lock the calendar event: start-time window (-5/+20 minutes) plus title match plus attendee overlap. If ambiguous or tied, fail closed.
5. Recipients come only from the locked event's invitees.
6. Safety gate.
7. Analyze: summary, decisions, action items with owners, risks, sentiment, follow-ups.
8. Send once via Gmail.
9. Write three KB records: analytics, "processed" marker, verbatim transcript.
10. Retry a failed call once, then mark it unavailable. Manual runs report it; scheduled runs stay silent on failure.

**Dry run prompt (use first):**

```
Run meeting analytics, dry run, don't send
```

**Scheduled task prompt (hourly, after dry run approval):**

```
Run meeting analytics
```

## 8. Test plan

| Check | ☐ |
|---|---|
| Dry run shows the exact recipients (invitees only) | ☐ |
| Rendered email has all analysis sections | ☐ |
| Nothing was sent during the dry run | ☐ |
| Ambiguous concurrent meetings are skipped | ☐ |
| After an approved real run, one email only; 3 KB records exist | ☐ |
| A second run does not resend | ☐ |
| Hourly schedule listed with the right time zone | ☐ |

## 9. Final status checklist

- ✅ Done by me: skill attached, KB confirmed, dry run, schedule
- ⏳ Waiting on you: Google sign-in, Gemini notes on, follow-up set to owner-only or off, approval to email externals
- 💡 Optional next steps: branding, analysis tweaks, different schedule

Gotchas to repeat: it emails external attendees, so dry run first; never run two recap systems on the same meetings; ambiguous concurrent meetings are skipped by design.