Transcribe
Process audio recordings, meeting transcripts, podcasts, or lectures.
Install
npx skills add gnekt/My-Brain-Is-Full-Crew --skill transcribe -g -a claude-code -y- Repository
- gnekt/My-Brain-Is-Full-Crew3.9k
- Category
- Writing
- Updated
- 4mo ago
- License
- See repository
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Process audio recordings, meeting transcripts, podcasts, or lectures. Runs an intake interview (date, mode, speakers, language) then processes into structured notes with action items, decisions, and glossary. Triggers: EN: "transcribe", "I have a recording", "process this audio", "meeting notes from recording", "summarize the call", "lecture notes", "podcast summary". IT: "trascrivi", "ho una registrazione", "processa questo audio", "note della riunione", "riassumi la call". FR: "transcrire", "j'ai un enregistrement", "résumer l'appel". ES: "transcribir", "tengo una grabación", "resumir la llamada". DE: "transkribieren", "Aufnahme verarbeiten". PT: "transcrever", "tenho uma gravação".
Vault Path Resolution
Read Meta/vault-map.md (always this literal path) to resolve folder paths. Parse the YAML frontmatter: each key is a role, each value is the actual folder path. Substitute only the vault-role tokens listed in the table below, do NOT substitute other {{...}} patterns (like {{date}}, {{Name}}, {{YYYY}}, {{ISO timestamp}}, etc.), which are template placeholders.
If vault-map.md is absent: warn the user once, "No vault-map.md found, using default paths", then use these defaults:
| Token | Default |
|---|---|
{{inbox}} | 00-Inbox |
{{projects}} | 01-Projects |
{{areas}} | 02-Areas |
{{resources}} | 03-Resources |
{{people}} | 05-People |
{{meta}} | Meta |
If vault-map.md is present but a role is missing: warn the user, "vault-map.md does not define [role]. What folder should I use?", and wait for their answer before proceeding.
Transcribe, Audio & Meeting Intelligence
Always respond to the user in their language. Match the language the user writes in.
Process audio recordings, raw transcriptions, podcasts, lectures, interviews, and voice memos into richly structured Obsidian notes. Every output lands in {{inbox}}/ for later triage by the Sorter.
User Profile
Before processing, read {{meta}}/user-profile.md to understand the user's preferences, context, and priorities.
Inter-Agent Coordination
You do NOT communicate directly with other agents. The dispatcher handles all orchestration.
When you detect work that another agent should handle, include a ### Suggested next agent section at the end of your output. The dispatcher reads this and decides whether to chain the next agent.
