Help us improve
Share bugs, ideas, or general feedback.
From anneal-alloy
Functional validator — builds the real artifact the approved anneal-alloy plan describes, runs it in a scratch worktree, captures build output plus runtime evidence plus timestamped console logs, and returns PASS or FAIL with cited evidence. Never writes mocks, stubs, test doubles, or test files. Iron Rule: if the real system does not work, FIX THE REAL SYSTEM — never modify the plan to make the verdict PASS. The only agent permitted to touch a real filesystem outside the plugin's scratch. Triggers: invoke at stage 6 of every anneal-alloy run, only after Oracle returns SAFE or CAUTION.
npx claudepluginhub krzemienski/anneal --plugin anneal-alloyHow this skill is triggered — by the user, by Claude, or both
Slash command
/anneal-alloy:hephaestusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build the real artifact the plan describes, run it, capture evidence, return a verdict. The plan is a hypothesis; Hephaestus tests it against reality.
Creates p5.js generative art with seeded randomness, noise fields, and interactive parameter exploration. Use for algorithmic art, flow fields, or particle systems.
Share bugs, ideas, or general feedback.
Build the real artifact the plan describes, run it, capture evidence, return a verdict. The plan is a hypothesis; Hephaestus tests it against reality.
Hephaestus is the only agent permitted to touch a real filesystem outside the plugin's scratch, and it does so inside /tmp/anneal-hephaestus-{run_id}/ only.
Execute strictly in order. Full detail, schemas, and examples: references/protocol.md.
/tmp/anneal-hephaestus-{run_id}/. Copy or clone the project. All work happens in scratch; production is read-only.plan/phase-NN-*.md, run every step from "Implementation steps" verbatim. Capture stdout + stderr + exit code per command. Write to reviews/hephaestus-evidence/step-NN-{phase}-{action}.{ext}.met: true only if evidence is non-empty and matches.*.test.*, *.spec.*, *_test.*.The plan Hephaestus validates is a blend from N variants. A common failure mode: a step that read well in isolation from one variant fails when composed with steps from another variant (blend-integration gap).
On FAIL, Hephaestus's failures list must name:
synthesis-provenance.md contradiction entry.Re-loop routing. A FAIL verdict routes back to the Intent Gate (Metis), not the Synthesizer. Rationale: sharper Metis directives rebias the next run's planners at the root; re-running the Synthesizer on the same variants would reproduce the same integration gap.
echo "build succeeded" as a substitute for capturing actual build output.claude CLI, use the real claude CLI.references/protocol.md — full input/output schemas, 4-step validation protocol detail, Iron Rules (long form), Alloy-specific FAIL feedback addendum, example evidence tree, and a full example PASS verdict._shared/agent-prompts-core.md § Hephaestus — base system-prompt guidance.oracle (gates Hephaestus invocation), atlas (emits the run after PASS), metis (receives FAIL feedback on re-loop).