Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/dgalarza/claude-code-workflows/process-meeting-transcriptnpx skills add dgalarza/claude-code-workflows --skill process-meeting-transcriptgit clone --depth 1 https://github.com/dgalarza/claude-code-workflowsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00053 | $0.01137 |
| Opus 5 | $0.00026 | $0.00568 |
| Sonnet 5 | $0.00011 | $0.00227 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
process-meeting-transcript scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process Meeting Transcript
Overview
Process raw meeting transcripts into well-structured Obsidian notes with YAML frontmatter, extracted action items, meeting summary, and properly formatted transcript sections.
When to Use This Skill
Use this skill when:
- User provides a raw meeting transcript (typically from Granola)
- User asks to "process a meeting transcript" or "format meeting notes"
- User points to a file containing an unprocessed transcript
- User pastes transcript content directly into the conversation
Workflow
Step 1: Read the Transcript
If the transcript is in a file, read the entire contents. If the user pasted the transcript directly, use that content.
Step 2: Extract Action Items
Carefully review the entire transcript to identify all action items, tasks, and commitments. Look for:
- Explicit commitments: "I'll do X", "Alex will review Y"
- Assigned tasks: "Nathan and Damian should schedule..."
- Follow-up items: "We need to...", "Let's make sure to..."
- Decisions requiring action: "We should deploy X before Y"
Format action items as:
- Bulleted list under
# Action Itemsheading - Use bold for person names when specific people are assigned
- Include context for what needs to be done and why
- Order by priority/importance when evident from discussion
Example format:
# Action Items
- **Alice & Bob**: Review the new feature implementation next week and provide feedback
- **Charlie & Dana**: Schedule a knowledge transfer session on the payment service architecture
- **Eve**: Discuss deployment timeline with the infrastructure team
Step 3: Create Meeting Summary
Write a comprehensive but concise summary that captures:
- Main topics discussed
- Key decisions made
- Technical architecture or approach agreed upon
- Timeline and next steps
- Important context or constraints
Structure the summary with:
- Opening paragraph: High-level overview of what was discussed and main outcome
- Subsections (using
##or###headings) for major topics - Use bold for important terms, decisions, or concepts
- Include enough detail that someone who wasn't in the meeting can understand what happened
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 150 lines · 53 tokens per session scan A f70860dad044
process-meeting-transcript is a skill published in the GitHub repository dgalarza/claude-code-workflows (59 stars, last pushed 5d ago), licensed MIT. It adds 53 tokens to every session and 1,137 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…