A teammate drops a link:
“install this, it’s amazing.”

A skill is a set of instructions your agent follows.

It gives the agent a consistent way of working: review code the way your team does, write commit messages in your format, or draft your release notes. Define it once, and the agent does it that way every time.

Anthropic describes skills as a practical way to equip agents for real work. As they spread, one question matters more: what exactly are you installing?

Skills are shared everywhere, but trusted nowhere.

A link in chat. A folder in a repository. A wiki page that may already be stale. Teams can store skills today, but there is no consistent way to inspect their behavior, understand required access, compare versions, or learn how they perform for other users.

A shared folder or repo is fine for storing skills—not for trusting them. It keeps history and versions, but it can’t tell you whether a skill is safe, what it’s allowed to touch, which version you’re really on, or how it worked out for anyone else.

A trusted home for the skills your agents run.

Browse a public catalog, see exactly what a skill does before you run it, install an exact version in one line, and publish your own — to everyone, or privately to your team.

A folder can store a skill. SkillPatch can vouch for it — every skill is checked for safety before you ever run it. And that’s only the start: save what works into new skills you can reuse, and improve the ones you depend on when they fall short.

Every public release is reviewed before installation.

Each submitted release runs through automated checks across six areas—prompt injection, data exfiltration, code execution, secret access, supply-chain integrity, and network behavior. Releases that do not meet the required threshold are blocked from public installation until the issues are resolved.

See exactly what it does. Then install it.

Once the review, the access it needs, the maker, and the version all look right, install that exact version straight into your agent—no copy-pasting a random folder, no hoping “latest” is the one you actually checked.

Keep what worked. Use it again tomorrow.

You and your agent figure out a really good way to handle something tricky — an approach worth reusing. But there’s nowhere to keep it. When the session ends, that know-how is gone, and next time you’re solving it all over again.

/skillpatch save reads back through the session, spots the method you landed on, and drafts a skill from it — stripping out anything that should stay private, like repository names, file paths, and ticket numbers.

Review the draft and decide where it belongs: keep it private, share it with your team, or submit it publicly. Public releases go through the same required review process before installation is enabled.

A one-off fix on a Tuesday becomes something your whole team runs in one command.

Improve a skill the moment it lets you down.

Even the skills you rely on will hit their limits — and normally, that gap just stays there. SkillPatch lets you turn a real miss into a fix its maker can review and ship to everyone.

When your agent hits something a skill doesn’t handle, /skillpatch suggest drafts a fix from what just happened — and you see exactly what gets shared before anything is sent.

Every suggestion is reviewed before the maker approves a new version — so the skills you rely on keep getting better, and nothing an AI drafts is ever trusted blindly.

A place to store skills is common. A place that maintains them is not.

Your team, one standard.

Every team has its own way of working — how you review code, how you ship, the standards you don’t bend on. Usually that knowledge sits with a few senior people and takes newcomers months to pick up. SkillPatch lets you package it into private team skills, so every teammate’s agent can work that way — a new hire installs them and works like a veteran on day one.

Same one-line install, same safety checks — just kept inside your team.

Ask the people who actually run it.

Every skill carries its community with it — questions, bug reports, and answers from the people who actually run it. Ask how a skill works, or how to make it fit what you’re doing — and the people already using it answer.

Anyone who’s run it can weigh in — maintainers included.

The best skills shouldn’t be buried under a search box. Your feed brings them to you — what’s trending, what the makers you follow just shipped, and what fits the kind of work you do.