メニュー
Convert VTT meeting transcripts from meetings/incoming/ into structured markdown notes in meetings/
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Tracks Architecture Decision Records (ADRs) in docs/adrs/. Creates, lists, and updates ADRs following project conventions. TRIGGER when: user wants to record, review, or update an architectural decision.
Check and align a repo's .claude/settings.json and CLAUDE.md with team conventions. Use when the user wants to standardize a repo, align conventions, check settings, or bootstrap Claude Code config in a new project.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Set up and maintain Gmail Multiple Inboxes with auto-discovered sender filters. Scans the user's Gmail to discover senders, suggests inbox categories, generates a Google Apps Script that creates labels and filters. Use this skill for: organizing Gmail, setting up multiple inboxes, managing Gmail labels and filters, categorizing email senders, updating inbox filters with new senders, or unsubscribing from noisy emails. Trigger phrases: "Gmail sections", "inbox categories", "email organization", "sender filters", "multiple inboxes", "clean up my inbox".
Morning review and prioritization of Things todos. Use this skill every morning, or whenever the user asks to review, triage, categorize, or prioritize their Things tasks. Also trigger when the user says things like 'what should I work on today', 'organize my todos', 'morning routine', or 'daily review'.
Generate or update distributed STRUCTURE.md index files across a repo to help LLMs orient quickly in project structure and to make large knowledge repositories easier to navigate and summarize.
| name | process-transcript |
| description | Convert VTT meeting transcripts from meetings/incoming/ into structured markdown notes in meetings/ |
Process all VTT meeting transcripts from meetings/incoming/ into structured markdown notes in meetings/.
scripts/parse-vtt.py — Parses raw VTT files into Markdown files with YAML frontmatter (date, attendees) and a clean Speaker: text transcript (blank line between each turn). Supports --output-dir to control where .md files are written.Find VTT files: Check both meetings/incoming/ and ~/Downloads/ for .vtt files. Automatically process, without asking, every .vtt file modified within the last 24 hours (plus anything already sitting in meetings/incoming/). List the files you selected with their stat timestamps so the user can see what was picked, but do not wait for confirmation. Ignore older files unless the user explicitly asks for them. If no recent files are found in either location, tell the user and stop.
Parse VTT files: Run the bundled script on the confirmed files, always outputting to meetings/incoming/. Use absolute paths for both the script and the output to avoid working-directory issues:
SKILL_SCRIPT="$(ls "${PWD}/.claude/skills/process-transcript/scripts/parse-vtt.py" "${HOME}/.claude/skills/process-transcript/scripts/parse-vtt.py" 2>/dev/null | head -1)" && uv run "$SKILL_SCRIPT" --output-dir meetings/incoming <file1>.vtt <file2>.vtt
This creates .md files in meetings/incoming/ with frontmatter and transcript already formatted.
Read each generated .md file and determine:
strategy, progress-sync, brainstorm, planning, one-on-one, kickoff, etc.).# Meeting Title heading above the ## Transcript section.Important: Do not rewrite the transcript through the model. Only prepend the title and summary to the file generated by the script. Keep the transcript output from the script as-is.
Move the file to meetings/YYYY-MM-DD-<slug>.md.
After processing, report which files were created, then always delete the processed source .vtt files (from ~/Downloads/ and/or meetings/incoming/) without asking.