wiki-capture

Converts conversation findings into structured Obsidian wiki notes with provenance tracking.

Updated Nov 9, 2023
One-click install
npx skills add https://github.com/oresttokovenko/dot-files --skill wiki-capture-oresttokovenko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiki-capture
Source: https://github.com/oresttokovenko/dot-files/tree/main/chezmoi/dot_agents/skills/wiki-capture
Command: npx skills add https://github.com/oresttokovenko/dot-files --skill wiki-capture-oresttokovenko

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Valuable knowledge discovered during AI conversations — bug fixes, debugging conclusions, design decisions — is lost when the session ends. This Skill preserves that knowledge as permanent, structured wiki notes in an Obsidian vault instead of letting it disappear. ## Core Features & Use Cases - Full capture mode: Classifies conversation content into synthesis, concept, source, decision, or session types, rewrites it as declarative knowledge with provenance markers, and files it in the correct vault category with cross-links. - Quick mode: Stages findings to a _raw/ folder in under 60 seconds with no index or manifest writes, ideal for mid-session capture of bug fixes and gotchas. - Correction mode: Records atomic corrections against immutable sources with SHA-256 integrity verification and per-consumer propagation tracking. - Use Case: After debugging a Swift actor reentrancy issue in a session, say "save this" to file a structured wiki note with root cause, fix, confidence score, and links to related pages. ## Quick Start Ask the assistant to save this conversation to your wiki using the wiki-capture skill.

Frequently Asked Questions about wiki-capture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save an AI conversation to my Obsidian wiki?

Invoke the skill by saying "save this", "capture this", or "/wiki-capture". It classifies the content into a type like synthesis or concept, rewrites it as declarative knowledge, and writes a cross-linked note into the correct vault folder.

What is the difference between quick capture and full wiki capture?

Quick mode drops findings into a `_raw/` staging folder in under 60 seconds with no manifest or index writes, while full mode writes a finished, cross-linked wiki page and updates index.md, log.md, and hot.md. Staged files are later promoted via /wiki-ingest.

How does wiki capture handle corrections to previous claims?

Correction mode records one atomic claim pair with a SHA-256 hash of the immutable source, verifying the source is unchanged before and after the write. It then propagates the correction to each derived consumer and tracks per-consumer completion status.

Does wiki-capture work with multiple Obsidian vaults?

Yes, it supports inline named-vault routing such as "@research save this" through a shared Config Resolution Protocol. Vault paths resolve from inline overrides, local .env files, or global config.

When should I not use automatic session capture?

Skip capture when the conversation is purely conversational with no implementation, no debugging conclusions, and nothing surprising or undocumented. The built-in KEEP/SKIP gate prevents staging low-value sessions, especially when triggered automatically by a Stop hook.