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
- toy-crane/claude-code-playbook-templatetheir own version, first seen Nov 8, 2026
- reddygopalkrishna/developer-agent-skillstheir own version, first seen Nov 8, 2026
- krzysztofsurdy/code-virtuosotheir own version, first seen Nov 1, 2026
- VoDaiLocz/kilo-kit-mcptheir own version, first seen Aug 21, 2026
- saitarrun/Devforge-aitheir own version, first seen Jun 20, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- toy-crane/claude-code-playbook-template★ 77same name
- krzysztofsurdy/code-virtuoso★ 36same name
- VoDaiLocz/kilo-kit-mcp★ 28same name
- reddygopalkrishna/developer-agent-skills★ 8same name
- saitarrun/Devforge-ai★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository134 other files it gives its agents.
- accessibility-engineerSkill
- accessibility-fixSkill
- ai-data-remediation-engineerSkill
- ai-engineerSkill
- ai-eval-suite-builderSkill
- android-developerSkill
- api-designSkill
- api-lifecycle-engineerSkill
- appsec-architectSkill
- audit-readinessSkill
- authenticationSkill
- autonomous-optimization-architectSkill
- backend-architectSkill
- backend-buildSkill
- blockchain-security-auditorSkill
- branching-strategySkill
- bug-explainerSkill
- changelog-writerSkill
- change-notesSkill
- ci-cd-pipeline-builderSkill
- ci-pipelinesSkill
- cloud-costSkill
- cloud-security-architectSkill
- cloud-securitySkill
- codebase-mapSkill
- codebase-onboarding-engineerSkill
- code-comment-writerSkill
- code-reviewerSkill
- code-reviewSkill
- code-translatorSkill
- commerce-platformSkill
- compliance-auditorSkill
- composioSkill
- cron-job-plannerSkill
- database-optimizerSkill
- database-schema-designerSkill
- databaseSkill
- data-engineerSkill
- data-pipeline-architectSkill
- data-pipelinesSkill
- debuggingSkill
- debugging-strategistSkill
- dependency-auditSkill
- dependency-upgrade-auditorSkill
- deployment-checklistSkill
- deploymentSkill
- developer-platformSkill
- devops-automatorSkill
- ecommerce-cms-architectSkill
- email-intelligence-engineerSkill
- embedded-firmware-engineerSkill
- environment-setup-guideSkill
- error-boundary-designerSkill
- error-handlingSkill
- evidence-collectorSkill
- filament-optimizerSkill
- finops-engineerSkill
- firmwareSkill
- frontend-buildSkill
- frontend-developerSkill
- The first 60 shown.
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
- Distinctive: line 38
NEVER deploy prompt changes without running the eval suite first.
- Distinctive: line 39
NEVER use a single metric (e.g., only accuracy) to evaluate multi-dimensional LLM output.
- Distinctive: line 40
NEVER treat eval datasets as static.
“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.
Files
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
- Curate golden test datasets with human-annotated ground truth across representative task categories.
- Define scoring dimensions: Accuracy, Relevance, Completeness, Tone Adherence, Safety, Latency.
- Build adversarial test cases targeting known failure modes (hallucination, refusal, format violation).
Phase 2: Scoring & Comparison Infrastructure
- Implement automated scorers: exact match, semantic similarity (embedding cosine), LLM-as-judge, regex validators.
- Build A/B comparison pipelines for prompt version testing (old prompt vs new prompt).
- Set up drift detection: track score distributions over time windows and alert on statistical deviation.
Phase 3: CI Integration & Reporting
- Integrate eval suite into CI/CD pipeline as a required gate before prompt/model deployment.
- Generate eval reports with pass/fail rates, score distributions, and regression flags.
- 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.
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
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.

