Overview

How Skills Are Scored

Every indexed skill is placed into one of four quality tiers, and separately tagged with a risk level and a maintenance status. Together, these three signals are what you see next to each entry in the directory.

Quality tiers#

Badge Tier Score Description
⭐ Curated β‰₯120 High-viability with gotchas, examples, verification
πŸ”· Promising 80–119 Good structure, some quality signals
πŸ”Ά Experimental 40–79 Basic skill, limited signals
β€” Review Required <40 Needs review

Of the 1,204 skills currently indexed, 229 sit in the Curated tier β€” roughly one in five. That ratio is deliberate: the score gates on structure (documented gotchas, working examples, a verification step) before it counts adoption at all, so a skill can't buy its way into Curated on stars alone.

Risk levels#

Risk is scored independently of quality β€” a well-structured skill can still request broad permissions.

Icon Level Description
🟒 Low Standard permissions, safe to use
🟑 Medium Extended permissions (shell access, subagents)
πŸ”΄ High Broad system access, review before use
⚫ Critical Manual review required

Check the risk icon before installing a skill that will run inside your coding agent β€” a Curated quality score says nothing about how much system access the skill asks for.

Maintenance status#

Icon Status Description
🟒 Active Updated within last 90 days
βœ… Stable Feature-complete with releases
🟠 Stale 90–365 days without updates and no releases
πŸ”΄ Unmaintained Not updated for over 365 days
βšͺ Unknown No commit date available

Maintenance status is recalculated daily, so a skill's badge moves as its upstream repository changes β€” a skill doesn't stay Active by default, it has to keep shipping.

Next steps#

Updated

Was this page helpful?