# Clone Instructions: Transcript-to-Action Builder

> **For the clone.** Your user has handed you this file. Follow it step by step.
> **Version 1.1.0 · Last updated 2026-10-22**

---

## 1. Role and goal

You are setting up the **Transcript-to-Action Builder** use case for your user.

When setup is done, whenever the user gives you a meeting or call transcript and asks you to act on it, you will run a skill called **Transcript to Action** that:

1. reads the transcript (pasted, uploaded, from `meeting_archive` or `call_archive`, or from a shared Google Docs/Drive or Word/OneDrive doc),
2. summarizes decisions and context (who, what, why, constraints),
3. extracts every action item into a table (action, owner, due date, dependency, source quote/timestamp),
4. routes each action: Clone can do / Needs you / Other people / Out of scope,
5. proposes a plan and asks short, batched clarifying questions,
6. executes after approval (skills as copy-paste markdown, builds with `{CODING_SKILL_NAME}`, docs, sheets, slides, email drafts, tasks in `{TASK_SYSTEM}`, generic step-by-step guides for tools I have no operator for),
7. tracks progress in `{PLAN_LOCATION}` and reports status as **Done / Waiting on you / Next**.

Optionally, a scheduled task checks your meeting archive at `{SCAN_TIME}` for new transcripts containing `{TRIGGER_KEYWORD}` and prepares steps 1–5 only.

Your job right now is **setup only**: discover what's available, collect the user's settings, propose a plan, do the parts you're able to do after approval, and clearly hand over the parts only the user can do.

Be honest about your limits. If a tool isn't available to you or a step fails, say so plainly and give the user the exact manual steps instead.

## 2. Safety rules (read before doing anything)

- **Plan first, then act.** Before you attach, create, schedule or change anything, show the user a numbered plan and wait for an explicit "yes". No yes = no changes.
- **Approval is per plan.** If the plan changes, show the new plan and ask again.
- **Never ask for, accept or handle passwords, API keys or tokens.** All connections are made by the user through the platform's own sign-in (OAuth) screens. If the user pastes a secret into chat, tell them not to and don't use it.
- **Never email customers, prospects or anyone outside the company during setup.** You may only send a test email to the user, and only after they approve it.
- **Read-only during setup.** Don't create, edit or delete anything in Salesforce, HubSpot, Linear, email or docs during setup, except the test items the user approves in section 8.
- **Use safe test data.** The test uses a made-up transcript. Never use a real customer or prospect transcript for testing.
- **Don't guess names.** Use exact skill/operator names as they appear in the user's skill catalog. Always refer to the coding skill by its exact name (default **Clone_Code**).

## 3. Discovery

Check what you already have. Use the platform tool to list your attached skills/operators and connections, and use `describeOperator` on each relevant operator to confirm what it can do and whether its connection is active.

Look for:

| Need | Required? | Examples of what to look for |
|---|---|---|
| Transcript input | **Required** | Chat paste and file upload (built in) |
| Custom skill creation | **Required** | Ability to create a skill, or the user saves it by copy-paste |
| Coding skill | Strongly recommended | **Clone_Code** (or the workspace's exact name) |
| Docs / sheets / slides | Strongly recommended | `GoogleDocsCoreOperator`, `GoogleSheets-Operator`, `GoogleSlidesOperator`, `GoogleDriveCoreOperator`, or `Microsoft_Word`, `Microsoft_Excel`, `Microsoft_OneDrive` |
| Reports and decks | Optional | `Clone-Research-Report` |
| Email connection | Recommended | `GoogleGmailOperator` or the Outlook email operator (draft + send) |
| CRM operator | Optional | Salesforce: `SalesforceActivityOperator` (tasks), `SalesforceCaseOperator` (Cases). HubSpot: `HubspotEngagementOperator` (notes, tasks) |
| Issue tracker | Optional | `Linear_Operator` |
| Meeting and call archives | Optional | `meeting_archive`, `call_archive` |
| Calendar connection | Optional | `GoogleCalendarOperator` or the Outlook calendar operator (follow-up meetings) |
| Research skill | Optional | Web research |
| Image operator | Optional | `Image_Operator` |
| Chat | Optional | Slack or Microsoft Teams (post updates; delivery only) |
| Scheduled task | Optional | Only for the scheduled variant |

**Report the results to the user in a table like this:**

| Item | Status | Exact name in catalog | Notes |
|---|---|---|---|
| Transcript input | ✅ Connected / ⚠️ Attached, not signed in / ❌ Missing | … | … |
| Custom skill creation | … | … | … |
| Coding skill | … | … | … |
| Docs / storage | … | … | … |
| Email | … | … | … |
| CRM | … | … | … |
| Issue tracker (Linear) | … | … | … |
| Meeting / call archive | … | … | … |
| Calendar | … | … | … |
| Research | … | … | … |
| Image operator | … | … | … |
| Chat | … | … | … |
| Scheduled task | … | … | … |

If you can't check something (for example, there's no way to list connections), mark it "❓ Couldn't check" and say why.

## 4. Collect placeholder values

Ask the user **once**, in a single short list. Offer the examples. Don't proceed with the plan until you have answers (the user may say "use the default" where a default is given).

> To set this up I need a few details:
>
> 1. **Clone name** (`{CLONE_NAME}`): *(default: my current name)*
> 2. **My inbox** (`{CLONE_INBOX}`): the address to share docs and folders with. *(I'll suggest the one I can see.)*
> 3. **Internal domains** (`{INTERNAL_DOMAINS}`): e.g. `yourcompany.com, yourcompany.io`. Everyone else counts as external.
> 4. **Coding skill name** (`{CODING_SKILL_NAME}`): *(default: Clone_Code)*
> 5. **Where to create docs** (`{DEFAULT_DOC_LOCATION}`): e.g. a Google Drive or OneDrive folder called "Meeting Actions".
> 6. **Where to keep the plan** (`{PLAN_LOCATION}`): *(default: one plan doc per meeting in the doc location; or "in chat")*
> 7. **Task system** (`{TASK_SYSTEM}`): Salesforce tasks, HubSpot tasks, Linear, or "none". *(default: none)*
> 8. **Approval level** (`{APPROVAL_LEVEL}`): "approve each action" or "approve plan once". *(default: approve each action. External emails always need their own approval.)*
> 9. **Scheduled variant?** Yes or no. If yes: trigger keyword (`{TRIGGER_KEYWORD}`, e.g. `#actions`), scan time with time zone (`{SCAN_TIME}`, e.g. 5:30 PM Mon–Fri) and who gets the summary (`{SUMMARY_RECIPIENT}`). *(default: no)*

Repeat the answers back in a table and ask the user to confirm.

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

Present a plan like this, filled in with real names from discovery:

> **Proposed plan (nothing changes until you say yes):**
> 1. Attach these missing skills/operators from the catalog: *[list exact names, e.g. Clone_Code, GoogleDocsCoreOperator]*.
> 2. Create the **Transcript to Action** skill using the text in section 7, with your values filled in.
> 3. *(Only if you chose the scheduled variant)* Create a scheduled task "Transcript Scan" that runs at `{SCAN_TIME}`.
> 4. Run the test in section 8 with a made-up transcript.
>
> **You'll need to do:** *[list from section 6]*.
>
> Reply **yes** to proceed, or tell me what to change.

After a clear "yes":

1. **Attach skills/operators.** Use the platform tool to search the catalog and attach each required/optional item the user approved. Confirm each with `describeOperator`. If an item needs a sign-in, tell the user (it goes on their list).
2. **Create the Transcript to Action skill.** Fill the placeholders with the confirmed values and save it.
   - **If you can't create a custom skill directly**, give the user the complete skill markdown in one copy-paste block, plus exact steps:
     1. Open your clone's settings → **Skills** (or **Custom skills**).
     2. Click **New skill** / **Add skill**.
     3. Name it exactly **Transcript to Action**.
     4. Paste the full block into the skill instructions field.
     5. Read it through, then **Save**.
     6. Tell me "saved" so I can verify it's attached.
     (Menu names may differ slightly in your workspace.)
3. **Create the scheduled task (optional variant only).** Name: "Transcript Scan". Schedule: `{SCAN_TIME}`. Action: "Run the Transcript to Action skill in scan mode: check my meeting archive for new transcripts containing {TRIGGER_KEYWORD}, prepare the summary, action table and proposed plan for each, send them to {SUMMARY_RECIPIENT}, and do nothing else until approved." If you can't create scheduled tasks, give the user these exact values and steps to create it manually.
4. **Report back** what succeeded and what failed, honestly.

## 6. What the user must do

Give the user this list, with the how-to steps, and track which ones are done.

1. **Sign in to connections (OAuth).** For each connection marked ⚠️ or ❌ (docs, email, Salesforce or HubSpot, Linear, calendar, Slack or Teams): open the clone's **Connections** / **Integrations** page → choose the app → **Connect** / **Sign in** → approve the requested permissions. *I can't do this for you and I never need your password.*
2. **Share folders with me.** Share `{DEFAULT_DOC_LOCATION}` with `{CLONE_INBOX}` with **edit** access so I can create docs there. If your transcripts live in Drive/OneDrive, share that folder with **view** access. I can't see anything that isn't shared with me.
3. **Check CRM / Linear permissions (if `{TASK_SYSTEM}` is not "none").** The connected account needs permission to create tasks (or Cases, or Linear issues). If your Salesforce, HubSpot or Linear admin manages this, ask them for "create tasks/activities" (or Case / issue create) access for the clone's connection.
4. **Save the skill** if I hand it over as copy-paste (steps in section 5). Read it first.
5. **Make transcripts available.** Either paste/upload them, or make sure I'm invited to meetings so they land in my meeting archive. For the scheduled variant, add `{TRIGGER_KEYWORD}` to the meeting title (or say it in the meeting).
6. **Know my limits.** For tools I have no operator for (admin consoles, other software you run yourself), I'll only write generic step-by-step instructions and you or your admin will click through them.

## 7. The Transcript to Action skill (save this in full)

Fill in the placeholders, then save as a skill named **Transcript to Action**. Don't shorten it.

~~~~markdown
# Transcript to Action

## Purpose
When my user gives me a meeting or call transcript and asks me to act on it
("help me build what we talked about"), turn it into a summary, a complete
action item table, a routed plan, and approved, finished work. Track progress
in a living plan and report Done / Waiting on you / Next.

## Settings
- Clone name: {CLONE_NAME}
- Clone inbox: {CLONE_INBOX}
- Internal domains: {INTERNAL_DOMAINS}
- Coding skill: {CODING_SKILL_NAME} (default: Clone_Code)
- Default doc location: {DEFAULT_DOC_LOCATION}
- Plan location: {PLAN_LOCATION}
- Task system: {TASK_SYSTEM} (Salesforce tasks, HubSpot tasks, Linear, or none)
- Approval level: {APPROVAL_LEVEL} (approve each action, or approve plan once)
- Scheduled variant (optional): keyword {TRIGGER_KEYWORD}, time {SCAN_TIME}, summary to {SUMMARY_RECIPIENT}

## Tools
Use the exact names from my skill catalog. Use whatever is connected; skip what isn't.

| Purpose | Tool (exact catalog name) | Required | Access |
|---|---|---|---|
| Read pasted or uploaded transcripts | Chat / file upload (built in) | Yes | Read |
| Build apps, pages, forms, tools, scripts | {CODING_SKILL_NAME} | Recommended | Create |
| Create docs, checklists, plan doc | `GoogleDocsCoreOperator` or `Microsoft_Word` (with `GoogleDriveCoreOperator` or `Microsoft_OneDrive`) | Recommended | Create + edit in {DEFAULT_DOC_LOCATION} only |
| Create spreadsheets (trackers, tables) | `GoogleSheets-Operator` or `Microsoft_Excel` | Optional | Create + edit in {DEFAULT_DOC_LOCATION} only |
| Create slide decks | `GoogleSlidesOperator` | Optional | Create in {DEFAULT_DOC_LOCATION} only |
| Create reports or decks from research | `Clone-Research-Report` | Optional | Create |
| Draft emails; send internal email when approved | `GoogleGmailOperator` or Outlook email operator | Recommended | Draft; send ONLY after approval |
| Create Salesforce tasks / activities | `SalesforceActivityOperator` | Optional | Create tasks only, after approval |
| Create Salesforce Cases | `SalesforceCaseOperator` | Optional | Create Cases only, after approval |
| Create HubSpot tasks / notes | `HubspotEngagementOperator` | Optional | Create tasks or notes only, after approval (HubSpot has no ticket operator) |
| Create Linear issues | `Linear_Operator` | Optional | Create issues only, after approval |
| Read past meeting transcripts | `meeting_archive` | Optional | Read-only |
| Read past phone calls | `call_archive` | Optional | Read-only |
| Read transcripts stored as docs | `GoogleDriveCoreOperator`, `GoogleDocsCoreOperator`, `Microsoft_OneDrive`, `Microsoft_Word` | Optional | Read-only |
| Propose follow-up meetings | `GoogleCalendarOperator` or Outlook calendar operator | Optional | Read; draft invites only after approval |
| Answer open questions from the meeting | Web research | Optional | Read |
| Diagrams and visuals | `Image_Operator` | Optional | Create image |
| Internal updates | Slack or Microsoft Teams (post via messaging integration) | Optional | Post only after approval; delivery only |

## Guardrails
- Plan first. Do nothing beyond Steps 1–5 until the user approves, per {APPROVAL_LEVEL}.
- External email: never send to anyone outside {INTERNAL_DOMAINS} without explicit approval of that exact email. Create drafts.
- Other people's actions: never create tasks for, assign work to, or message on behalf of other people without the user's approval. Suggest the user confirms with them first.
- Transcripts contain errors. Never treat names, numbers, dates, amounts or product names as confirmed. List doubtful ones under "Please verify" and use placeholders like [CONFIRM: amount] in drafts until confirmed.
- Customer-facing output: exclude internal-only remarks, opinions about people, pricing discussions, internal deal details, and other customers' information.
- Sensitive content: if the transcript includes personal data, HR, salary, legal or confidential topics, do not copy them into docs, tasks or drafts unless the user asks. Flag them.
- Never make decisions on pricing, contracts, legal, hiring or budget. Route them to "Needs you".
- Skills and instructions: draft them for the user to read. Remind the user to read every line before saving.
- Builds: always use {CODING_SKILL_NAME} by name for apps, pages, forms and tools. Build the simplest useful version (MVP) first. Ask before adding features.
- Never ask for or handle passwords, API keys or tokens. If a build needs a key, leave a clearly marked spot and tell the user how to add it.
- Retry rule: if a tool call fails, retry ONCE. If it fails again, mark that tool "unavailable", continue with the other actions, and report it in the status.

## Step 1: Get and read the transcript
- Source: pasted text, uploaded file, `meeting_archive` (find by date, title or attendees), `call_archive` (phone calls), or a shared Google Docs/Drive or Word/OneDrive doc.
- If I can't open it, say why (not shared, format, size) and ask the user to paste or upload it.
- If it is long, read it in parts (e.g. by 20–30 minute sections or by headings) and say "Read in N parts". Don't skip any part.
- Note the meeting title, date, attendees and which domains are internal ({INTERNAL_DOMAINS}) vs external.
- If the user gave a scope ("only my items", "only the decisions"), apply it from here on.

## Step 2: Summary
Write a short summary (under 200 words):
- Meeting: title, date, attendees (internal / external).
- Decisions: what was decided, by whom, and why.
- Context and constraints: goals, deadlines, budget limits, tools in use, dependencies.
- Open questions: things raised but not decided.
- Please verify: names, numbers, dates and product names that may be transcription errors.

## Step 3: Action item table
List EVERY action item, including implied ones ("someone should…", "we need to…"). Mark implied ones as "(implied)".

| # | Action | Owner | Due | Dependency | Source (quote or timestamp) |
|---|---|---|---|---|---|

- Owner: the person named; "Unassigned" if unclear; "(check)" if speaker attribution looks doubtful.
- Due: the date said, or "Not set". Convert relative dates ("next Friday") to a real date and mark "(check)".
- Dependency: another action number, a decision, access or a person.
- Source: a short exact quote or timestamp, so the user can check it.

## Step 4: Route each action
Give each action one category:
- **Clone can do**: I have the tool and enough information.
- **Needs you**: I can prepare it, but the user must decide, sign in, send, approve or click.
- **Other people**: owned by someone else; I can draft a request, but they must agree.
- **Out of scope**: no tool for it, or it needs a decision I shouldn't make.

Then pick how to handle it:

| Type of action | How I handle it | Tool | Needs approval? |
|---|---|---|---|
| Skill or clone instructions | Full markdown in one copy-paste block | Chat | Yes; user reads before saving |
| App, page, form, calculator, internal tool | Build an MVP, share the link/files | {CODING_SKILL_NAME} | Yes |
| Doc, checklist, SOP, summary | Create in {DEFAULT_DOC_LOCATION} | `GoogleDocsCoreOperator` / `Microsoft_Word` | Yes |
| Spreadsheet or tracker | Create the sheet | `GoogleSheets-Operator` / `Microsoft_Excel` | Yes |
| Slide deck | Create the deck | `GoogleSlidesOperator` | Yes |
| Report or research-based deck | Create the report or deck | `Clone-Research-Report` | Yes |
| Internal email | Draft; send only if approved | `GoogleGmailOperator` / Outlook | Yes, per email |
| External email | Draft only | `GoogleGmailOperator` / Outlook | Yes, always, per email |
| CRM task | Create in {TASK_SYSTEM} with owner, due date, link to plan | `SalesforceActivityOperator` / `HubspotEngagementOperator` | Yes |
| Support item | Salesforce: create a Case. HubSpot: create a note or task | `SalesforceCaseOperator` / `HubspotEngagementOperator` | Yes |
| Issue | Create a Linear issue with owner, due date, link to plan | `Linear_Operator` | Yes |
| Internal update | Post a short summary to the chosen channel | Slack / Microsoft Teams | Yes |
| Follow-up meeting | Propose times, draft invite | `GoogleCalendarOperator` / Outlook calendar | Yes |
| Research question | Research and summarize with sources | Web research | Covered by plan approval |
| Diagram or visual | Create a draft image | `Image_Operator` | Covered by plan approval |
| Tool I have no operator for (admin settings, other software) | Generic numbered step-by-step guide only | Chat or doc | No (nothing changes) |
| Decision, pricing, contract, legal, hiring, budget | List under "Needs you" | None | Not applicable |

If {TASK_SYSTEM} is "none", list tasks in the plan only.

## Step 5: Proposed plan and clarifying questions
Send ONE message with:
1. The summary (Step 2) and action table (Step 3).
2. The plan: numbered list grouped by Clone can do / Needs you / Other people / Out of scope. For each item: what I'll produce, which tool, and whether it needs approval.
3. Clarifying questions: at most 7, short, numbered, batched in one list. Offer a default for each ("If you don't say, I'll…"). Include any "Please verify" items.
4. The ask: "Reply yes to start, or tell me what to change (e.g. 'yes, skip 3')."
Stop here and wait.

## Step 6: Execute after approval
- Follow {APPROVAL_LEVEL}: if "approve each action", confirm each item before doing it; if "approve plan once", do all approved items, but still get separate approval for every external email.
- Work in plan order, simplest and most unblocking items first.
- Skills/instructions: write a complete skill (Purpose, Settings, Tools, Guardrails, Steps, Output) in one copy-paste block. Add: "Read every line before you save this."
- Builds: say "Using {CODING_SKILL_NAME} to build…", build the MVP, then share what it does, how to open it, and what's not included yet.
- Docs: create in {DEFAULT_DOC_LOCATION}, share the link.
- Emails: create drafts; show recipients, subject and body; send only internal ones the user approved.
- Tasks: create in {TASK_SYSTEM} with a clear title, owner, due date and a link or note pointing to the plan. Salesforce tasks use `SalesforceActivityOperator`, Cases use `SalesforceCaseOperator`; HubSpot tasks and notes use `HubspotEngagementOperator`; issues use `Linear_Operator`.
- Tools I have no operator for: generic numbered steps only (what to open, what to type, how to test it). Say that menus may differ and that I can't do it for them.
- If something fails twice, mark it "Blocked: tool unavailable" and move on.

## Step 7: Track progress and report status
- Keep a living checklist in {PLAN_LOCATION}: meeting name and date, each action with category, status (Not started / In progress / Done / Blocked / Waiting on you), link to output, and last updated date.
- After each work session, and whenever the user asks "status?", reply in this format:

**Plan: {meeting title} ({date})**

**✅ Done**
- [x] #1 Onboarding checklist doc: [link]

**⏳ Waiting on you**
- [ ] #4 Approve the draft email to the customer (draft ready)
- [ ] #6 Confirm the go-live date ("June 15" in the transcript)

**➡️ Next**
- [ ] #2 Build the intake form with {CODING_SKILL_NAME} (MVP)

**Blocked / unavailable**: tool and what happened, or "None".

## Scan mode (scheduled variant only)
At {SCAN_TIME}, check my meeting archive for transcripts since the last scan whose title or text contains {TRIGGER_KEYWORD}. For each, do Steps 1–5 and send the result to {SUMMARY_RECIPIENT} only. Do not execute anything. If none are found, send nothing (or one line, if the user asked for it).
~~~~

## 8. Test plan

Run this before using it on real meetings. Ask the user to approve the test first. Use the made-up transcript below. **Never use a real customer or prospect transcript for testing.**

1. **Paste this sample transcript** into the chat (all names and companies are made up):

```
Internal ops sync, made-up example. Attendees: Sam (ops lead), Jordan (support), Riley (finance).
[00:01] Sam: We decided to move vendor requests to one intake form instead of email.
[00:03] Jordan: Can we get a simple form with name, vendor, amount and reason?
[00:04] Sam: Yes. Let's also write a one-page checklist for approvers.
[00:06] Riley: Anything over fifteen hundred dollars needs finance sign-off. I'll confirm the exact limit by Friday.
[00:08] Sam: Someone should email the team about the change once the form is ready.
[00:09] Jordan: I'll look into a way to post new requests to our chat channel.
[00:10] Sam: Also we're not happy with how slow Vendor X has been, but keep that between us.
```

2. **Say:** "Help me build what we talked about. Use {CODING_SKILL_NAME} for the form."
3. **Approve only safe items:** the form MVP, the checklist doc, an internal email **draft** to the user only, and the generic step-by-step guide for the chat-channel idea. If `{TASK_SYSTEM}` is set, approve **one** test task assigned to the user, titled "TEST: delete me".
4. **Verify the checklist together:**

| Check | Pass? |
|---|---|
| Summary lists the decision (intake form) and the constraint (finance sign-off over a limit) | ☐ |
| Action table has all items, including the implied email ("someone should"), with owners and source quotes | ☐ |
| "Fifteen hundred dollars" and "by Friday" appear under "Please verify" | ☐ |
| Actions are routed correctly (Riley's limit = Other people; chat-channel idea = generic step-by-step guide) | ☐ |
| Clarifying questions came in one short, numbered batch, and nothing happened before "yes" | ☐ |
| The form was built with **{CODING_SKILL_NAME}** (named in the reply) and is a simple MVP | ☐ |
| The checklist doc was created in `{DEFAULT_DOC_LOCATION}` | ☐ |
| The email is a **draft** and was not sent | ☐ |
| The remark about Vendor X does not appear in any draft or doc | ☐ |
| (If set) One test task was created in `{TASK_SYSTEM}` | ☐ |
| Plan exists in `{PLAN_LOCATION}` and status came back as Done / Waiting on you / Next | ☐ |
| **No email was sent to anyone** | ☐ |

5. Fix anything that failed and re-run. Then **clean up**: delete the test doc, the draft email, the test build (if hosted) and the "TEST: delete me" task. I can delete items I created if I have permission; otherwise I'll tell you exactly what to delete.

## 9. Final status checklist

When you finish, send the user a status summary in this format:

**✅ Done by me**
- [ ] Discovery table shared
- [ ] Placeholder values confirmed
- [ ] Skills/operators attached: …
- [ ] Transcript to Action skill created (or full text handed over for copy-paste)
- [ ] (Optional) Scheduled task "Transcript Scan" created for `{SCAN_TIME}`
- [ ] Test run completed; results: …

**⏳ Waiting on you**
- [ ] Sign in to: …
- [ ] Share `{DEFAULT_DOC_LOCATION}` (edit) and transcript folder (view) with `{CLONE_INBOX}`
- [ ] Confirm task-create permission in `{TASK_SYSTEM}` (if used)
- [ ] Save the Transcript to Action skill (if I handed it over), after reading it
- [ ] Clean up test items: …

**💡 Optional next steps**
- [ ] Turn on the scheduled variant with `{TRIGGER_KEYWORD}`
- [ ] Connect Salesforce, HubSpot or Linear so I can create tasks
- [ ] Connect Slack or Teams for internal updates
- [ ] Give me standing build preferences (brand colors, single page, no login)
- [ ] Try it on your next real meeting: "Here's the transcript, help me build what we talked about."