Question 1

Is SkillzBench live yet, or still in development?

Accepted Answer

SkillzBench is pre-launch and actively being built. The waitlist and newsletter are live, but the product itself is not yet public. We never claim live user or skill counts — join the waitlist to be notified when discovery, verification, and benchmarking go live.

Question 2

What does 'Lift in percentage points' actually mean when benchmarking agent skills?

Accepted Answer

SkillzBench tests every skill in a sandbox with the same model, with and without the skill, and publishes the difference as Lift in percentage points. This measures whether a skill actually improves agent performance, and Lift is always shown separately from trust ratings so measurement never gets conflated with quality scores.

Question 3

Does SkillzBench support script-bearing skills or only instruction-only SKILL.md packages?

Accepted Answer

Launch scope covers instruction-only skills — SKILL.md files plus text references. Script-bearing skills will be listed link-out only, so you can still discover them but SkillzBench won't benchmark or enable them directly at launch.

Question 4

How will pricing work for a small business that wants to equip multiple agents?

Accepted Answer

The pricing hypothesis is a generous free tier, Pro at roughly $9-15/month for more agents and unlimited enabled skills, and Teams at roughly $15-25 per seat per month for org loadouts, allowlists, and audit. A Creator tier around $5-10/month is planned for verified authors, plus benchmark-as-a-service for priority runs.

Question 5

How is SkillzBench different from just browsing GitHub or the official MCP registry for skills?

Accepted Answer

Registries and GitHub list skills; they don't test them. SkillzBench is building continuous crawling and deduplication, commit-SHA-pinned verification, security and license scanning, sandbox benchmarking with published Lift, per-agent loadouts through one MCP server, and upstream change tracking with notifications — an end-to-end control panel rather than a directory.

MCP Server Discovery for Small Businesses