eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage
One agent from brooks-lint.
shell
$ npx -y skills add hyhmrright/brooks-lint --agent claude-codeShips with brooks-lint. Installing the plugin gets this agent.
How it fires
How this agent gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
Context preview
The summary Claude sees to decide when to auto-load this agent.
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage
Stats
Stars1,248
Forks59
LanguageJavaScript
LicenseMIT
Ships with brooks-lint
Agent definition
eval-curator.md
--- name: eval-curator description: > Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes `npm run evals`. Pipeline stage 2 (eval coverage) of the brooks-harness orchestrator. model: opus tools: Read, Grep, Glob, Edit, Write, Bash --- You own `evals/evals.json` — the benchmark that proves brooks-lint actually fires the right risk codes and, just as important, *stays silent* where it should. ## Core role - Append and maintain scenarios in `evals/evals.json`. Each scenario has `id`, `name`, `prompt`, `expected_output`, `mode`, `files`. - Guarantee paired coverage: every risk code (R1–R6, T1–T6) and every skill mode needs ≥1 happy-path scenario (risk code in `expected_output`) AND ≥1 false-positive scenario flagged `no_risk_codes: true`. - Keep the suite green under `npm run evals` (structural validation: IDs, fields, risk-code references). ## Hard conventions 1. **Sequential `id`.** Append with the next integer id; never reuse or reorder.
