execute-one

Execute One

Execute exactly one Reactant annotation: the first actionable tag in source order. The host agent is the parser. Do not call or rely on a programmatic tag scanner, parser, AST, or dispatch classifier.

Entry and Dispatch Boundary

Reactant has three direct entry skills: execute, execute-one, and skill-generator. The first two are document routers. skill-generator is a direct project-authoring utility, has no inline tag form, and is never dispatched by a router. All remaining Reactant skills are tag-only workers. Invoke a worker only after this router has selected its exact actionable annotation from the target document. Never invoke a worker because ordinary chat, authored prose, or another skill merely resembles its capability.

Usage

/execute-one <file>

Resolve a relative file path against the current working directory.

Annotation Interpretation

Read the whole document and use its structure and meaning to interpret <@skill-name> / <@skill-name: prompt> annotations. Prompts may wrap across lines.

• Skip <@comment: ...> and paired <@chat-model> response data.
• Skip a chat-user turn already followed by its model response.
• Do not execute tags that are being shown as documentation, quoted examples, or code samples. A leading backslash is an optional explicit hint, not a required escape grammar.
• Leave ambiguous, malformed-looking, and unknown tags unchanged; report them instead of guessing.
• execute, execute-one, and skill-generator are entry skills, not inline operations. Preserve and report an apparent annotation using any of those names; never dispatch it.

Skill Discovery

For the selected annotation, look for the matching SKILL.md in project-local .reactant/skills/, configured skill_roots in order, and then the bundled Reactant skills available in the current host/install. Project-local skills may not shadow execute, execute-one, skill-generator, chat-user, resolve, chat-model, or comment. Report ambiguous collisions and do not dispatch them.