evaluate-stochastic-systems

Evaluate Stochastic Systems

Use this skill before claiming an LLM-backed behavior is correct, reliable, or ready.

Required Discipline

Load references/eval-design.md.

• Measure rates over an eval set, not anecdotes.
• Include pass, fail, partial, and adversarial fixtures.
• Repeat stochastic cases with k samples (k samples) when randomness, retries, routing, or agent planning can change outcomes.
• Set thresholds before running the eval.
• Track regressions by adding cases for every meaningful failure category.
• When a new reusable failure appears in this marketplace, suggest filing a repo-level GitHub Eval case issue. If the eval-case-reporter plugin is available, use its submit-eval-case skill so the case is scrubbed, previewed, approved, and posted consistently.
• Keep deterministic checks for contract behavior and calibrated judgment for semantic quality.
• Refuse to treat one successful run, one demo, or one hand-picked example as proof.
• A single good run is a demo, not proof.

Output Bar

For any eval recommendation, produce:

• The behavior under test.
• The fixture source and expected outcome.
• The scoring method.
• The sample count and aggregation rule.
• The pass threshold and release gate.
• The failure taxonomy used to grow the suite.
• The artifact path that preserves results for review.