OpenParable
Skip to content
← Back to skills

Call Recap

Business
call-recap

Call Recap is an Agent Skill for business published in the kortix-ai/suna repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

The per-call runbook for turning a finished sales call's transcript — found in the connected Google Drive folder — into an updated HubSpot deal (or a flagged handoff when no deal matches), filed follow-up tasks in {{linear_team}}, and a drafted recap email — held for the rep's approval before it sends.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/kortix-ai/suna/blob/HEAD/packages/starter/templates/marketplace/runtime/skills/call-recap/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/call-recap, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Step 1 — Find and read the transcript

The call recorder drops the transcript into the connected Google Drive folder ({{transcript_folder}}) once a call finishes. Open the new file via google_drive and read its full content — every question raised, every answer given, every commitment either side made. This is the entire input for the session; no other call's context loads in.

Step 2 — Match the call to its HubSpot deal

Identify the deal from the call's attendees (contact email domain, company name).

SignalRouting
Exactly one deal matches confidentlyPull its current stage, notes, and contact list before writing anything, so Step 4's update is a diff against reality, not a guess
No deal matches, or more than one plausibly matchesDo not guess — skip Step 4 and flag the call instead when you hold it for approval (Step 7), so a human links it to the right deal manually

Step 3 — Load the account's history and the recap playbook from memory

Read the shape of a good recap, how the team phrases next steps, which kinds of objections need a considered answer, and this account's own history (past calls, open threads) from memory. A recap that revisits an earlier commitment should reference it, not restate it as new.

Step 4 — Update the HubSpot deal

Skip this step entirely if Step 2 didn't produce a confident deal match — go straight to Step 5, and let Step 7 carry the flag instead. Otherwise write back what the call actually covered:

FieldUpdate
StageAdvance only if the call clearly moved the deal (verbal commit, next step scheduled) — otherwise leave it
NotesAppend a summary of the call: what was discussed, decided, and asked
ContactsAdd any new attendee who isn't already on the deal

Step 5 — File the follow-up tasks

Create one Linear task per commitment in {{linear_team}}: title is the commitment phrased as a task, description is the context plus a link back to the call, due date from anything the call implied ("by Friday"), assignee is the rep who hosted the call (the owner/host field on the transcript file or recording). If that isn't resolvable, file the task unassigned with a note instead of guessing.

Step 6 — Draft the recap email

Write the recap to the account's history and the team's playbook: a short summary of the call, a direct answer to every open question that came up, and the next steps restated plainly. Ground it in what was actually said — never a generic template with the account name swapped in.

Step 7 — Hold for approval

Place the drafted recap in {{approval_channel}} as a draft only. Do not send it. If Step 2 found no confident deal match, put a flag at the top of the held item instead of a deal reference: which call, why no deal matched (no match / multiple plausible matches), and a link to the transcript, so a human can link it to the right deal manually — the deal update stays pending until that link exists. Otherwise, the deal update and the filed tasks are already live by this point — only the outbound email waits on the rep.