# Requirements: Transcript-to-Action Builder

> **Version 1.1.0 · Last updated 2026-10-22 · Estimated setup time: 20–40 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

Names below are the exact operator and skill names. **Confirm them against your skill catalog** (your clone will report what it finds).

| # | Skill / operator | What it's used for | Notes |
|---|---|---|---|
| 1 | **Transcript input** | Read the transcript you paste or upload | Built in. `meeting_archive`, `call_archive` and Drive/OneDrive docs are optional extras |
| 2 | **Custom skill** (Transcript to Action) | The instructions the clone follows every time | The clone creates it, or you save it by copy-paste |
| 3 | **`Clone_Code`** (coding skill) | Build apps, pages, forms, calculators and small tools | Strongly recommended. Always name it explicitly when asking for a build |
| 4 | **`GoogleDocsCoreOperator`** (with `GoogleDriveCoreOperator`) or **`Microsoft_Word`** (with `Microsoft_OneDrive`) | Create docs, checklists and the living plan | Strongly recommended |
| 5 | **`GoogleGmailOperator`** or the **Outlook email operator** | Draft follow-up emails; send internal ones you approve | Recommended |

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

Without 3–5 the clone can still summarize, extract actions, write skills and give step-by-step guides in chat. It just can't build, file docs or draft emails for you.

> Tools without an operator are not integrations. For those the clone only writes generic step-by-step instructions.

## 2. Required connections and permissions

| Connection | Minimum permission | Why |
|---|---|---|
| Docs / storage (Google or Microsoft 365) | **Edit** in `{DEFAULT_DOC_LOCATION}` only | Create docs, sheets, slides and the plan |
| Docs / storage (transcripts, if stored there) | **View** the transcript folder | Read transcripts |
| Email (Gmail or Outlook) | **Read** + **Draft** (+ **Send** for approved internal emails) | Draft follow-ups; never send externally without approval |
| Salesforce (if used as `{TASK_SYSTEM}`) | **Read** + **Create tasks** (`SalesforceActivityOperator`); **Create Cases** (`SalesforceCaseOperator`) if you want Cases | Create approved tasks and Cases. No edit/delete needed |
| HubSpot (if used as `{TASK_SYSTEM}`) | **Read** + **Create tasks/notes** (`HubspotEngagementOperator`) | Create approved tasks and notes |
| Linear (if used) | **Read** + **Create issues** (`Linear_Operator`) | Create approved issues |
| Calendar (if used) | **Read** + create draft invites | Propose follow-up meetings |
| Slack or Teams (if used) | **Post** in chosen channels | Internal updates, only after approval |

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

## 3. Optional add-ons

| Add-on | Adds | Exact names |
|---|---|---|
| **Meeting and call archives** | Pick a transcript by meeting name/date; enables the scheduled variant | `meeting_archive`, `call_archive` |
| **Sheets and slides** | Trackers, tables, decks | `GoogleSheets-Operator`, `GoogleSlidesOperator`, `Microsoft_Excel` |
| **Reports and decks** | Research-based reports | `Clone-Research-Report` |
| **Salesforce** | Follow-up tasks; support Cases | `SalesforceActivityOperator`, `SalesforceCaseOperator` |
| **HubSpot** | Follow-up tasks and notes | `HubspotEngagementOperator` |
| **Linear** | Issues for product, support or ops work | `Linear_Operator` |
| **Calendar connection** | Propose and draft follow-up meetings | `GoogleCalendarOperator`, Outlook calendar operator |
| **Research** | Answer open questions raised in the meeting, with sources | Web research |
| **Image operator** | Diagrams, process visuals, simple graphics | `Image_Operator` |
| **Slack or Teams** | Post approved internal updates | Messaging integration |
| **Scheduled task** | Scan the archive for `{TRIGGER_KEYWORD}` at `{SCAN_TIME}` | Platform feature |

### CRM concept mapping (Salesforce ⇄ HubSpot)

| Generic concept | Salesforce | HubSpot |
|---|---|---|
| **Account / company** | Account | Company |
| **Contact** | Contact | Contact |
| **Lead** | Lead | Contact (Lifecycle stage = Lead) |
| **Opportunity / deal** | Opportunity | Deal |
| **Support item** | Case (`SalesforceCaseOperator`) | Note or task (`HubspotEngagementOperator`; no ticket operator) |
| **Task / activity** (what the clone creates) | Task (`SalesforceActivityOperator`) | Task (`HubspotEngagementOperator`) |
| **Custom fields** | Custom field (__c) | Custom property |

Field names vary by setup. The clone only creates tasks, Cases and notes; it doesn't edit accounts, deals or custom fields.

### Google Workspace ⇄ Microsoft 365

| Concept | Google Workspace | Microsoft 365 |
|---|---|---|
| Email | `GoogleGmailOperator` (drafts) | Outlook email operator (drafts) |
| Calendar | `GoogleCalendarOperator` | Outlook calendar operator |
| Docs | `GoogleDocsCoreOperator` | `Microsoft_Word` |
| Sheets | `GoogleSheets-Operator` | `Microsoft_Excel` |
| Slides | `GoogleSlidesOperator` | (use `Clone-Research-Report` for decks) |
| Storage | `GoogleDriveCoreOperator` | `Microsoft_OneDrive` |

### Slack ⇄ Teams

| Concept | Slack | Microsoft Teams |
|---|---|---|
| Team space | Channel | Team / Channel |
| Direct message | DM | Chat |

### Tools without an operator (instructions only)

For admin consoles or other software you run yourself, the clone can only write generic numbered instructions. It can't click through them, and they are not integrations.

## 4. Data prerequisites

- [ ] **You can get transcripts** of your meetings (from your meeting tool, the clone's archive, or a notes app) as text, DOCX, PDF or VTT/SRT.
- [ ] **You're allowed to share them** with the clone (check confidentiality, HR or legal restrictions).
- [ ] **A folder for outputs** exists (`{DEFAULT_DOC_LOCATION}`) and can be shared with `{CLONE_INBOX}`.
- [ ] **You know your internal domains** (`{INTERNAL_DOMAINS}`) so the clone can tell internal from external people.
- [ ] (If creating tasks) **Owners exist as users** in Salesforce, HubSpot or Linear, so tasks can be assigned.
- [ ] (Scheduled variant) **The clone attends the meetings** you want scanned, and you use `{TRIGGER_KEYWORD}` in titles.

## 5. Roles and permissions

| Who | Needs to |
|---|---|
| **Clone admin** (owner of the clone in the Clone platform) | Attach skills/operators, approve the plan, save the Transcript to Action skill, create the optional scheduled task |
| **Connection owner(s)** | Complete OAuth sign-in for docs, email, Salesforce, HubSpot, Linear, calendar, Slack or Teams |
| **Salesforce / HubSpot / Linear admin** | Grant the clone's connection permission to create tasks, Cases or issues (if used) |
| **Folder owner** | Share `{DEFAULT_DOC_LOCATION}` (edit) and transcript folder (view) with the clone |
| **Day-to-day user** | Hand over transcripts, answer questions, approve plans and each external email, verify names/numbers/dates |
| **Other action owners** | Agree before work is assigned to them or sent in their name |

## 6. Estimated setup time

| Step | Time |
|---|---|
| Pre-flight check (this doc) | 5 min |
| Clone discovery + placeholders + plan | 5–10 min |
| Your sign-ins and folder sharing | 5–10 min |
| Save skill (+ optional scheduled task) | 5 min |
| Test run with the sample transcript | 10 min |
| **Total** | **20–40 min** |

## 7. Pre-flight checklist

- [ ] I'm the clone admin (or have one available)
- [ ] I can paste or upload a transcript to my clone
- [ ] `Clone_Code` is available in my catalog
- [ ] `GoogleDocsCoreOperator` or `Microsoft_Word` is available and I can sign in
- [ ] `GoogleGmailOperator` or Outlook is available (for drafts)
- [ ] I've picked `{DEFAULT_DOC_LOCATION}` and `{PLAN_LOCATION}`
- [ ] I know my `{INTERNAL_DOMAINS}`
- [ ] I've decided `{TASK_SYSTEM}` (Salesforce, HubSpot, Linear, or none)
- [ ] I've decided `{APPROVAL_LEVEL}`
- [ ] (Optional) Salesforce, HubSpot or Linear operator available with create permission
- [ ] (Optional) Scheduled variant: `{TRIGGER_KEYWORD}`, `{SCAN_TIME}`, `{SUMMARY_RECIPIENT}` decided
- [ ] I'll use the made-up sample transcript for testing, not a real customer meeting

## 8. You're ready when…

- ✅ Your clone can read a transcript you paste or upload.
- ✅ `Clone_Code` and a docs operator are attached (or you've accepted chat-only output).
- ✅ You have answers for the placeholders (or are happy with the defaults).
- ✅ `{DEFAULT_DOC_LOCATION}` is shared with the clone.
- ✅ You know that external emails always stay drafts until you approve them.
- ✅ You've set aside ~10 minutes for the test run.

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