How it works

Three things, and deliberately nothing else. No community, no ratings, no authoring — those are how skill libraries turn into landfill.

The scan

A skill is a document that tells a model what to do with your CRM. Installing one is a trust decision, and most libraries ask you to make it blind.

Every skill here is read and scanned, and the result is on its page in four lines: what it needs, what it reads, what it can change, and what leaves your portal. The interesting one is the third. A skill that cannot write anything is a very different risk from one that updates deal stages, and the difference should not be buried in paragraph six.

Read-only — reads and reports. It cannot change anything.
Drafts only — produces text for you to use. It never sends on your behalf.
Proposes writes — prepares a change and shows it to you. Nothing lands until you apply it.
Not declared — the skill doesn't say. We show that rather than assuming the safe answer.

The posture comes from the skill's own compatibility line, and a check in our build fails if the two ever disagree. If a skill is edited to write to the CRM without updating that line, the library stops building.

The harness

A skill is a prompt someone wrote down. That is worth something, but not automatically — modern models already do a lot of this unaided, and a skill that adds nothing is worse than none, because it costs tokens and hides what the model would have done anyway.

1Give it a real task — a company you actually need a brief on, not a demo.
2It runs twice: once with the skill loaded, once with the same model and the same task without it.
3You read both, side by side, and decide.

Sometimes the honest answer is that you didn't need the skill. We would rather you find that out here than three weeks into using it.

Getting the skill

The default is a reference, not a copy. Point an MCP client at the library and the skills are available as tools, still hosted here — so when one is corrected, you get the correction.

If your client doesn't speak MCP, every skill is a markdown file at its own .md URL. Copy it. That works everywhere and always will, with the tradeoff that you now own a snapshot and keeping it current is on you.

Where the skills come from

This first set is the Builder.org GTM library — written for HubSpot workflows and used internally before it was published. Curated, not crowdsourced: a small number that are known to work beats a large number nobody has read.

There is no submission form yet, and that is on purpose. Opening authoring before the scan and the harness are trustworthy would just produce volume nobody can evaluate.