Skip to content
Back to skills

Llm Evaluation

ASecurity

Design and run an evaluation for an AI or agent feature using representative tasks, explicit success criteria, failure taxonomy, baselines, and reproducible evidence.

  • 16 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 11, 2026
ai-agents

Security analysis

A100/100

Scanned September 11, 2026

npx -y skills add Dadmin88/hermes-profile-packs --skill llm-evaluation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Llm Evaluation?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Llm Evaluation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dadmin88-llm-evaluation/badge)](https://www.skillsdirectory.com/skills/dadmin88-llm-evaluation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: llm-evaluation
description: Design and run an evaluation for an AI or agent feature using representative tasks, explicit success criteria, failure taxonomy, baselines, and reproducible evidence.
---
# LLM Evaluation

Use before relying on a model, prompt, retrieval flow, or agent behavior in a consequential product workflow.

## Procedure
1. Define the behavior being evaluated and the real user/task distribution it must serve.
2. Build representative test cases including normal, difficult, adversarial, ambiguous, and known-failure examples.
3. Define scoring criteria before running the evaluation. Prefer observable task success and structured rubrics over vibes.
4. Establish a meaningful baseline: previous prompt/model, simpler method, human result, or deterministic system where appropriate.
5. Run with fixed configuration and record model, prompt/version, tools, retrieval inputs, temperature/reasoning settings, and relevant environment.
6. Classify failures by cause: instruction following, reasoning, retrieval, tool use, format, hallucination, safety, latency, or cost.
7. Compare changes on the same evaluation set and inspect regressions, not just average score.

## Quality gate
A model change is better only when evidence shows improvement on the intended task without unacceptable regression, cost, latency, or safety tradeoffs.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…