chronicle-session-documenterlisted

# Chronicle Session Documenter This skill helps you document development sessions to your Obsidian vault using Chronicle's database. Works with both MCP server (fast, structured) or CLI commands (portable, everywhere). ## Auto-Activation > **This skill auto-activates!** (Milestone #13) > > Prompts like "document session 75" or "export to Obsidian" automatically trigger a recommendation to use this skill. No need to manually load it! > > **Trigger patterns:** document session, export to obsidian, save to vault > **See:** `docs/HOOKS.md` for full details ## When to Use This Skill Use this skill when: - A development session has just completed - User wants to document what was accomplished in a session - Creating a development log or journal entry - Building a searchable knowledge base of past work - Need to link related sessions, commits, or decisions ## How It Works **Option 1: With MCP (Preferred)** 1. **Query Chronicle** - `mcp__chronicle__get_session_summary(session_id)` → Get structured JSON with full summary 2. **Create Note** - `mcp__obsidian__write_note(...)` → Write directly to Obsidian vault 3. **Link Work** - Use session relationships from JSON to create wikilinks **Option 2: With CLI (Portable)** 1. **Query Chronicle** - `chronicle session <id>` → Get formatted session details and summary 2. **Parse Output** - Extract summary, files, duration from CLI output 3. **Create Note** - `mcp__obsidian__write_note(...)` OR manually create note file 4. **Link Work** -