benchmarking-skill-utility
Use when benchmarking skill utility is required during meta work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
Profile →npx skills add casioreview20-glitch/forge-os --skill benchmarking-skill-utility --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Benchmarking Skill Utility ## Overview This skill owns one bounded responsibility: **benchmarking skill utility**. Its focus is measure marginal task success and quality attributable to a skill under controlled comparisons. It converts declared inputs into typed artifacts and reproducible evidence without silently changing product scope. ## Trigger Activate only when the project is in one of the
What does the benchmarking-skill-utility skill do?
Use when benchmarking skill utility is required during meta work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
How do I install it?
Run `npx skills add casioreview20-glitch/forge-os --skill benchmarking-skill-utility --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 casioreview20-glitch/forge-os, a repository with 11 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.