para-obsidian

Second brain orchestrator — routes natural language to the right para-obsidian skill

Inbox capture with Web Clipper parity — fetches page titles and content for URLs, generates titles for inline text

Commit uncommitted notes in your Obsidian vault

Create a PARA area for ongoing life responsibilities with collaborative validation

Create a new inbox document classifier with guided wizard

Create custom Templater-compatible note templates via interactive wizard

Create a PARA project with validated area connections and collaborative workflow

[DEPRECATED] Create PARA notes - use /create-project or /create-area instead

Start a journaling session to transform today's logs into a meaningful journal entry

Enrich inbox notes with external data (YouTube transcripts, bookmarks, etc.)

Create a meeting note from transcription text, VTT file, or inbox note

Create a note from any URL with automatic template routing (resource, meeting, invoice, booking)

Semantic search across your Obsidian vault using PARA folders

Monitor SLO health and burn rates for para-obsidian operations

Manage stakeholders - list, add, remove, or lookup

Trace logs by correlation ID for debugging para-obsidian operations

Convert voice memos or transcriptions to Obsidian capture notes.

Process inbox items - single file or bulk with parallel batches

Validate frontmatter across all notes in your vault or specific directories.

Export and manage Obsidian Web Clipper JSON templates

Process a single inbox item for the triage orchestrator: read content, enrich from external sources, analyze, create note, inject Layer 1 content, and persist proposal via TaskUpdate. Use this agent when processing inbox items during /para-obsidian:triage. Each instance handles one item in isolation so content never pollutes the coordinator's context. MUST run in foreground — MCP tools are not available in background subagents.

Analyze PDF/DOCX attachments, create notes, and return lightweight proposals. Reads content via para_read, analyzes, creates note with para_create, and persists proposal. Worker skill for triage orchestrator.

Analyze voice memo transcriptions, create notes with appropriate content, and return lightweight proposals. For resources (ideas, reflections), creates note with Layer 1 transcription. For meetings, extracts structured body content. Worker skill for triage orchestrator.

Analyze web clippings, create resource notes with Layer 1 content, and return lightweight proposals. Handles enrichment, analysis, note creation, and Layer 1 injection so content never flows through coordinator. Worker skill for triage orchestrator.

Your PARA second brain orchestrator. Say what you need, not which command. Routes natural language to the right skill.

Inbox capture that matches Web Clipper output. Clips URLs or inline text as clipping notes with LLM-generated titles. Batch-capable for multiple URLs. No classification, no area/project assignment — triage handles that.

Create notes, inject Layer 1 content, and commit to vault. Canonical pipeline shared by triage-worker agent and quick-create skill. Not user-invocable — loaded as reference knowledge.

Create PARA area notes for ongoing life responsibilities. Validates that the concept is truly an area (ongoing, no end date) rather than a project. Use when establishing new life domains or responsibilities to track.

Create PARA notes (resource or meeting) from data gathered during conversation. Interactive workflow that classifies, proposes, and creates with content injection. Use when structured information exists in conversation context and needs capturing as a vault note.

Meeting orchestrator — creates structured meeting notes from any source: inline transcription text, VTT files, inbox transcription notes, or triage proposals. Use when creating meeting notes or when /meeting is invoked.

Create PARA project notes with validated area connections and PARA philosophy guidance. Ensures projects have clear outcomes, deadlines, and valid area relationships. Use when creating new projects to ensure they follow PARA method correctly.

Create resource notes from analyzed proposals. Use when triage orchestrator routes a proposal with proposed_template=resource. Handles frontmatter setup and original file cleanup via para_create.

Journaling partner that helps extract deeper meaning from daily logs. Use when the user wants to review their day, process logs into journal entries, or mentions "daily review".

**Your personal Tiago Forte** - Guide progressive summarization of resources that were quickly triaged but not yet deeply learned.

Generate AI-assisted frontmatter field suggestions using para-obsidian LLM utilities. Demonstrates 3-layer architecture (constraints, prompt-builder, orchestration) for metadata extraction.

Process daily note log entries into structured inbox notes. Handles voice memos (🎤), URLs (YouTube, Twitter/X, GitHub, articles), and text entries. Use when triaging daily logs, converting voice memos, or processing saved URLs.

Audit para-obsidian plugin for convention drift across skills, commands, hooks, and plugin registration.

Analyze and classify inbox items using PARA methodology. Use when triage or distill skills need decision trees, emoji mappings, and philosophy guides for consistent categorization.

Create a note from any URL with automatic template routing, enrichment, and content injection. Detects resource, meeting, invoice, and booking content automatically.

Record brain routing corrections with confidence scoring. Use when the brain orchestrator detects a wrong routing decision and needs to log the correction for future learning.

Manage stakeholders for voice memo speaker matching. Add, list, lookup, or remove stakeholders used by triage and meeting skills. Use when team members change, to verify current configuration, or to look up "who is [alias]?"

Generate intelligent content for PARA Obsidian vault templates. Use when asked to create new notes (project, area, resource, task, clipping, daily, weekly-review, booking, checklist, itinerary, trip-research), populate template sections with AI-generated content, or understand what fields a template requires before creation.

Unified inbox processor - handles ALL content types (clippings, transcriptions, VTT files, attachments) with parallel subagents and single-table review. Routes to appropriate creator based on proposed_template.

Web Clipper template management for ADHD-friendly capture workflow. Single universal template with zero-decision capture, automatic classification, and deferred organization. Use for template installation, understanding the capture pipeline, or troubleshooting Web Clipper issues.

3 hooks across 2 events