ReddRadar
Agent skill
archive-meeting
Archive one or more meetings into the brain repo by importing Zoom transcript folders (~/Documents/Zoom/*) and/or downloaded Teams .vtt files (~/Downloads/*.vtt), then generating a transcript markdown file, an executive summary, and creating meeting notes. Use when the user says "archive meeting", "archive my last meeting", "process these transcripts", or similar.
Install this agent skill to your Project
npx add-skill https://github.com/jonmagic/skills/tree/main/skills/archive-meeting
SKILL.md
Archive Meeting
Overview
Turn "there's a transcript somewhere" into structured, linked artifacts in the brain repo:
Transcripts/YYYY-MM-DD/NN.md(imported transcript with frontmatter)Executive Summaries/YYYY-MM-DD/NN.md(generated summary with frontmatter)Meeting Notes/<target>/YYYY-MM-DD/NN.md(meeting notes with links and detailed notes)Weekly Notes/Week of YYYY-MM-DD.mdcheckbox for the meeting marked as complete (if found)- Pending
{{Meeting Notes/<target>}}placeholders replaced with wikilinks
Agent Responsibilities
The agent's job is simple: call the CLI. Everything else is handled automatically.
For interactive mode (recommended), just run:
archive-meeting \
--brain-dir ~/code/jonmagic/Brain \
--executive-summary-prompt-path ~/code/jonmagic/prompts/summarize/zoom-transcript-executive-summary.md \
--detailed-notes-prompt-path ~/code/jonmagic/prompts/summarize/transcript-meeting-notes.md
The CLI will use fzf to:
- Select from recent meetings (Zoom folders + Teams VTTs)
- Select from pending meeting note targets in weekly notes
Explicit Mode
If the user specifies the input and target:
archive-meeting \
--brain-dir ~/code/jonmagic/Brain \
--input "/path/to/transcript.vtt" \
--meeting-notes-target "jonmagic" \
--executive-summary-prompt-path ~/code/jonmagic/prompts/summarize/zoom-transcript-executive-summary.md \
--detailed-notes-prompt-path ~/code/jonmagic/prompts/summarize/transcript-meeting-notes.md
CLI Options
| Option | Required | Description |
|---|---|---|
--brain-dir |
Yes | Path to Brain directory |
--input |
No | Path to input (VTT file or Zoom folder). If omitted, uses fzf selection |
--meeting-notes-target |
No | Meeting Notes target basename (e.g., "jonmagic"). If omitted, uses fzf selection |
--executive-summary-prompt-path |
Yes | Path to prompt file for executive summary |
--detailed-notes-prompt-path |
Yes | Path to prompt file for detailed notes |
--date |
No | Override meeting date (YYYY-MM-DD). Defaults to file mtime |
--dry-run |
No | Show what would be done without writing files |
Batch Workflow
For multiple meetings, call the CLI once per meeting with explicit arguments.
Prerequisites
The archive-meeting CLI from ~/code/jonmagic/scripts must be on PATH.
To verify:
which archive-meeting
archive-meeting --help
If not available:
cd ~/code/jonmagic/scripts && bun install
# Ensure ~/code/jonmagic/scripts/bin is on PATH
References
references/formats.md— Zoom folder conventions and Teams VTT quirksreferences/meeting_notes_routing.yml— manual overrides/aliases for Meeting Notes routingassets/transcript-meeting-notes.prompt.md— prompt template for meeting notes (legacy)assets/zoom-transcript-executive-summary.prompt.md— prompt template for executive summary (legacy)
Frontmatter
All output files should include YAML frontmatter. Generate a TID for each file:
node ~/.copilot/skills/frontmatter-add/scripts/generate-tid.js
Transcript files (Transcripts/YYYY-MM-DD/NN.md)
---
uid: <TID>
type: transcript
created: <meeting date ISO 8601>
tags: []
links:
related: []
---
Executive summary files (Executive Summaries/YYYY-MM-DD/NN.md)
---
uid: <TID>
type: executive.summary
created: <meeting date ISO 8601>
tags: []
links:
source: [<transcript TID>]
related: []
---
Meeting notes files (Meeting Notes/<target>/YYYY-MM-DD/NN.md)
---
uid: <TID>
type: meeting.note
created: <meeting date ISO 8601>
tags: []
links:
source: [<transcript TID>]
related: []
---
The links.source field connects the executive summary and meeting notes back to the transcript they were generated from. If the CLI handles file creation, the agent should add frontmatter to any files that don't already have it.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
jonmagic/skills
markdown-to-standalone-html
Convert Markdown documents (*.md files) to self-contained HTML files with embedded images. Use when you need a portable, offline-friendly single HTML file from Markdown—ideal for blog posts, essays, reports, or any content that should work without external dependencies.
jonmagic/skills
brain-operating-system
Quick reference for operating within jonmagic's second-brain workspace. Use when working with files in the brain repository—provides directory structure, naming conventions, append-only norms, wikilink patterns, frontmatter requirements, project conventions, and file organization rules. Essential for understanding where to create files, how to name them, and how to maintain continuity with existing structures.
jonmagic/skills
semantic-commit
Generate semantic commit messages from staged changes. Use when committing code to produce consistent, well-structured commit messages following conventional commit format.
jonmagic/skills
brain-commit
Analyze changes in the Brain repo and create semantic commits. Use when the user wants to commit their brain changes with meaningful, organized commit messages. Analyzes staged/unstaged changes, groups related files, creates appropriate commits, and pushes without user interaction.
jonmagic/skills
session-to-brain
Archive a Copilot CLI session to the brain. Creates a daily project file with the session transcript and adds a resume link to the weekly note. Use when ending a significant work session to preserve context for future reference.
jonmagic/skills
create-bookmark
Save a URL as a bookmark with frontmatter and a blurb or AI summary. Use when the user says "bookmark this", "save this link", or shares a URL they want to remember.
Didn't find tool you were looking for?