eval-cs-skill

Evaluates and optimizes CodeStable skills through fixture-based multi-model experiment loops.

1.1k|83|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/liuzhengdongfortest/easysdd --skill eval-cs-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eval-cs-skill
Source: https://github.com/liuzhengdongfortest/easysdd/tree/main/.claude/skills/eval-cs-skill
Command: npx skills add https://github.com/liuzhengdongfortest/easysdd --skill eval-cs-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Writing and improving AI agent skills is usually guesswork: you edit a prompt, eyeball a few outputs, and ship. This Skill turns skill authoring into a measurable engineering loop—author, evaluate across models and harnesses, optimize with pre-registered hypotheses, and release with regression evidence—so every change to a skill is backed by tagged, reproducible measurements.

Core Features & Use Cases

  • Four-stage lifecycle: author, eval, optimize, and release stages, each with its own protocol reference and a state machine that resumes from repository facts in experiments/.
  • Deterministic evaluation harness: bundled runner, scorers (planted-defect recall, DoD gate, LLM judge), and prompt builders execute a skill snapshot against fixtures across multiple models and harnesses with cost guardrails.
  • Cognitive honesty enforcement: every number carries a [measured], [soft], or [underpowered] tag; hypotheses must be git-committed before any LLM run; judge models must be independent from tested models.
  • Use Case: You rewrote the cs-review skill and want to know if it actually catches more defects. Run the eval stage against planted-defect fixtures on two model families, then let the optimize loop test variants until the convergence criteria are met, and release with a version bump and regression battery.

Quick Start

Ask the agent to evaluate the cs-review skill with eval-cs-skill, starting with a dry-run cost estimate before running the full experiment.

Frequently Asked Questions about eval-cs-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate whether a prompt or skill change actually improves results?

Define fixtures with known answers (planted defects, golden tasks), then run the skill snapshot against them across at least two models using the runner script. Scorers produce tagged metrics like recall and DoD pass rate, so improvements are measured rather than eyeballed.

How do I test an AI agent skill across multiple models?

Declare model_list and harnesses in the experiment config.json, then run runner.py with the experiment directory. The harness executes the skill as injected snapshot text per fixture and model, recording wall time, tokens, and cost per run.

What is the eval-cs-skill optimize loop?

The optimize stage runs an autoresearch cycle: pre-registered hypotheses, variant generation, evaluation, keep/kill decisions, and convergence checks against dual value functions V_instance and V_meta. Each iteration is persisted as iteration-N.md with tagged scores.

Why must hypotheses be committed to git before running evaluations?

Committing hypotheses.md before any LLM run freezes the pre-registration, preventing post-hoc hypothesis editing. The optimize script mechanically verifies commit timestamps precede the first run artifacts, and violations void the pre-registration score.

Can the judge model be the same as the model being tested?

No. The config validation rejects a judge_model that appears in model_list because same-source judging creates confounded scores. The judge must be an independent model, and calibration fixtures verify its pairwise accuracy before scores count as measured.

What are the limitations of mock harness evaluation?

Mock harnesses produce no real model output, so generative fixture kinds like design and docs yield no signal offline. Scores from mock runs stay tagged as soft, and meaningful evaluation requires real harness and model targets.