agentleFS
salmandevsalmandev/everything-gemini/skills/agent-evals/SKILL.md

agent-evals

Skill2 starsChanged 28 days agoApache-2.0View on GitHub

Designs, executes, and benchmarks AI agent evaluation pipelines, LLM-as-a-judge scoring rubrics, golden test datasets, and prompt regression testing harnesses.

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-security.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mattpartidaSkill

    agent-security

    Review and harden OpenClaw/Hermes agent security, including tool permissions, elevated access, exec approvals, allowlists, sandboxing, browser and web exposure, prompt-injection risk, model risk, persistence, and personal-vs-shared trust boundaries. Use when the task is primarily about agent or runtime security rather than host firewall or OS hardening.

    Also in 3 projects that use this

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 5 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:

    Prefer deterministic, unit-testable assertions (schema validation, regex matching, exit codes, latency limits) before falling back to …

    line 15
  2. Distinctive:

    When assessing agent output quality, evaluate across four standardized vectors:

    line 25
  3. Distinctive:

    When using Gemini as an automated evaluator, structure the prompt with strict zero-shot rubrics and JSON output:

    line 38

“Common” is measured: kept by at least 6 in 10 of the 5 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

Agent Evals & LLM Benchmark Playbook

This skill guides the creation of automated evaluation harnesses, LLM-as-a-judge scoring pipelines, and regression testing suites for AI agents and LLM applications.


1. Core Principles

  1. Deterministic Assertions First:
    • Prefer deterministic, unit-testable assertions (schema validation, regex matching, exit codes, latency limits) before falling back to subjective LLM judges.
  2. Golden Datasets with Ground Truth:
    • Maintain versioned golden evaluation datasets (evals/golden.jsonl) pairing input prompts with expected outputs or behavioral criteria.
  3. Regression Containment:
    • Any prompt revision or model switch must run against the baseline eval suite to measure accuracy deltas, token consumption, and latency shifts.

2. Evaluation Dimensions

When assessing agent output quality, evaluate across four standardized vectors:

DimensionMetricMeasurement Method
Accuracy / CorrectnessFactual precision, task fulfillmentLLM-as-a-judge with binary pass/fail rubric
Safety & AlignmentInjection vulnerability, secret leakageAutomated static analysis & safety classifiers
Schema ComplianceValid JSON, Pydantic type conformanceDeterministic parser validation (json.loads, Pydantic)
Context EconomicsToken count, time-to-first-token (TTFT)Profiler logs & Gemini metadata tokens

3. LLM-as-a-Judge Scoring Template

When using Gemini as an automated evaluator, structure the prompt with strict zero-shot rubrics and JSON output:

EVAL_SYSTEM_PROMPT = """You are an impartial, expert evaluation judge. 
Assess the candidate agent response against the provided Reference Criteria.
Provide a structured JSON evaluation adhering to the schema:
{
  "score": <float 0.0 to 1.0>,
  "reasoning": "<concise explanation of strengths and shortcomings>",
  "violations": ["<list of any missed constraints>"]
}
Only output valid JSON.
"""

4. Eval Runner Execution Flow

  1. Load Test Suite: Ingest test cases from evals/test_cases.jsonl.
  2. Execute Candidate Prompt: Query the model with temperature=0.0 for reproducible benchmarking.
  3. Run Deterministic Checks: Validate JSON schema, required keys, and formatting constraints.
  4. Run LLM Judge: Pass model output + reference criteria to the evaluator.
  5. Aggregate Metrics: Calculate overall pass rate, p95 latency, and token cost per run.

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.