Skill

Meeting recap

Turn a Fathom meeting recording into a structured recap, draft a Notion page for the meeting, and draft a short Slack thread to post in the relevant channel. Drafts only — never posts or publishes without explicit approval.

npx claudepluginhub sitloboi2012/team-marketplace --plugin team-core

Tool Access

This skill uses the workspace's default tool permissions.

Preview

**Invocation: user only.** This skill creates artifacts other humans will see, so it must not run autonomously.

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 23, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Meeting recap

Invocation: user only. This skill creates artifacts other humans will see, so it must not run autonomously.

Workflow

1. Locate the meeting

If the user passed a Fathom URL or meeting ID in $ARGUMENTS, use it.
If the user passed "latest" or nothing, use the Fathom MCP to find the user's most recent completed recording.
If Fathom MCP isn't connected, stop and tell the user to connect it.

2. Pull the transcript + existing AI summary

Use the Fathom MCP to retrieve:

Meeting title, start time, duration, attendees
Full transcript (or summarized chunks if the API forces it)
Any auto-extracted action items Fathom already produced

3. Write the recap

Produce this in a markdown code block, do not execute any write actions yet:

# <Meeting title> — YYYY-MM-DD

**Attendees:** <comma-separated>
**Duration:** <HH:MM>
**Recording:** <Fathom link>

## TL;DR
<2-3 sentences. What was the meeting for, and what's different now.>

## Decisions
- <decision>  (owner: <person>)
- ...
(If none: "No decisions.")

## Action items
- [ ] <action>  — <owner>  — due <YYYY-MM-DD or "TBD">
- ...
(Every action item needs an owner. If Fathom extracted one with no owner, either infer from context or flag "(owner: TBD)".)

## Key discussion points
- <topic>: <one line>
- ...

## Unresolved / follow-ups
- <thing we didn't answer, with who should answer it>

4. Draft the Slack post

Separately, draft a shorter version for Slack:

*<Meeting title>* — <date> · <Fathom link>

TL;DR: <one sentence>

Decisions:
• <decision>

Actions:
• <action> — @<person> — due <date>

Full notes: <Notion link will go here once posted>

Ask the user which Slack channel/thread to post to. Don't guess. Common choices: the meeting's own channel, #general, a project channel.

5. Confirm, then write

Show both drafts to the user. Wait for explicit approval ("ship it", "post it", "yes"). Then:

Create the Notion page via Notion MCP under the meetings path (default location is in the team CLAUDE.md; if unclear, ask).
Post the Slack message via Slack MCP, replacing <Notion link will go here once posted> with the actual link.
Report back with both links.

6. Don't do

Don't post to Slack before Notion — the Slack post references the Notion link.
Don't re-send if the user edits the draft and approves again — treat each approval as the final version.
Don't include transcript quotes unless the user asks; the transcript has the truth, the recap has the signal.