agentleFS
poorvith-mppoorvith-mp/skills-developer/skills/llm-evals/SKILL.md

llm-evals

Skill0 starsChanged 3 months agoMITView on GitHub

Build evaluation harnesses: regression sets, scoring rubrics, drift detection and benchmarks. Use when building LLM evaluation harnesses, scoring rubrics, or drift benchmarks.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    NEVER deploy prompt changes without running the eval suite first.

    line 38
  2. Distinctive:

    NEVER use a single metric (e.g., only accuracy) to evaluate multi-dimensional LLM output.

    line 39
  3. Distinctive:

    NEVER treat eval datasets as static.

    line 40

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Llm Evals

Architects automated evaluation infrastructure for AI/LLM systems to ensure output quality, detect drift, and prevent regression.

Phased Workflow

Phase 1: Evaluation Dataset Design

  1. Curate golden test datasets with human-annotated ground truth across representative task categories.
  2. Define scoring dimensions: Accuracy, Relevance, Completeness, Tone Adherence, Safety, Latency.
  3. Build adversarial test cases targeting known failure modes (hallucination, refusal, format violation).

Phase 2: Scoring & Comparison Infrastructure

  1. Implement automated scorers: exact match, semantic similarity (embedding cosine), LLM-as-judge, regex validators.
  2. Build A/B comparison pipelines for prompt version testing (old prompt vs new prompt).
  3. Set up drift detection: track score distributions over time windows and alert on statistical deviation.

Phase 3: CI Integration & Reporting

  1. Integrate eval suite into CI/CD pipeline as a required gate before prompt/model deployment.
  2. Generate eval reports with pass/fail rates, score distributions, and regression flags.
  3. Maintain versioned eval datasets alongside prompt versions for reproducibility.

Verification & Quality Checklist

  • Golden dataset covers minimum 50 representative test cases per task category.
  • Scoring rubrics are deterministic and reproducible across runs.
  • Drift detection thresholds calibrated against baseline performance windows.
  • Eval pipeline runs in under 10 minutes for rapid feedback loops.

Anti-Patterns & Constraints

  • NEVER deploy prompt changes without running the eval suite first.
  • NEVER use a single metric (e.g., only accuracy) to evaluate multi-dimensional LLM output.
  • NEVER treat eval datasets as static; refresh quarterly with new edge cases.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.