Inside the data.
We indexed every AI-agent artifact we could find, comprehended each one, and measured which actually work. Here's what 7,950 skills, tools, and workflows reveal — including the uncomfortable parts.
The index
What's in it
Six kinds of artifact, twelve business functions. Engineering dominates the open-source supply — the business functions you'd actually hire for are the underserved minority.
By kind
By business function
Fresh and sourced widely
A current index — most of the corpus was updated this spring — drawn from hundreds of repos, not a handful.
Last updated, by month
Top contributing repos
Stars don't predict quality
The uncomfortable truth at the heart of this project. We measured each skill's causal lift — does it improve the output versus no skill at all — and plotted it against GitHub stars. There is no relationship. Popular skills routinely sit below zero.
Each dot is a measured artifact · green helps, red harms · x = stars (log) up to 183k
One in three measured skills make output worse
Of 199 artifacts we measured, 69 produced measurably worse results than using no skill at all. Stars don't warn you — measurement does.
Distribution of measured lift
Most popular skills that harm output
Where skills actually matter
A skill's value depends on how good the base model already is. Where the model is weak, the right skill lifts results a lot. Where it's already strong, skills add nothing — or hurt. The zone where skills matter shrinks as models improve.
Capabilities where the model already wins — skip the skill
The map of the AI-skill universe
Every comprehended artifact, projected by what it actually does. Neighbors do similar work. Colors are business functions; the glowing rings are the ones we measured — green where they help, red where they harm. Drag to explore.
What this work costs today
The freelancer and agency prices for the jobs these recipes do — the budget a measured AI recipe competes with.
what people pay freelancers/agencies/tools for these jobs today · median dot
How much runs on its own
Recipes chain library skills, but some steps need outside tools — your CRM, a sender, a calendar. Here's which tools recur, and how self-contained each business area is.
Most-used connectors
Autonomy by area
■ runs from the library■ needs an external tool
The capabilities that power everything
A few stable capabilities show up across many recipes — the reusable backbone of the library. Build these well and the whole catalog gets better.
The point of all this measurement
So when you pick a recipe, the steps are filled by what actually works — not what's popular. Pick a job and run it.
What do you need to run? →