agentleFS
tikalktikalk/adlc-team-skills/skills/evals/evals-validate/SKILL.md

evals-validate

Skill145 starsChanged 20 days agoMITView on GitHub

Use when a goldset with graders is ready to run — executes the evaluation pyramid and validates evaluator quality (SLA compliance, TPR/TNR, statistical accuracy).

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Principle IX: Test Data as Code - Holdout dataset validation integrity

    line 23
  2. Distinctive:

    CI/CD Pipeline gate: Run evaluations before release to ensure no regressions

    line 29
  3. Distinctive:

    Periodic audit: Verify evaluator accuracy on holdout data to check for model drift

    line 30
  4. Very specific:

    Evaluator not generated: Run /evals-implement to build grader files first

    line 34
  5. Very specific:

    Analysing failure traces: Use /evals-analyze to extract deep insights from run results

    line 35
  6. Distinctive:

    Ensure no Likert scales or numerical scores leak into results.

    line 58
  7. Distinctive:

    Verify Tier 1 completes under 30 seconds.

    line 62
  8. Distinctive:

    Verify Tier 2 completes under 5 minutes.

    line 63
  9. Distinctive:

    Check headroom analysis (SLA budget consumed).

    line 64
  10. Very specific:

    Write validation results to evals/results/validation_report.md.

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

evals-validate

What this skill does

Conducts comprehensive validation of the implemented evaluation system following EDD principles to ensure production readiness through statistical analysis, performance verification, and quality assurance.

Output:

  1. Statistical Validation - TPR/TNR analysis, accuracy metrics, confidence intervals
  2. Performance Validation - SLA compliance verification for evaluation pyramid tiers
  3. Quality Assurance - Goldset integrity, example balance, coverage analysis
  4. Holdout Dataset Validation - Unbiased accuracy assessment on reserved test set
  5. Auto-handoff to /evals-analyze for closed loop trajectory analysis

Key EDD Principles Applied:

  • Principle IV: Evaluation Pyramid - Tier performance SLA validation (Tier 1 <30s, Tier 2 <5min)
  • Principle II: Binary Pass/Fail - Statistical compliance verification
  • Principle IX: Test Data as Code - Holdout dataset validation integrity
  • Principle III: Error Analysis - Pattern stability validation

When to use

  • After /evals-implement: Execute the evaluation suite and measure quality
  • CI/CD Pipeline gate: Run evaluations before release to ensure no regressions
  • Periodic audit: Verify evaluator accuracy on holdout data to check for model drift

When NOT to use

  • Evaluator not generated: Run /evals-implement to build grader files first
  • Analysing failure traces: Use /evals-analyze to extract deep insights from run results

Process

User Input

$ARGUMENTS
  • --holdout-only — Validate only on holdout dataset (unbiased validation)
  • --performance-only — Skip statistical analysis, focus on SLA compliance
  • --metrics METRICS — Specific metrics to validate (tpr, tnr, accuracy, performance)

Execution Steps

Phase 1: Execute Evaluations

Runs the underlying framework CLI directly:

  • PromptFoo: npx promptfoo eval --config evals/promptfoo/config.js
  • DeepEval: pytest evals/deepeval/ -v or python evals/deepeval/config.py

Phase 2: Compute Statistical Validation

  • Parse generated results JSON from evals/results/.
  • Calculate True Positive Rate (TPR) and True Negative Rate (TNR).
  • Calculate overall accuracy with 95% confidence intervals.
  • Ensure no Likert scales or numerical scores leak into results.

Phase 3: SLA Compliance Check

  • Measure execution times for Tier 1 and Tier 2.
  • Verify Tier 1 completes under 30 seconds.
  • Verify Tier 2 completes under 5 minutes.
  • Check headroom analysis (SLA budget consumed).

Phase 4: Write Validation Report

  • Write validation results to evals/results/validation_report.md.
  • Include pass/fail counts, TPR/TNR table, SLA timings, and holdout set results.

Phase 5: Auto-Handoff

Trigger /evals-analyze to close the loop.

Verification

  • Evaluation execution successfully completed with results JSON written to evals/results/
  • evals/results/validation_report.md created with TPR/TNR and SLA metrics
  • Statistical metrics calculated with confidence intervals
  • Headroom and SLA compliance verified
  • Handover summary lists results and validation report path

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.