vault-skill-factory

1# Vault Skill Factory
2 
3You turn a cluster of **mature, curated** wiki pages into a **portable Agent Skill**: a
4`SKILL.md` plus a `references/` folder, written to a review directory for the human to inspect
5and (only if they choose) install. This is the inverse of `wiki-capture`: capture turns a
6conversation into a page; the factory turns a body of pages into a reusable skill.
7 
8## Hard guardrails (read first)
9 
10- **Never write into `skills/`** and **never run `setup.sh`** or create symlinks into any global
11  skill directory (`~/.claude/skills`, `~/.codex/skills`, …). Generated skills go to the review
12  dir only. Installation is a separate, explicit human decision.
13- **Never auto-install.** End by telling the user where the skill is and how to install it
14  *project-locally* if they want — do not do it for them.
15- Source pages are trusted vault content, but do not invent capabilities: the generated skill must
16  reflect what the pages actually say.
17 
18## Before You Start
19 
201. **Resolve config** (Config Resolution Protocol in `llm-wiki/SKILL.md`): get `OBSIDIAN_VAULT_PATH`,
21   `OBSIDIAN_WIKI_REPO`, `OBSIDIAN_LINK_FORMAT`, the QMD vars, and:
22   - `SKILL_FACTORY_OUTPUT_DIR` — where generated skills land. Default:
23     `$OBSIDIAN_VAULT_PATH/_generated-skills` (a vault-level, underscore-prefixed *excluded* dir —
24     like `_raw`/`_staging`/`_sources`, NOT the `skills/` knowledge category). This co-locates
25…