Agent skills and the plugin

st plugin install puts the orchestration skills in Claude Code and Codex, so an agent knows the st worker commands.

An agent learns the orchestration commands from a skill. st carries the skills and puts them where Claude Code and Codex look for them. st 0.3.67 or later.

Installing with st

st plugin install      # the Claude Code plugin and the Codex skills
st plugin status       # what is installed
st plugin uninstall    # take them out

st plugin install puts in:

  • Claude Code: the sophonz plugin, from a local marketplace in ~/.sophonz/plugins, installed for your user. New sessions get /sophonz:orchestrate. Its second skill, the worker's, is not one you call: it is for agents st started as workers.
  • Codex: the skills sophonz-orchestrate and sophonz-worker, in ~/.codex/skills (or $CODEX_HOME/skills).

When claude is not on the PATH, st writes the files and says how to start Claude Code with them (--plugin-dir), or to run st plugin install again later.

The guides the agents read

To read what the agents read, run:

st skills get orchestrate     # the coordinator's guide
st skills get worker          # the worker's guide

Starting

Run st hooks install once if you have not. Then open Claude Code in a pane of a session st shares and ask with /sophonz:orchestrate:

/sophonz:orchestrate Give the API tests to Codex and the README cleanup to another
Claude, then check both results and tell me.

In Codex, ask the same in plain words, or name the sophonz-orchestrate skill. An agent started as a worker knows it is one and loads the worker's guide.

What happens next is on Orchestration and Workers.