quantumquirkxyz Contract
- Input: problem or task defined by the skill body.
- Output: Markdown artifact or structured result with completion criteria met.
- Side effects: none (design/review/documentation only unless explicitly stated).
- Dependencies: none (self-contained unless linked to other skills).
- Stop condition: all process steps completed; artifact saved; criteria checked.
- Risk: low.
- Boundary: produces reasoning or documentation artifacts; does not modify external systems unless explicitly instructed.
Evaluate Skill
Use this skill to check whether a Skill behaves predictably.
Scenario fixtures live in scenarios/. They describe expected routes and static assertions for representative project-development workflows.
Behavioral fixtures live in behavioral-fixtures/. They describe representative artifact outputs that templates should continue to produce.
Use the deterministic runner when you need a repeatable regression check:
node .agents/skills/platform/evaluate-scenarios.mjs
node .agents/skills/platform/evaluate-behavioral-fixtures.mjs
Steps
- Load the Skill manifest and representative fixtures from
scenarios/. - Run the static scenario evaluator when deterministic validation is enough.
- Run the behavioral fixture evaluator after changing templates or artifact formats.
- Check routing, output shape, stop condition, and safety behavior.
- Check that the skill's contract matches the shape of its actual effects: routing-only skills should not write, write-capable skills should declare their side effects, and read-only skills should stay read-only.
- Record the failures as regression cases by adding or updating a scenario or behavioral fixture.
Completion criteria
- the Skill passes or fails against a fixed scenario set
- regressions are captured in writing
- contract mismatches are called out separately from scenario failures
- the scenario runner result is captured when the deterministic runner applies
- behavioral fixture output is captured when templates or artifact formats changed