verify-behavior
Skill0 starsChanged 3 months agoMITView on GitHub
Runs headless Claude Code behavior evals against plugin skills and hooks. Use when asked to "verify behavior", "run behavior evals", "挙動検証して", or after behavior-affecting changes to plugin skills or hooks.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Codagent-AI/agent-skillstheir own version, first seen Nov 1, 2026
- mthines/agent-skillstheir own version, first seen Oct 30, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Codagent-AI/agent-skills★ 31same name
- mthines/agent-skills★ 20same 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.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Run the behavior evals in evals/ to check that plugin skills and hooks produce the intended behavior in headless Claude Code sessions, and …
- Very specific: line 13
Run evals/run.sh — all scenarios by default, or only the scenario names passed as $ARGUMENTS.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Verify Behavior
Run the behavior evals in evals/ to check that plugin skills and hooks produce the intended behavior in headless Claude Code sessions, and report the results.
Steps
- Run
evals/run.sh— all scenarios by default, or only the scenario names passed as$ARGUMENTS. Read the output and report each scenario's PASS/FAIL and trial breakdown. - For any scenario that FAILs, re-run it with
KEEP_WORK=1so the workdir and output file are preserved, then read them to determine whether the failure is a plugin regression or a stale/flaky scenario. - If the change being verified introduces new behavior not covered by an existing scenario, design and trial a new scenario for it, and add the ones that work reliably to
evals/scenarios/(ascenario.conf+check.shpair). Prefer mechanical checks (git status, grep on output, functional tests on files) over judgment calls; use TRIALS/PASS_MIN to absorb the model's inherent variance.
Cost note
A full run spawns roughly 10 headless claude -p sessions and costs API tokens. Only run this after changes that affect plugin behavior — for structural-only changes, use the verify skill instead.
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.