Procedural Knowledge for coding agents lives in the Wiki CLI repository under skills/. The wiki skill routes operational workflows to focused references, and wiki-feedback handles integration proposal feedback. Skills are not wiki pages — do not add skills/ to wiki.inputs.
Onboarding workflows are independent modules with no required order. Each completes its job and stops unless the user asks for the next step in the same turn.
Canonical operational skill file: skills/wiki/SKILL.md. Integration proposal feedback lives in skills/wiki-feedback/SKILL.md.
Install via skills.sh
Install agent skills with the Skills CLI (npx skills). Source repository: wazootech/wiki. Browse the ecosystem at skills.sh.
Badge for your README
[](https://skills.sh/wazootech/wiki)
npx skills add wazootech/wiki@wiki -g -y
npx skills add wazootech/wiki@wiki-feedback -g -y
npx skills add wazootech/wiki@wiki-sync -g -y
# List skills without installing
npx skills add wazootech/wiki --list
Use -g for a user-wide install (~/.agents/skills/). Omit -g to install into the current project only (.agents/skills/). -y skips confirmation prompts.
Refresh after upgrades
When Wiki CLI ships skill fixes (deploy templates, init guidance), re-run:
npx skills add wazootech/wiki@wiki -g -y
Project-local copies under .agents/skills/ do not update automatically. Avoid committing vendored skill snapshots unless intentional; they can drift from upstream quickly.
Workflows and routing
The wiki skill routes operational workflows to focused references:
| Intent | Reference | Stop when |
|---|---|---|
| CLI missing or stale | skills/wiki/references/install.md |
CLI verified or blocker reported |
New wiki / wiki init |
skills/wiki/references/init.md |
Scaffold summarized |
| Audit / pre-PR / lint failures | skills/wiki/references/improve.md |
Findings report delivered |
| GitHub Pages / CI deploy | skills/wiki/references/deploy.md |
Workflow + URLs summarized |
Read one reference per turn unless the user explicitly asked for a multi-step flow (for example install → create → deploy).
The wiki-feedback skill handles ecosystem feedback and integration proposals. Use it when comparing an external tool with Wiki CLI, drafting a template proposal issue, or turning an integration idea into a repeatable GitHub issue. It reviews existing template issues in the wiki-templates monorepo first, preserves the boundary between Wiki CLI and downstream integrations, and recommends the integration-template.yml issue form in wazootech/wiki-templates for final filing.
The wiki-sync skill maintains code wikis (a repo's docs/ folder, e.g. wazootech/sparql-engine) — the Git-anchored delta process that keeps documentation truthful to source after code changes: anchor at docs/.sync-base, diff origin/main forward, check file inventory with git ls-tree, edit only the affected pages, validate, and land. It defaults to drift-free docs — no line numbers, machine-specific measurements, or test counts — with an opt-in detail_level directive in the repo's AGENTS.md (line-numbers, measurements, or full) that re-enables the execute-to-verify steps (deno doc --json lines, runner counts, bench snapshots). Canonical file: skills/wiki-sync/SKILL.md.
Scripts
bash skills/wiki/scripts/verify.sh
bash skills/wiki/scripts/audit.sh -c path/to/wiki.yml [FILE...]
verify.sh exits 0 when wiki and fmt capability pass, 1 when missing, 2 when stale. audit.sh runs fmt → lint → check → render (--strict / --check), then wiki link --check only when wired in .github/workflows/.
Install workflow
Detect whether wiki is on PATH, install wazootech-wiki when needed, verify with wiki --help and a fmt capability probe, and exit with a ready-to-go message. Does not suggest wiki init unless the user asks.
See skills/wiki/references/install.md.
Init workflow
Non-interactive wiki init for wiki project structure (config, starter pages), then a short tweak step: replace the starter first page, and optionally uncomment blocks in wiki.yml. Requires wiki on PATH before any init or file edits. Default post-init wiki check --strict with opt-out.
See skills/wiki/references/init.md and wiki init.
Improve workflow
Survey a wiki as a read-only advisor: run validators, cite evidence, deliver a prioritized findings report. Never edits wiki files unless explicitly asked. Suggest repairs (wiki fmt, wiki link --fix-broken) only when asked.
See skills/wiki/references/improve.md, Wiki Configuration, and Design Philosophies.
Deploy workflow
Align site.base_url, add .github/workflows/deploy.yml from wholesale templates, set the correct upload-pages-artifact path, and remind you to enable Pages → GitHub Actions. Requires wiki on PATH and an existing wiki config (wiki.yml, or legacy wiki.yaml).
Workflow assets (embed one template in full; substitute CONFIG_PATH, SITE_BASE_URL, ARTIFACT_PATH only):
skills/wiki/references/workflow-template-uv.yml— uv monoreposkills/wiki/references/workflow-template-pip.yml— pip standalone
See skills/wiki/references/deploy.md (which includes the Deploy Alignment Checklist) and Deploying to GitHub Pages.
Repository layout
skills/
wiki/SKILL.md
wiki/scripts/audit.sh
wiki/scripts/verify.sh
wiki/references/install.md
wiki/references/init.md
wiki/references/improve.md
wiki/references/audit.md
wiki/references/plan.md
wiki/references/loop.md
wiki/references/deploy.md
wiki/references/workflow-template-uv.yml
wiki/references/workflow-template-pip.yml
wiki-feedback/SKILL.md
Human-oriented install and daily workflow: Getting Started.