Meeting Scribe
Inspired by USV's Meeting Scribe agent (https://blog.usv.com/meet-the-agents), rebuilt as a generic version for any team that keeps files on people, organizations, or projects — not just a VC deal log. Reads a meeting transcript and a folder of entity files you already keep, then produces a dated meeting note, one appended mention line on each entity file the transcript actually names, and a recap email drafted for a human to review. It never guesses who a name refers to: a name either matches a file, becomes a proposed new entity for you to confirm, or is flagged as ambiguous with every candidate listed. Complements meeting-memo rather than replacing it — meeting-memo writes your circulate-ready notes, meeting-scribe keeps your people/company/project files current with a sourced mention timeline. Includes an eval contract with self-tests covering unmatched names, ambiguous names, quote-grounded mentions, and the draft-not-send boundary.
First-party, by Skills and Agents Co
August 14, 2026
Simple install — no setup required
Open the Claude desktop app and go to the Project you want this in
Go to Code, then Customize, then click Create a new skill and upload the skill file below
Say a trigger phrase to activate it
Download the skill file below
In ChatGPT, create a Project and attach the file (or paste its contents into the project instructions). For a reusable setup, build a Custom GPT via Explore GPTs → Create and add the file there
Start a chat in that Project or GPT, then say a trigger phrase to activate it
Download the skill file below
Place it at .cursor/skills/meeting-scribe/SKILL.md (rename the downloaded file to SKILL.md). The shared .agents/skills/meeting-scribe/SKILL.md path also works
Cursor loads the skill when your task matches its description. Say a trigger phrase to activate it
Download the skill file below
Place it at .github/skills/meeting-scribe/SKILL.md in your repository (rename the downloaded file to SKILL.md)
Copilot loads the skill when it is relevant to your task. Say a trigger phrase to activate it
Download the skill file below
Place it at .agents/skills/meeting-scribe/SKILL.md in your repository (rename the downloaded file to SKILL.md)
Codex loads the skill when your task matches, or invoke it explicitly with /skills. Say a trigger phrase to activate it
Download the skill file below
In Gemini, create a Gem, then upload the skill file as a knowledge file
Copy the Gem instructions with the button below, then paste them into the instructions box
Start a chat with the Gem, then say a trigger phrase to activate it
You are a Gem built around the "Meeting Scribe" skill. Turns a meeting transcript into a per-entity mention history — one dated line appended to each person, organization, or project file the transcript names, matched against your own tracked entities, plus a recap email drafted for review but never sent. Read the attached file first, then follow its instructions. Activate this skill when the user says something like: run meeting scribe, turn this transcript into meeting memory, log this meeting against my contacts, who did we mention on this call, draft a recap from this transcript.
npx skills add skills-agents-co/skills-and-agents-library/meeting-scribeYour skill is downloading.
Get an email when we ship new skills and updates.
You're on the list. We'll email you when new skills drop.
What this skill does
This is an overview of the skill from the site, not the skill's real instructions. The full SKILL.md Claude reads when this skill is active lives on GitHub at the source below.
Inspired by USV’s Meeting Scribe agent — USV built it for VC deal logs (portfolio companies, founders, co-investors). This is a generic, independently built version, not their code: any team that keeps files on people, organizations, or projects can point this at a transcript and get the same shape of output.
Reads a meeting transcript and a folder of entity files you already keep, then produces three things: one dated meeting note, one appended mention line on each entity file the transcript actually names, and a recap email drafted for a human to review — never sent. It never guesses who “sounds like” a tracked entity. A name either matches a file, becomes a proposed new entity for you to confirm, or is flagged as ambiguous with every candidate listed. Run it after every meeting and each entity’s mention timeline compounds. Complements meeting-memo rather than replacing it — run meeting-memo for the notes your team reads, run meeting-scribe to keep your people/company/project files current.
View full SKILL.md on GitHub