a554b554/Reactant / skills/skill-generator
skill-generator
VerifiedReactant direct-entry skill authoring utility. Use when the user directly asks to create a project-local Reactant tag skill from a natural-language description; it has no inline tag form and is never dispatched by execute or execute-one.
Skill Generator
Entry Boundary
This is a direct entry skill, alongside execute and execute-one. It is not
a Reactant tag skill or document router. Activate it only from an explicit
user request to create a Reactant project-local skill, such as:
/skill-generator a translate skill that preserves citations and LaTeX commands
There is no inline form for this entry skill. execute and execute-one must
never select or dispatch an apparent generator annotation in an authored
document. Do not read, consume, or edit a document merely to obtain the
generator request.
The generated directory is a standard Agent Skill. The router agent discovers the new worker by reading project skill roots on its next invocation; there is no registry and no programmatic tag scanner.
Input
Accept the user's direct natural-language description of the new skill and the current project root. If the intended behavior, name, or file effects are materially ambiguous, clarify them before creating files.
Workflow
- Read the description and
references/skill-contract.mdin this skill directory. Infer the requested behavior without reducing the description to a machine tag grammar. - Choose a name made of lowercase letters or numbers separated by single
hyphens. It must not be a reserved name (
execute,execute-one,skill-generator,chat-user,resolve,chat-model,comment) or collide with another skill unless the user explicitly requests an allowed override. - Inspect the project-local skill root and create
.reactant/skills/if it does not exist. - Write
.reactant/skills/<name>/SKILL.mdaccording to the contract: YAML frontmatter with a matchingname, a description explicitly limiting activation to router-dispatched tags, anActivation Boundarysection, tag examples, input behavior, workflow, scope-modifier and context-reference handling, consumption behavior, and clean failure behavior. Add supportingscripts/,references/, or assets only when the skill needs them; keep the skill self-contained. - Validate the directory by reading it against the structural contract: frontmatter, naming, required behavior, self-containment, and reserved-name rules. If an optional structural Agent Skills or Reactant validator is available, it may be run as an additional check. Such a validator must not scan authored documents or classify annotations.
- Fix any structural errors and validate again. If the skill cannot be made valid, remove only the incomplete directory created by this invocation and report the diagnostics.
- Report the created path and the generated worker's annotation form. Do not modify an authored document as part of generation.
Rules
- Generated skills are tag-only workers; this generator does not create new entry skills.
- Validation is structural only. Reactant does not semantically verify what a generated skill will produce at runtime.
- Phase 1 skill generation and routing require no Python runtime or vendored
reactant_core.py. - On failure, do not leave an incomplete generated directory. Preserve all pre-existing project files and report the problem.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |