Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/plugin-review
Review plugin quality with tiered checks and dependency scoping.
Passed 17 of 20 test cases with the skill, and 4 of 20 without it.
and 13 more in the full report
14 fixed5 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
Where should plugin maintainers place custom quality gate threshold overrides, such as skills_min or bloat_max_percentage, and what is the exact filename?
| Checked | Without skill | With skill |
|---|---|---|
| The configuration file is named .plugin-review.yaml in the plugin root. | Missed | Passed |
The instructions your model reads when the skill loads.
Tiered quality review of plugins with dependency-aware scoping.
abstract:skills-eval)abstract:hooks-eval)Skill() references across plugins (use
abstract:skill-graph-audit)| Tier | Trigger | Scope | Depth | Duration |
|---|---|---|---|---|
| branch | Default | Affected and related | Quick gates | ~2 min |
| pr | Before merge | Affected and related | Standard | ~5 min |
| release | Before version bump | All 17 plugins | Full | ~15 min |
--tier flag, find affected
plugins from git diff, resolve related plugins from
docs/plugin-dependencies.jsonAffected plugins: git diff main --name-only filtered to
plugins/*/.
Related plugins: load docs/plugin-dependencies.json,
look up each affected plugin's reverse index to find
dependents. Mark as "related" (lighter checks).
If --tier release or no git diff available, scope to
test cases passed, vs 4 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.