Imported from wycats/exo2 (
plugins/exo/skills/exo/SKILL.md). Install upstream withnpx skills add wycats/exo2 --skill exo. Copyright stays with the author.
Exo
Use the exo-run MCP tool as the authoritative interface to Exo project state.
Operating Rules
- Start an Exo work session with
exo-runcommandstatus, then read the task plan withtask listwhen task state matters. - Send commands without the leading
exo; for example, usestatus,task list, ortask complete <id> --log $1. - Treat
exo-runas an Exo CLI-language runner, not a shell. Do not use pipes, redirects, command substitution, environment assignment prefixes, or glob expansion. - Use the
argsarray with$1,$2, and later placeholders for multiline text instead of shell escaping. - Keep the phase loop current with Exo commands as work progresses.
Confirmations
- If Exo asks for execution approval, ask the human whether to approve the action in plain language. If they approve, continue the same action with the hidden approval data returned by Exo.
- If Exo asks for outcome review, ask the human the question and options Exo returned. If they approve recording the completed outcome, continue the same completion command with the hidden approval data.
- Do not display hidden confirmation fields, raw JSON, tickets, or protocol names to the user unless they explicitly ask for raw protocol details.
