Skill Marketplace

What these templates are

Each card above is a role template: a written job description, a repeatable workflow, and output checks you save as a SKILL.md file. The skill itself is just text — the value is that the same review steps run the same way every time, instead of living in your head or in an old chat log.

How to pick your first template

• Match the role to work you repeat weekly. Code review on every pull request or documentation upkeep are ideal; one-off tasks do not need a skill.
• Start with the checker roles. Reviewer and auditor templates are low-risk: they read your work and report findings, they do not change files.
• Read the output checks before running. If you cannot say what a good result looks like, tighten the template first.

Using a template well

1. Copy the SKILL.md from the template page and skim every line before first use.
2. Adapt the workflow to your stack — the defaults are starting points, not requirements.
3. Run it on copied files or a low-stakes task first, then compare the output against the checks.
4. Keep notes on where it misled you, and edit the template the same day.

Skill, workflow, or connector?

Skills shape how Claude works (role, steps, output standards). Workflows are end-to-end recipes for a whole task. Connectors control what sources Claude can read. Many real setups use all three — see the connectors hub and the workflow library for the other two layers.

Do these templates guarantee correct output?

No. A skill makes Claude consistent, not infallible. Checker-style skills reduce missed steps, but you still own the final decision — especially for security findings and text you plan to publish.

Can I modify and share a template?

Yes. The templates on this site are meant to be adapted. If a variation works well for you, send it to the email below and it may become a card here.