Agent skill · writing content · aiskillstore
chronicle-session-documenter
Document AI-assisted development sessions to Obsidian vault using Chronicle data. Works with MCP (fastest) or CLI commands (portable). Use when completing a coding session, creating development logs, or maintaining a knowledge base of past work. Automatically creates structured notes with metadata, summaries, and wikilinks.
Why this skill is useful
Adds executable scripts for documenting development sessions in Obsidian, automating note creation and metadata extraction.
What it needs
Requires chronicle installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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 - mcpchroniclegetsessionsummary(sessionid) → Get structured JSON with full summary 2. Create Note - mcpobsidianwritenote(...) → 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 - mcpobsidianwritenote(...) OR manually create note file 4. Link Work - Use parsed data to create wikilinks Decision Tree: Note: Summaries are automatically generated in background when session ends (may still be processing for recent sessions) Note Structure Create notes in Chronicle/Sessions/Session-{id}.md with this format: Workflow Examples Option 1: With MCP (Fast, Structured) After completing a session: Option 2: With CLI (Portable, No MCP Required) After completing a session: Note: CLI approach requires parsing Chronicle's formatted output, which is less elegant but fully portable to any system with Chronicle installed. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/chronicle-session-documenter