Agent skill · Security

benchmark-fp-fn-audit

Audit React Doctor against ReactBench or similar diagnostic benchmark corpora for confirmed false positives, false negatives, taxonomy gaps, and verifier artifacts. Use when analyzing rd.log, rd-before.json, rd-after.json, model.patch, result.json, reward/test logs, rule distributions, or when asked to perform a second adversarial pass over React Doctor benchmark findings.

Million Software, Inc.14,162★ · +123/wk · 1 repos on radarProfile →
claude-codeNOASSERTION
Install
npx skills add millionco/react-doctor --skill benchmark-fp-fn-audit --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 8 KB
Bundled scripts: none
Path: .agents/skills/benchmark-fp-fn-audit/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 14,264 · +102 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# React Doctor benchmark FP/FN audit Perform an evidence-backed audit of React Doctor diagnostics across a benchmark corpus. Read the complete rule documentation, quantify the distribution of failures, inspect every relevant trial artifact, and independently perform a second pass for additional false positives and false negatives. ## Corpus and required resources For this benchmark, use: ```text /home/aidenybai/Developer/react-bench-internal/jobs/ReactBench-v1.1-beta-rd-0.9.3-consolidated-final-20260801 ``` Read the complete React Doctor rule documentation from: ```text https://www.react.doctor/docs/rules ``` Read these repository review materials when they exist: ```text /home/aidenybai/Developer/react-bench-internal/docs/aiden-review ``` Do not treat prior reviews or reports as ground truth. Use them as leads and reverify every claim against the current benchmark revision. For every inspected trial, locate and read: - `verifier/model.patch` - `verifier/rd-before.json` - `verifier/rd-after.json` - `verifier/rd.log` - `result.json` - reward and test logs, discovered with `rg --files` - the task README, prompt, or review material - the base and patched source files referenced by the

What's inside
Steps it walks through
  1. Corpus and required resources
  2. Evidence rules
  3. Workflow
  4. 1. Inventory the corpus
  5. 2. Build diagnostic distributions
  6. 3. Inspect high-impact clusters
  7. 4. Perform the independent second pass
  8. 5. Produce audit artifacts
Ships with 2 files
  • agents/openai.yaml
  • references/benchmark-artifacts.md
More from react-doctor
All skills →
About this skill
What does the benchmark-fp-fn-audit skill do?

Audit React Doctor against ReactBench or similar diagnostic benchmark corpora for confirmed false positives, false negatives, taxonomy gaps, and verifier artifacts. Use when analyzing rd.log, rd-before.json, rd-after.json, model.patch, result.json, reward/test logs, rule distributions, or when asked to perform a second adversarial pass over React Doctor benchmark findings.

How do I install it?

Run `npx skills add millionco/react-doctor --skill benchmark-fp-fn-audit --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From millionco/react-doctor, a repository with 14,264 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going