Skill

meeting-recap

Pull a Fathom transcript and extract decisions, action items, open questions, and notable quotes. Reads about-me/business-brain.md (for ICP context — what the user cares about). Uses Fathom MCP. Lands in reference/research/meetings/<date>-<title>.md. Optionally drafts to chosen destination.

npx claudepluginhub automatedmarketer/cowork-research --plugin cowork-research

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/cowork-research:meeting-recap

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Pull a Fathom meeting transcript and extract decisions + action items + open questions.

Supporting Files

templates/meeting-recap-template.md

SKILL.md

59 lines · ~623 tokens

Similar Skills

cache-components

139.5k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

pdf

131.6k

Processes PDFs: extracts text/tables/images, merges/splits/rotates pages, adds watermarks, creates/fills forms, encrypts/decrypts, OCRs scans. Activates on PDF mentions or output requests.

11 files

document-skills

Stats

LanguageShell

Parent stars0

MaintenanceExcellent

Last CommitMay 14, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

meeting-recap

/meeting-recap — v0.1.0

Pull a Fathom meeting transcript and extract decisions + action items + open questions.

Inputs

Required: Fathom URL OR call_id OR recording_id

Read on every run:

about-me/about-me.md
about-me/business-brain.md (for ICP context — what action items matter to THIS user)
templates/meeting-recap-template.md
projects/research/research-preferences.md (recap depth: executive / detailed / verbatim)

Logic

Read input files

Resolve Fathom input: URL → mcp__claude_ai_Fathom__get_recording_by_url; call_id → get_recording_by_call_id; recording_id → get_meeting_summary directly

Call get_meeting_transcript with the resolved recording_id (for timestamped quotes) AND get_meeting_summary (for AI-generated summary as a starting point)

Extract structured data:

1-paragraph TLDR
Decisions made (3-5 bullets)
Action items (with owner + deadline if mentioned)
Open questions (things raised but not resolved)
2-3 notable quotes with timestamps + speaker

Generate recap using templates/meeting-recap-template.md shape

Plan-then-approve: show user the recap structure + key extracted items

On user approval, write the recap

Append one-line entry to reference/research/_index.md

Append one-line entry to projects/research/memory.md

If destination = Notion or vault, ask: "Draft to too?"

Output

reference/research/meetings/<date>-<title>.md (the recap)

Hard rules

Never make claims about meeting content without calling get_meeting_transcript first (per Fathom MCP grounding rule)

Plan-then-approve before any write

Action items MUST include owner + deadline if mentioned in the transcript; mark "owner: unspecified" if not

Voice for the recap itself

Tactical, scannable. Decisions and actions are the load-bearing parts — the rest is supporting. Quotes only when they capture something the summary can't.

/meeting-recap — v0.1.0

Pull a Fathom meeting transcript and extract decisions + action items + open questions.

Inputs

Required: Fathom URL OR call_id OR recording_id
Read on every run:
- about-me/about-me.md
- about-me/business-brain.md (for ICP context — what action items matter to THIS user)
- templates/meeting-recap-template.md
- projects/research/research-preferences.md (recap depth: executive / detailed / verbatim)

Logic

Read input files
Resolve Fathom input: URL → mcp__claude_ai_Fathom__get_recording_by_url; call_id → get_recording_by_call_id; recording_id → get_meeting_summary directly
Call get_meeting_transcript with the resolved recording_id (for timestamped quotes) AND get_meeting_summary (for AI-generated summary as a starting point)
Extract structured data:
- 1-paragraph TLDR
- Decisions made (3-5 bullets)
- Action items (with owner + deadline if mentioned)
- Open questions (things raised but not resolved)
- 2-3 notable quotes with timestamps + speaker
Generate recap using templates/meeting-recap-template.md shape
Plan-then-approve: show user the recap structure + key extracted items
On user approval, write the recap
Append one-line entry to reference/research/_index.md
Append one-line entry to projects/research/memory.md
If destination = Notion or vault, ask: "Draft to too?"

Output

reference/research/meetings/<date>-<title>.md (the recap)

Hard rules

Never make claims about meeting content without calling get_meeting_transcript first (per Fathom MCP grounding rule)
Plan-then-approve before any write
Action items MUST include owner + deadline if mentioned in the transcript; mark "owner: unspecified" if not

Voice for the recap itself

Tactical, scannable. Decisions and actions are the load-bearing parts — the rest is supporting. Quotes only when they capture something the summary can't.