ai-wiki — filing content into the knowledge base

Turns "write this up" into a correctly-named, correctly-linked note inside the AI-managed vault folder.

Where output goes

Throughout this skill, <AI_WIKI> means the configured AI-managed folder at the vault root. Resolve it once at the start of the task: use the value declared by the vault's CLAUDE.md or local rules, otherwise use 0ai_wiki/. Never create a literal folder named <AI_WIKI>. Everything this skill files lands under the resolved folder. That is the point of the skill, not a permission wall.

Zone	How to treat it
`<AI_WIKI>/**`	create / edit / move / rename / delete — free hand
every other top-level folder	the user's own notes. Read and search freely; additive edits fine; ask before deleting, renaming, moving, or overwriting
`.claude/rules/`, `CLAUDE.md`	static configuration; edit only when the user asks to change Claude's behaviour. The sole dynamic exception is `.claude/rules/active.md`
`.obsidian/`, `.trash/`	reachable but hands-off — editing Obsidian's own config can break the vault

Nothing is blocked at the permission layer, so the restraint above is judgement, not a wall. An Obsidian vault is usually not a git repo: a bad overwrite of a hand-written note is only recoverable from whatever cloud version history backs the folder.

Reading from those zones and filing a summary into <AI_WIKI>/ is exactly what this skill is for.