skill-benchmark
Skill37 starsChanged 5 months agoMITView on GitHub
Scores any SKILL.md across 5 quality dimensions, runs a compatibility check against 50+ AI agents, and returns a ranked fix list. Trigger when the user asks to benchmark, score, or audit a skill, wants to check cross-agent compatibility (Cursor, Windsurf, Gemini, etc.), needs a ranked fix list before publishing a SKILL.md to the community repo, is comparing two skills before a pull request, or wants to audit a SKILL.md for compatibility before opening a PR.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- AllanSantos-DV/skill-kittheir own version, first seen Oct 15, 2026
- iamzhangg/skill-benchmarktheir own version, first seen Sep 24, 2026
- TheophilusChinomona/idevtheir own version, first seen Jun 12, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- AllanSantos-DV/skill-kit★ 0same name
- iamzhangg/skill-benchmark★ 0same name
- TheophilusChinomona/idev★ 0same 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 repository38 other files it gives its agents.
- ad-breachSkill
- ai-llm-hunterSkill
- attack-surfaceSkill
- bugbounty-reporterSkill
- cavemanSkill
- check-exploitSkill
- clickjacking-hunterSkill
- compliance-gap-analyzerSkill
- control-lookupSkill
- ctf-writeupSkill
- cvss-scorerSkill
- deadangleSkill
- droid-reconSkill
- economist-attackSkill
- engagement-handoffSkill
- finding-writerSkill
- find-skillsSkill
- graphql-raiderSkill
- hexstrike-forgeSkill
- high-severity-hunterSkill
- hpp-hunterSkill
- idor-hunterSkill
- js-analyzerSkill
- jwt-crackerSkill
- less-aggressive-attackSkill
- less-noise-attackSkill
- nuclei-template-writerSkill
- pentest-reportSkill
- redirect-forgeSkill
- redmindSkill
- remediation-plannerSkill
- risk-assessorSkill
- scope-grillSkill
- ssrf-hunterSkill
- ssti-hunterSkill
- vuln-diagnoseSkill
- xss-hunterSkill
- xxe-phantomSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
If the user provided a path, read that file directly.
- Distinctive: line 20
If not, search in this priority order:
- Distinctive: line 24
If multiple are found, list them and ask the user to confirm which one.
- Very specific: line 25
If no SKILL.md is found after exhausting all search paths, stop and output: [skill-benchmark error] No SKILL.md found — provide a file path …
- Distinctive: line 27
Read the full file into context before proceeding.
- Very specific: line 63
Read references/agent-profiles.md.
- Very specific: line 79
Use the template in references/report-template.md.
- Distinctive: line 91
After presenting the report, offer exactly these three options:
“Common” is measured: kept by at least 6 in 10 of the 3 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
Skill Benchmark
Reads a target SKILL.md, scores it across 5 weighted dimensions (100 pts
total), runs a static compatibility analysis against 50+ agent profiles, and
returns a structured report with a ranked fix list.
No agents need to be installed. Everything is static analysis — you read the skill file, apply the rubric below, and produce the report.
Protocol
Step 0 — Locate the target skill
- If the user provided a path, read that file directly.
- If not, search in this priority order:
- Current directory:
SKILL.md,*/SKILL.md - Project skill paths:
.claude/skills/,.agents/skills/,.cline/skills/ - Global paths:
~/.claude/skills/,~/.config/agents/skills/
- Current directory:
- If multiple are found, list them and ask the user to confirm which one.
- If no SKILL.md is found after exhausting all search paths, stop and output:
[skill-benchmark error] No SKILL.md found — provide a file path to continue. - Read the full file into context before proceeding.
Step 1 — Intake
Extract and note:
- Skill name (frontmatter
name:field) - Description (frontmatter
description:field, full text) - Body length (line count)
- Has bundled resources? (scripts/, references/, assets/ subdirs)
- Explicit agent targets (any
--agentflag mentions or agent-specific sections)
Step 2 — Score each dimension
Apply the rubric in references/rubric.md. For each dimension, note the
score, a one-sentence rationale, and the single most impactful fix.
| # | Dimension | Max pts |
| 1 | Trigger quality | 25 |
| 2 | Instruction clarity | 25 |
| 3 | Agent-agnostic design | 20 |
| 4 | Self-containment | 15 |
| 5 | Output definition | 15 |
| Total | 100 |
Scoring is strict. A score of 70+ means the skill is publishable. Below 50 means it will silently fail on most agents.
Step 3 — Run compatibility matrix
Read references/agent-profiles.md. For each of the 7 agent profiles,
check the target skill for the compatibility signals listed. Assign one of:
- ✅ Compatible — no blocking signals found
- ⚠️ Partial — one or more soft-fail signals (skill may work but will degrade or skip steps)
- ❌ Likely broken — one or more hard-fail signals
Then map each named agent to its profile result. When an agent appears in multiple profiles (e.g., Claude Code in A and C), assign the worst result across all applicable profiles: ❌ overrides ⚠️ overrides ✅.
Step 4 — Generate the report
Use the template in references/report-template.md.
Fill in every section. Do not skip the "Top fixes" section — it is the most actionable part and the reason the skill exists.
Sort the 54 agents into three groups (Compatible / Partial / Broken) and list them comma-separated. Do not list each agent on its own line.
Step 5 — Offer next steps
After presenting the report, offer exactly these three options:
- Auto-fix — apply the top-ranked fix and re-score immediately
- Deep dive — expand any dimension score with full evidence from the skill text
- Export — save the report as
skill-benchmark-report.mdin the same directory as the evaluated skill
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.

