Skills
A skill is a packaged procedure: instructions, and optionally the tools and files that go with it. Where a tool is one capability, a skill is a way of working.
Skills versus tools
A tool does one thing — open a pull request. A skill describes how your team does something — review a diff against a checklist, then open a pull request with the checklist result in the description. Skills call tools; the reverse is not true.
Installing and managing
arble skills install @acme/release-checklist
arble skills install ./skills/incident-review # local path, for development
arble skills disable @arble/pr-description # installed, hidden from planner
arble skills update @acme/release-checklist
arble skills rm @arble/pr-description$ arble skills ls
NAME VERSION STATE SCOPE
@acme/release-checklist 2.1.0 enabled project
@acme/incident-review 0.4.2 enabled project
@arble/pr-description 1.0.0 disabled globalDisable rather than uninstall
A disabled skill stays installed but is invisible to the planner. This is the right way to narrow what an agent considers for a particular kind of work, and it is reversible without reinstalling.
Pinning
Skills are pinned by default and belong in arble.json. A registry update that changes
how an agent behaves mid-sprint is a bad surprise; pinning prevents it.