cog-meeting-processing
Process meeting recordings and transcripts into decisions, action items, and team dynamics
npx skills add a5c-ai/babysitter --skill meeting-processing --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
- Extract decisions with context, rationale, and stakeholders - Identify action items with owners, priorities, and deadlines - Analyze team dynamics: engagement, alignment, collaboration quality - Generate executive meeting summaries - Segment transcripts into topics and discussion threads - Route meeting artifacts to vault with project cross-references ## Tool Use Instructions 1. Use `file-read` to load the meeting transcript or recording 2. Parse transcript and identify speakers against participant list 3. Segment into topics and discussion threads 4. Extract decisions with context and rationale 5. Extract action items with owners and deadlines 6. Analyze team dynamics (engagement, alignment, disagreements) 7. Use `file-write` to create meeting notes in 03-professional 8. Use `file-search` to find related projects for cross-referencing 9. Use `git-commit` to commit meeting artifacts ## Examples ```json { "vaultPath": "./cog-vault", "captureType": "meeting-transcript", "transcriptPath": "./meeting-2026-03-02.txt", "meetingTitle": "Sprint Planning Q1 W9", "participants": ["Alex", "Jordan", "Sam"] } ```
- Tool Use Instructions
- Examples
What does the cog-meeting-processing skill do?
Process meeting recordings and transcripts into decisions, action items, and team dynamics
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill meeting-processing --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.