New: SEO Blog Writer, a readable, checked blog post for your site every week. Pay once, download straight away.
See itA skill written in an afternoon fires when it feels like it and breaks on a machine that isn't its author's. Ours fire on the words you type, are tested on a clean machine, ship with three worked examples, and get fixed when Claude changes.
Every number here comes straight from the catalogue, and every listing shows real output before you pay.
Runs in the agent you already use
Every skill is a plain SKILL.md folder in the open Agent Skills format, which these agents read. We test in Claude Code, and a few skills use Claude Code features; each listing says what it needs.
And the tools you build with
Names belong to their owners. Listed because our skills work with them, not because any of them endorse us.
Not code. Anyone can write a SKILL.md. You're paying for the day someone else spent making it reliable.
Skill imported
on your task…
Drag the folder into your skills directory and you're done. No package manager, no config file, no account, nothing to sign in to. Ask for the thing in plain words and it fires.
description:
helps with code
never fired
The description was written for a human, so Claude never matches it. The script assumes a tool you don't have. Nine hundred lines of SKILL.md eat the context window, and you stop reaching for it.
should fire
should not fire
dated on the listing
published
Trigger accuracy against a written test suite, published on each listing with its date once it has run. Until it has, the listing says so and shows no number.
Updates
Re-tests
Replies
Twelve months of updates as Claude Code moves underneath it, re-tested on a clean machine each time, and a person who answers.
$docker run --rm skilltest
fresh image, no local state
installs and loads
Every skill installs into a fresh container with no local state before it ships. The machine a skill was written on is the one place it is guaranteed to work, and it is the one machine you do not have.
Markdown and scripts in a folder. No proprietary format, no runtime, and nothing to uninstall.
Each one shows its real output, what it needs, and exactly what you get when you buy it.
Context, the 5-hour limit and the weekly limit as capsules, with the exact reset time inside each.
Eval suite not run yet
Original app icons from a one-line brief, in seven styles, exported for every platform.
Eval suite not run yet
Google Analytics 4 and Search Console for your site, set up by Claude in your own Chrome, with the tag in your code.
Eval suite not run yet
Search by the problem rather than the tool's name. Every listing shows real output and what it needs, before you spend anything.
Describe what keeps going wrong. You do not have to know what the skill is called, or that one exists. Filter by category or by price.
Rewrote the trigger description
Checked the tools it assumes
Cut SKILL.md to what Claude reads
Added three worked examples
Every product page lists what the skill does, what it needs and three worked examples, and credits anyone whose work it builds on.
Your rules, not generic ones
Its own eval suite
A private channel to ask in
Nothing in the catalogue fits the way you work? Tell us the task and we will harden one against your own rules, with its own eval suite.
A skill is instructions Claude reads before it starts. A hardened one fires on the prompt you would actually type, and answers with your own rules rather than with general advice.
We pick a job people redo every week and work out what a reliable skill for it has to do. Nothing ships that we cannot test.
Ten fixed points: clean-machine test, rewritten trigger description, token diet, honest error handling, real docs, an eval suite.
A ZIP and a licence key by email. Unzip, drop it in, done. Updates for a year and a person to ask when it breaks.
Pick the job, download one folder, pay once. Every skill goes through the same checks before it is listed: the trigger, the licence, a clean machine and three worked examples.
Each skill is priced on its own page, for what that one skill saves you. One-off, with no subscription, no seats to count and nothing that renews while you are not looking.
A ZIP and a licence key within a minute of paying. Inside: the skill, our README with three worked examples, and a troubleshooting table written from the ways it actually broke.
Re-tested on a clean machine whenever Claude Code moves underneath it, and reissued to you. No renewal, no second charge.
If we cannot deliver the skill you paid for, you are refunded in full. Every listing publishes its measured trigger accuracy and its worked examples first, so nothing about it is a surprise after the fact.
The six we are asked most. Everything else is in the install guide, or by email.
You can, and for a one-off task you probably should. The cost is not the first draft: it is the trigger description that fires on the words you actually use, the tools it assumes are installed, the context it eats every turn, and the docs. We do that once, and publish the measured number on the listing once the eval has run.
A ZIP of the skill and a licence key, by email, within a minute of paying. Inside: the skill, our README with three worked examples, and a troubleshooting table written from the ways it actually broke on a clean machine.
Nothing technical, and we will not pretend otherwise. Claude reads a skill as plain text, so anything on your disk is copyable. What you are buying is that it keeps working: updates when Claude Code changes, and someone to ask when it does not.
A written set of prompts that should fire the skill and prompts that should not, run against the skill. The number goes on the listing with the date it was measured. If we did not measure it, we do not publish a number, and the listing says so.
Yes. Within 14 days of buying, for any reason, in full: email support and we refund it. Everything you need to decide is on the listing before you buy: real output from the skill, the three worked examples, and what it needs installed.
We do. Where a skill builds on someone else's published work we say so on its page and ship their licence with it, but the catalogue is our own code, written to one standard and tested the same way.
