eval-runner

Solid

Run eval scenarios to benchmark Mycelium effectiveness. Execute tasks using reflexion loop, validate against success criteria, record metrics.

AI & Automation 45 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 86/100

Stars 20%
55
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Eval Runner Benchmark the agent's performance against defined scenarios. Adapted from n-trax eval system. ## Commands ### `run <category/name>` 1. Read YAML from `.claude/evals/scenarios/<category>/<name>.yml` 2. Parse fields (name, category, task_prompt, success_criteria, budget) 3. Execute setup steps if defined 4. Record start time 5. Execute task via reflexion workflow (read corrections first) 6. Record end time and iteration count 7. Validate ALL success criteria 8. Write result JSON to `.claude/evals/results/<timestamp>-<name>.json` 9. Report summary ### `run-all [category]` 1. Glob `.claude/evals/scenarios/**/*.yml` 2. Skip scenarios with `status: retired` 3. For each: run in isolation (git stash), record result, restore 4. Update `.claude/evals/pass-history.json` with each result 5. Aggregate and report ### `run-split <optimization|holdout>` 1. Glob `.claude/evals/scenarios/**/*.yml` 2. Read each YAML, filter by `split` field matching the requested set 3. Skip scenarios with `status: retired` 4. For each matching scenario: run in isolation, record result, restore 5. Update `.claude/evals/pass-history.json` with each result 6. Aggregate and report (label output clearly as "Optimization Set" or "Holdout Set") ### `report` 1. Read all results from `.claude/evals/results/` 2. Generate summary table: ``` | Category | Pass Rate | Avg Iterations | Avg Time | Notes | |-------------|-----------|----------------|----------|-------| | discovery | ... | ... ...

Details

Author
haabe
Repository
haabe/mycelium
Created
5 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

eval

Run the context fitness-function probe suite (.oh/evals/probes/*.sh) against real state and write the .oh/evals/RESULTS.md benchmark. Each probe is a deterministic 3-state oracle (PASS/REGRESSION/SKIPPED); a green→red transition is surfaced as a REGRESSION naming the lesson it closes. Tier-B behavioral evals are out of scope. TRIGGER when: asked to run evals, check the probe suite, "run /eval", verify a lesson's probe is green, benchmark the harness, or before/after editing a rule/skill that a probe guards.

38 Updated today
mifunedev
AI & Automation Listed

eval-run

Run the offline LLM eval harness and gate on regression. Detects the project's own eval framework (promptfoo / OpenAI-evals / deepeval / ragas / LangSmith / a custom pytest harness), loads the versioned dataset, runs each case through the CURRENT prompt+model+retrieval, scores with the configured scorers (assertion + LLM-as-judge), diffs against the stored baseline, and FAILS below threshold. Emits a per-metric table + the regressed cases with their cited case-id + score. The measurement half of every prompt/model/retrieval change — dispatched by @ai-feature-reviewer and /add-ai-feature's Evaluate phase.

1 Updated today
adnanmokhtar
AI & Automation Listed

eval-run

Launch a model evaluation batch. Use when running interactive/foreground eval runs — parameter collection, pre-flight checks, execution, and post-run analysis. NOT for: long-running batches that need tmux isolation (use overnight-eval instead).

0 Updated today
SamyakJhaveri