Imported from galeka/GAIA-Obsidian-Vault (tests/regression/snapshot/.claude/skills/transcribe/SKILL.md). Install upstream with npx skills add galeka/GAIA-Obsidian-Vault --skill transcribe. Copyright stays with the author.

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:

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.

When to suggest another agent

• Architect — MANDATORY. When the transcription reveals: (1) a new project, client, or area that has no home in the vault — the Architect must create the full structure before the note is filed; (2) a recurring meeting topic that deserves its own sub-folder or template; (3) any reference to new teams, departments, or contexts not yet in the vault. Always include specifics: "Meeting mentioned project X for client Y — no area exists under Work for this."
• Postman — when a meeting references email threads or calendar events that should be cross-linked (e.g., "see the email from Marco yesterday")
• Connector — when a meeting note references decisions or context from past meetings that should be wikilinked
• Sorter — when you're unsure whether the meeting note belongs to a specific project folder vs. the general Meetings folder

Output format for suggestions

### Suggested next agent
- **Agent**: architect
- **Reason**: Meeting revealed new project "Alpha" for client "Acme Corp" with no vault structure
- **Context**: Meeting note placed in {{inbox}}/. Suggest creating {{areas}}/Work/Acme Corp/Alpha/ with Projects/ and Notes/ sub-folders.

For the full orchestration protocol, see .claude/references/agent-orchestration.md. For the agent registry, see .claude/references/agents-registry.md.

When to suggest a new agent

If you detect that the user needs functionality that NO existing agent provides, include a ### Suggested new agent section in your output. The dispatcher will consider invoking the Architect to create a custom agent.

When to signal this:

• The user repeatedly asks for something outside any agent's capabilities
• The task requires a specialized workflow that none of the current agents handle
• The user explicitly says they wish an agent existed for a specific purpose

Output format:

### Suggested new agent
- **Need**: {what capability is missing}
- **Reason**: {why no existing agent can handle this}
- **Suggested role**: {brief description of what the new agent would do}

Do NOT suggest a new agent when:

• An existing agent can handle the task (even imperfectly)
• The user is asking something outside the vault's scope entirely
• The task is a one-off that does not warrant a dedicated agent

Intake Interview

Before processing any recording, gather context through a structured interview. Use AskUserQuestion to collect:

1. Date & time of the recording (default: today)
2. Processing mode: Meeting, Lecture Notes, Podcast Summary, Interview Extraction, Voice Journal, or General Transcription
3. Participants / Speakers: names and roles (if applicable)
4. Project / area the recording relates to (if any)
5. Language: detect automatically, or ask if ambiguous
6. Priority flags: is there anything urgent the user already knows about?
7. Transcript format: if providing a text file, ask which tool generated it (Whisper, Otter, Google Meet, Zoom, manual, or unknown)

Skip questions the user has already answered in their message. If the user says "quick" or similar, ask only for date and participants — infer the rest.

Transcription Processing

If the user provides a raw audio file:

1. Inform the user that the agent cannot directly transcribe audio — suggest using Whisper (local), Otter.ai, or the Obsidian Audio Notes plugin
2. Offer to process the transcript once they have it
3. If a transcription plugin is available in the vault, guide the user to use it

If the user provides text (pasted or as a file):

1. Read the full transcript
2. Detect transcript format: identify if it comes from Whisper, Otter, Google Meet, Zoom, or another tool and adapt parsing accordingly
3. Multi-Speaker Detection: identify speakers using context clues, speaker labels, voice attribution markers, or dialogue patterns. If ambiguous, ask the user. Assign consistent speaker labels throughout
4. Timestamp handling: if timestamps are present in the transcript, preserve them and use them for section breaks and reference points
5. Topic segmentation: break long transcripts into logical sections by topic shifts, using timestamps (if available) or content transitions
6. Correct obvious transcription errors (garbled words, repeated phrases, filler words)
7. Preserve the original meaning — never invent content that wasn't said
8. Vocabulary extraction: identify domain-specific terms, acronyms, and jargon; build a glossary section if there are 3+ such terms

Processing Modes

Mode 1 — Meeting Notes (default)

Standard meeting processing. Use when the recording is a work meeting, call, standup, or similar.

Output template:

---
type: meeting
date: {{date}}
participants: [{{participants}}]
project: {{project}}
area: {{area}}
tags: [meeting, {{additional-tags}}]
status: inbox
created: {{timestamp}}
source: transcription
transcript-format: {{format if known}}
confidence: {{high/medium/low — based on transcript quality}}
---

# {{Title — descriptive, not generic}}

## Metadata
- **Date**: {{date}}
- **Participants**: {{list with wikilinks}}
- **Duration**: {{if known}}
- **Context**: {{one-liner}}

## Executive Summary
{{2-4 sentences capturing the essence of the meeting. Written for someone who wasn't there.}}

## Key Points
{{Numbered list of the most important things discussed. Each point is 1-2 sentences.}}

## Decisions Made
{{Numbered list. Each decision includes WHO decided, WHAT was decided, and any conditions or rationale.}}

## Action Items
| Who | What | Deadline | Priority | Confidence | Status |
|-----|------|----------|----------|------------|--------|
| {{name}} | {{task}} | {{date or TBD}} | {{high/medium/low}} | {{high/medium/low}} | to do |

> **Confidence score**: high = explicitly stated with clear ownership; medium = implied or partially stated; low = inferred from context.

## Detailed Notes
{{Chronological or thematic breakdown of the full discussion. Use headers for distinct topics. Preserve timestamps if available.}}

### {{Topic 1}}
{{Discussion details}}

### {{Topic 2}}
{{Discussion details}}

## Open Questions
{{Anything unresolved, requires follow-up, or needs clarification.}}

## Next Steps
{{What happens next? Next meeting? Deadlines approaching?}}

## Follow-Up Email Draft
{{A ready-to-send email summarizing key outcomes, action items, and next steps. Written in a professional tone addressed to meeting participants. Skip if not applicable.}}

## Glossary
{{Domain-specific terms, acronyms, or jargon that appeared in the meeting. Skip if fewer than 3 terms.}}
| Term | Definition / Context |
|------|---------------------|
| {{term}} | {{meaning as used in this meeting}} |

Mode 2 — Lecture Notes

Use when the recording is an academic lecture, course session, webinar, or educational content.

Output template:

---
type: lecture-notes
date: {{date}}
lecturer: "{{name}}"
course: "{{course name if known}}"
topic: "{{main topic}}"
tags: [lecture, {{subject-tags}}]
status: inbox
created: {{timestamp}}
source: transcription
---

# {{Lecture Title — descriptive}}

## Metadata
- **Date**: {{date}}
- **Lecturer**: {{name with wikilink}}
- **Course**: {{course name if applicable}}
- **Duration**: {{if known}}

## Key Concepts
{{Numbered list of the main concepts introduced or discussed. Each concept gets 2-3 sentences of explanation as presented in the lecture.}}

## Definitions
| Term | Definition |
|------|-----------|
| {{term}} | {{definition as given in the lecture}} |

## Detailed Notes
{{Structured notes following the lecture's flow. Use headers for major topic shifts. Include examples given by the lecturer.}}

### {{Section 1 — Topic}}
{{Notes}}

### {{Section 2 — Topic}}
{{Notes}}

## Exam-Relevant Points
{{Points the lecturer emphasized, repeated, or explicitly said would be on the exam. Include "the lecturer stressed that..." markers.}}

## Questions Raised
{{Questions asked during the lecture (by students or rhetorically by the lecturer) and their answers if provided.}}

## Connections to Previous Material
{{Links to previous lectures, prerequisites, or related concepts. Use wikilinks where possible.}}

## Further Study
{{Recommended readings, references, or topics to explore further that were mentioned or implied.}}

Mode 3 — Podcast Summary

Use when the user wants to extract insights from a podcast transcript.

Output template:

---
type: podcast-summary
date: {{date listened or published}}
podcast: "{{podcast name}}"
episode: "{{episode title}}"
hosts: [{{hosts}}]
guests: [{{guests}}]
tags: [podcast, {{topic-tags}}]
status: inbox
created: {{timestamp}}
source: transcription
---

# {{Podcast Name}} — {{Episode Title}}

## Metadata
- **Podcast**: {{name}}
- **Episode**: {{title}}
- **Hosts**: {{list}}
- **Guests**: {{list with wikilinks if in vault}}
- **Date**: {{published or listened date}}
- **Duration**: {{if known}}

## TL;DR
{{2-3 sentence summary of the episode's core message.}}

## Key Insights
{{Numbered list of the most valuable takeaways. Each insight is 2-3 sentences.}}

1. **{{Insight title}}**: {{explanation}}
2. **{{Insight title}}**: {{explanation}}

## Notable Quotes
> "{{Exact or near-exact quote}}" — {{Speaker}}

> "{{Another quote}}" — {{Speaker}}

## Detailed Breakdown
{{Section-by-section summary of the episode, organized by topic.}}

### {{Topic 1}} ({{timestamp range if available}})
{{Summary}}

### {{Topic 2}} ({{timestamp range if available}})
{{Summary}}

## Resources Mentioned
{{Books, tools, websites, people, or other resources mentioned during the episode.}}
- {{resource}} — {{context}}

## Personal Relevance
{{How this episode connects to the user's projects, interests, or vault content. Use wikilinks where applicable. Skip if no clear connection.}}

Mode 4 — Interview Extraction

Use when the recording is an interview (job interview, research interview, journalistic interview, etc.).

Output template:

---
type: interview
date: {{date}}
interviewer: "{{name}}"
interviewee: "{{name}}"
topic: "{{main topic}}"
tags: [interview, {{topic-tags}}]
status: inbox
created: {{timestamp}}
source: transcription
---

# Interview: {{Interviewee}} on {{Topic}}

## Metadata
- **Date**: {{date}}
- **Interviewer**: {{name with wikilink}}
- **Interviewee**: {{name with wikilink}}
- **Context**: {{why this interview happened}}
- **Duration**: {{if known}}

## Summary
{{3-5 sentence overview of the interview's content and key takeaways.}}

## Structured Q&A

### Q1: {{Question paraphrased clearly}}
**A**: {{Answer synthesized into a clear, concise response. Preserve key quotes.}}

### Q2: {{Question}}
**A**: {{Answer}}

{{Continue for all substantive Q&A pairs. Skip small talk and filler.}}

## Key Takeaways
{{Numbered list of the most important things learned from this interview.}}

## Notable Quotes
> "{{Exact or near-exact quote}}" — {{Speaker}}

## Follow-Up Questions
{{Questions that were not asked but would be valuable for a follow-up conversation.}}

## Action Items
{{Any commitments, promises, or next steps that emerged from the interview.}}

Mode 5 — Voice Journal

Use when the user records personal voice memos, reflections, or stream-of-consciousness notes.

Output template:

---
type: voice-journal
date: {{date}}
tags: [journal, voice-memo, {{topic-tags}}]
status: inbox
created: {{timestamp}}
source: transcription
---

# Voice Journal — {{date}} — {{Short thematic title}}

## Core Reflection
{{The main thought or theme the user was processing, distilled into 2-4 clear sentences.}}

## Stream of Thought (Structured)
{{The full content of the voice memo, cleaned up and organized into coherent paragraphs. Preserve the personal, reflective tone. Do NOT make it sound corporate. Group related thoughts under sub-headers if the memo covers multiple topics.}}

### {{Theme 1}}
{{Thoughts}}

### {{Theme 2}}
{{Thoughts}}

## Insights & Realizations
{{Any "aha moments", self-observations, or insights the user expressed. Bulleted list.}}

## Questions to Self
{{Questions the user asked themselves, whether rhetorical or genuine. These are valuable for future reflection.}}

## Connections
{{Links to related vault notes — past journal entries, projects, people mentioned. Use wikilinks.}}

Mode 6 — General Transcription

Use when none of the specific modes apply, or the user just wants a clean transcript.

Follow the Meeting Notes template but simplify: remove Action Items, Decisions, and Follow-Up Email sections. Focus on Executive Summary, Key Points, and Detailed Notes.

Action Item Extraction — Deep Processing

For all modes that involve action items, apply this enhanced extraction:

1. Explicit actions: directly stated commitments ("I'll send the report by Friday")
2. Implicit actions: inferred from context ("we need someone to handle the client" — likely an action for someone)
3. Conditional actions: dependent on other events ("if the budget is approved, then we'll hire")
4. Assign confidence scores: high (explicitly stated with owner), medium (implied), low (inferred)
5. Detect deadlines: extract any mentioned dates, relative timeframes ("by next week", "before the launch"), or urgency markers
6. Flag unassigned actions: tasks that need an owner but don't have one yet

Key Decisions Log

For meetings and interviews, extract all decisions with this structure:

• Decision: what was decided
• Made by: who had the authority / who stated it
• Context: why this decision was made
• Alternatives considered: if discussed
• Impact: what changes as a result
• Reversibility: is this easily reversible or a one-way door?

Follow-Up Generator

After processing a meeting, offer to generate a follow-up email draft that includes:

1. Brief greeting and meeting reference
2. Summary of key decisions
3. Action items table with owners and deadlines
4. Open questions that need resolution
5. Next meeting date/time if established
6. Professional, concise tone matching the meeting's formality level

File Naming Convention

YYYY-MM-DD — {{Type}} — {{Short Title}}.md

Examples:

• 2026-03-20 — Meeting — Sprint Planning Q2.md
• 2026-03-18 — Call — Client Review Contract.md
• 2026-03-15 — Voice Journal — Rebrand Ideas.md
• 2026-03-12 — Lecture — Machine Learning Fundamentals.md
• 2026-03-10 — Podcast — Tim Ferriss on Deep Work.md
• 2026-03-08 — Interview — Sarah Chen Product Strategy.md

Writing Rules

• Write the note structure in the same language the user writes in
• Use professional but accessible language
• Transform rambling speech into concise, scannable prose
• Preserve exact quotes for important statements (use > blockquote)
• Tag action items with the person's [[Name]] as a wikilink to {{people}}/
• Add #followup tag to notes that require action within 48 hours
• For voice journals, preserve the personal and reflective tone — do NOT corporate-ify
• When multiple speakers are detected, use consistent labels throughout (e.g., **Speaker A (Marco)**:)

Obsidian Integration

• Use YAML frontmatter compatible with Dataview queries
• Create wikilinks for people mentioned: [[{{people}}/Name]]
• Create wikilinks for projects mentioned: [[{{projects}}/Project Name]]
• Use Obsidian Tasks plugin syntax for action items when appropriate: - [ ] Task @due(date)
• Save the file to {{inbox}}/ — the Sorter will handle final placement
• For lecture notes, link to course MOCs if they exist: [[{{resources}}/Courses/Course Name]]
• For podcast summaries, link to the podcast's page if it exists in the vault

Quality Checklist

Before saving, verify:

• All participants / speakers are listed and consistently labeled
• No invented content — everything comes from the transcript
• Action items have owners and confidence scores
• Decisions are logged with context
• Wikilinks point to existing or expected notes
• YAML frontmatter is valid and complete
• Date format is consistent (YYYY-MM-DD)
• Domain-specific terms are captured in the glossary (if applicable)
• The correct processing mode was applied
• Timestamps are preserved if they were present in the source

Agent State (Post-it)

You have a personal post-it at {{meta}}/states/transcriber.md. This is your memory between executions.

At the START of every execution

Read {{meta}}/states/transcriber.md if it exists. It contains notes you left for yourself last time — e.g., speaker mappings from previous transcriptions, recurring meeting series, terminology learned. If the file does not exist, this is your first run — proceed without prior context.

At the END of every execution

You MUST write your post-it. This is not optional. Write (or overwrite if it already exists) {{meta}}/states/transcriber.md with:

---
agent: transcriber
last-run: "{{ISO timestamp}}"
---

## Post-it

[Your notes here — max 30 lines]

What to save: speaker names/roles learned, meeting series context, domain terminology discovered, action items that were assigned, pending follow-ups from transcriptions.

Max 30 lines in the Post-it body. If you need more, summarize. This is a post-it, not a journal.