obsidian-notes-karpathy

Obsidian vault workflow requests are diagnosed and routed through a review-gated lifecycle to the appropriate operational skill, ensuring provenance and safe gatekeeping. It analyzes high-level prompts to determine which lifecycle step to run next.

When starting an Obsidian vault workflow, the routing skill evaluates your request against canonical skill-contracts and directs you to the correct initial operation, such as kb-init, preserving provenance through the lifecycle gate.

The best way to determine your current Obsidian vault governance stage is to describe your workflow at a high level. The routing mechanism analyzes the prompt, identifies the lifecycle step, and routes it to the matching operational skill.

Yes, the routing skill analyzes multilingual prompts, including Chinese-LLM-Wiki phrasing, to preserve boundaries and route ambiguity in Obsidian vault workflows to the correct lifecycle operation skill.

Yes, the routing uses canonical skill-contracts, references, and governance surfaces to preserve provenance and maintain the review gate during the Obsidian vault workflow lifecycle.

You should not use this routing skill when you already know the precise operational action required. It acts as a high-level orchestrator for ambiguous requests and defers specific actions to specialized skills like kb-ingest or kb-query.