Skill

how an agent learns to write a page

Contents

1Home
2Release
3References

The skill, writing-wiki-pages, is the instructions an agent follows to write a page: SKILL.md, and a references folder beside it.^[1] That folder holds the rules for naming, grammar, reference pages and flowcharts, and two worked examples, one for an ordinary page and one for a reference page, each written well and badly.^[1] wiki sync copies it into the project, where agents read it.^[2] Some of the rules it teaches are enforced by the Checks: citations, headings, pointing words, reading budgets and pictures. It forbids an agent to invent: everything on a page comes from the code, the owner's own words, or an outside service's own documentation, and a fact none of these gives is marked {missing} or left out.^[3]

Home

The skill goes into the project's .agents/skills folder if there is one.^[4] Otherwise it goes into .claude/skills, which is created if it does not exist.^[4] The first is preferred because the second is often a link to it, and writing through the link would write the same place twice.^[4]

The skill lands in a folder named after itself, and a file is rewritten only when its text has changed.^[5] A file that a newer release no longer ships stays in the project until it is deleted by hand.^[5]

wiki sync --skill-dir names the folder instead, relative to the project, and the skill goes there whatever else exists; the folder is created if it is missing.^[6] wiki sync --no-skill records the release without writing the skill, and asking for both at once is refused.^[7]

Release

wiki sync also records, in wiki.toml, which release of the tool the project is on.^[8] It replaces the first version line after [tool], or adds that table when there is none, and leaves the rest of the hand-written file alone.^[8] A [tool] table with no version line gets none, although wiki sync still prints that the release was recorded.^[8]

wiki check fails while that record is missing or names a different release, and it says to run wiki sync.^[9] A newer release can add a check, and a new check finds old pages; the record makes that failure expected rather than surprising.^[9]

References

src/builder/cli.py — SKILL_NAME names the skill; sync() copies every markdown file under SKILL, which src/builder/build.py finds with skill_dir().
src/builder/cli.py — sync().
src/skill/SKILL.md — the Truthfulness section, whose first rule is never to invent, and the last item of its definition of done.
src/builder/cli.py — skill_home() tries .agents/skills, then .claude/skills, and falls back to .claude/skills.
src/builder/cli.py — SKILL_NAME names the folder; sync() compares each file's text before writing it, and deletes nothing.
src/builder/cli.py — skill_home() joins a given folder to the project root before trying either convention.
src/builder/cli.py — sync() skips the copy when skill is false; main() puts --no-skill and --skill-dir in one mutually exclusive group.
src/builder/config.py — record_version() replaces the first line starting version after [tool], adds nothing when no such line follows, and appends the table when [tool] is absent; src/builder/cli.py — sync() prints the release either way.
src/builder/build.py — version_problems(), called from check().

Last updated 14 September 2026358 wordsabout 2 minutes to read9 sources cited0 claims with no source