Current step
Agents receive the instructions needed now, not the entire playbook.
Loading
Guide for adopting Reactive Skills
Reactive Skills turns a long instruction file into an executable workflow. Agents see the current step, advance on evidence, and leave a durable run history.
npx -y @reactive-skills/axi init my-workflowThe core idea
You do not need to understand every implementation detail to adopt the model. Start with these three properties.
Agents receive the instructions needed now, not the entire playbook.
Signals move the workflow only when declared facts satisfy the guard.
Each transition leaves a record that can be inspected and resumed.
Choose your path
You can use an existing skill, author one for your team, or connect the runtime to your preferred agent host.
Install a workflow someone already made, then run it from your agent or terminal.
npx skills add Reactive-Skills/skills --skill <name>Turn a repeatable process into explicit states, evidence gates, and durable outputs.
npx -y @reactive-skills/axi init my-workflowSelect a compatible local AXI or MCP transport during startup. AXI uses shell commands, while MCP connects host tool panels.
npx -y @reactive-skills/axi mcpFollow one run
A passing demo proves little. A rejected guard shows that the workflow can stop, preserve state, and continue from evidence.
Live run
Refactor workflow
states/verify.md
Only active instructions are mounted.
exit_code == 0Run the check. The guard decides whether the workflow advances.
Mount
The agent receives only VERIFY instructions.
Reject
A failed check blocks progress and preserves state.
Resume
A passing result advances the workflow and records why.
The working contract
Each file has one job. You can inspect the structure directly, or let an agent help author and validate it.
skill.yamlThe workflow contractStates, signals, guards, and allowed tools.states/*.mdThe active instructionsOne focused prompt slice per state.guards/The evidence checksCode-backed conditions that decide progress..reactive/The run historyEvents, state, and projected deliverables.Name the workflow
Define one repeatable outcome and the context it needs.
Name the states
Break the work into focused phases with explicit stop criteria.
Name the evidence
Attach signals and guards that decide whether progress is valid.
Validate the contract
Inspect the statechart before asking an agent to run it.
Start authoring
The scaffold gives you a working runtime contract. Customization gives it your domain workflow.
See the package anatomyKnow the boundaries
Reactive Skills is not required for every prompt. It earns its place when a workflow spans multiple steps, tools, or sessions.
It does not make a model correct. It makes progress explicit and inspectable.
It does not replace tests, reviews, or human decisions.
It does not require a state machine for a one-off question or short script.
It does not hide failed guards. Rejections remain visible in the run history.
Next steps