| name | wiki |
| description | Manages Wiki CLI end to end — install and verify wazootech-wiki, scaffold with wiki init, audit vault hygiene (fmt, lint, check, render), plan and execute vault improvements, and deploy to GitHub Pages. Use whenever the user mentions wiki, Wiki CLI, wazootech-wiki, wiki init, wiki.yml, wiki.yaml, broken links, lint/check failures, pre-PR wiki review, GitHub Pages for a wiki, or getting started with semantic markdown — even if they do not say "skill". Route to one workflow reference, complete that job, and stop. |
Wiki CLI Skill
Procedural knowledge for coding agents working with Wiki CLI (wiki command, PyPI wazootech-wiki).
Skills under skills/ are agent knowledge — not wiki pages. Do not add skills/ to wiki.inputs.
Principles
- Deterministic work belongs in scripts and the CLI — run
skills/wiki/scripts/verify.sh and skills/wiki/scripts/audit.sh instead of reimplementing validator pipelines in prose.
- One workflow per turn — read the matching reference below, finish that job, stop. Do not chain install → create → deploy unless the user asked for the full flow.
- Advisor-executor model for vault changes — survey and plan changes as a read-only advisor; dispatch executor subagents to apply edits in isolated worktrees, and review their diffs. Never directly edit user files without approval.
- Deploy uses wholesale templates — embed workflow-template-uv.yml or workflow-template-pip.yml in full; substitute placeholders only.
- No config migration shims — unknown wiki config keys fail at load; document upgrades in CHANGELOG and wiki docs only.
Route first
| User intent | Read | Stop when |
|---|
| CLI missing, stale, or verify install | references/install.md | CLI verified or blocker reported |
New wiki, wiki init, tweak step | references/init.md | Scaffold summarized |
| Audit, improve, pre-PR, lint/check failures | references/improve.md | Findings report delivered |
| Formatting, linting, check categories detail | references/audit.md | Audit criteria verified |
| Generate handoff plans, plans layout | references/plan.md | Plan file written |
| Execute plans, review diff, publish issues | references/loop.md | Executor output verified |
| GitHub Pages, deploy workflow, CI publish | references/deploy.md | Workflow + URLs summarized |
When the user asks for multiple intents in one message, pick the blocking workflow first (usually install), or the workflow they emphasized. Offer the next step in plain language.
Shared CLI resolution
Before any wiki command:
- Run
bash skills/wiki/scripts/verify.sh (or .agents/skills/wiki/scripts/verify.sh when vendored).
- Exit
0 → use PATH wiki.
- Exit
2 (stale) → upgrade wazootech-wiki per install.md.
- Exit
1 (missing) → install or stop with one-line PyPI hint; read install.md for paths.
In the Wiki CLI repository checkout, if PATH wiki fails but pyproject.toml exists, use uv run wiki or python -m wiki when both --help and fmt capability pass.
Zero-install equivalent: npx wazootech-wiki <args> or uvx wazootech-wiki <args> in place of wiki <args>.
Deterministic scripts
bash skills/wiki/scripts/verify.sh
bash skills/wiki/scripts/audit.sh -c path/to/wiki.yml [FILE...]
audit.sh runs fmt → lint → check → render (--strict / --check), then wiki link --check only when wired in .github/workflows/. In this repo: -c docs/wiki.yml.
Reference index
Human docs: Wiki Skills, Getting Started, Wiki Programmatic API.
