skills
A skill is a directory of markdown that the agent reads when it needs to do a specific task. It is one more set of files in the ant. The agent ships with a built-in set, and the operator can add more. Skills do not start on their own: every turn tells the agent to run /solve, which matches skills through /dispatch.
A skill is one directory with a SKILL.md
A skill is one directory under ant/skills/. Every skill has a SKILL.md with YAML frontmatter and a body:
---
name: skill-name
description: one-line summary; say in prose when the skill applies
---
Skill instructions here...A name must match ^[a-z0-9\-]+$, and the installer rejects every other name. Next to SKILL.md, the directory can hold reference files such as *.md and executable helpers such as *.sh and *.ts.
Packages and groups supply skills
Core is an ordinary package installed for every group. Other packages add skills through their skills/ directories. The renderer mounts selected skills read-only: core first, then packages in the order the operator added them. The later same-name skill wins.
A group can keep writable custom skills under ~/.claude/skills/. A local .disabled marker suppresses a packaged skill mount. Group selections inherit no parent directory.
The prompt tells the agent to find its skills
The core package installs a UserPromptSubmit hook. The hook adds a note that tells the agent to run /solve first. It adds the note to every prompt, with a stronger new-task text on the first prompt of a session and after 20 idle minutes. /solve decides whether the context already holds what the answer needs, recalls when it does not, runs /dispatch and checks claims before the reply. /dispatch compares the description of every skill with the request and loads the matches.
Package updates start no migration turn
Startup installs released core assets; an explicit arizuko package sync updates other selected sources. The next turn reads those assets. Packages documents sources, native hooks, host builds and guest paths.
Release announcements use configured routes
The router queues one short notice for each configured #announce destination: the release version, first changelog bullet and changelog link. The existing outbound queue handles delivery. A group with no announcement route gets no release notice and no release-triggered agent turn.
The upgrade guide covers images and verification; the changelog records each release.