resource verbs
Synopsis
Section titled “Synopsis”rigger <resource> <verb> [<id>...] [options]A second grammar addresses one nature at a time. The resource token
names a nature (or packs); the verb is the action. It is a typed front-end over the same commands:
skills add installs, validating that each id is a skill.
Resource tokens
Section titled “Resource tokens”Singular and plural forms are equivalent:
| Token | Maps to |
|---|---|
skill / skills |
skill |
agent / agents |
agent |
guardrail / guardrails |
guardrail |
context / contexts |
context |
plugin / plugins |
plugin |
hook / hooks |
hook |
tool / tools |
tool |
pack / packs |
pack |
catalog |
catalog sources (see catalog) |
| Verb | Action |
|---|---|
ls |
List entries of this nature. See ls. |
add <id>... |
Install the ids, each validated against the nature. |
info <id> |
Show one entry’s details and whether it is installed. |
check |
Audit installed entries of this nature. |
remove <id>... |
Uninstall the ids. See remove. |
update <id>... |
Update the ids. See update. |
Nature validation
Section titled “Nature validation”add, update, and remove require qualified ids. An
unqualified id is rejected:
[error] unqualified id "<id>" — use `<catalog>/<id>` (see `rigger ls`)An id whose nature does not match the resource is rejected with [error] id "<id>" is not a <singular>. add and update validate against the catalog;
remove validates against the manifest, so it stays offline.
Packs check
Section titled “Packs check”packs check is not supported. A pack is a bundle, not an installable target, so check has
nothing to audit for it:
[error] "packs check" is not supported — packs are bundles, not installable directly.Exit codes
Section titled “Exit codes”The delegated command’s exit codes apply (ls returns 0 once its arguments are valid; add,
remove, update, and check as documented on their own pages), plus 2 for a validation error:
an unqualified id, a nature mismatch, packs check, or an unknown verb. An unknown verb prints
Unknown verb "<verb>" for resource "<resource>". followed by usage.
See exit codes for the shared contract.
Example
Section titled “Example”rigger guardrails add team/guardrail:no-force-push --yes