Usually not, for common jobs. The Use This Skill directory lists 1,966 free skills (crawl of November 9, 2026), and free skills such as tdd and frontend-design changed Claude's output in side-by-side proofs. A paid skill is worth it when it has a proof on a brief like yours, its terms let you use it as you need, and no free skill with a proof does the same job.
A note before the numbers: this site sells skills. Five are in the store, at a one-time price of $15 to $29, and two of them, launch-page and nextjs-test-writer, have proofs. Both are on this page because they are the paid skills this site can show evidence for, and they are measured the same way as the free ones.
What do free and paid skills on this site show?
The table puts the free directory next to the paid store, from the weekly crawl and scan of November 9, 2026, and the proofs on proven skills. In a proof, Claude Opus 5.5 runs one fixed brief three times without a skill and three times with it, and all six pages are published.
| Free skills in the directory | Paid skills in this site's store | |
|---|---|---|
| Skills | 1,966 from 47 GitHub repositories | 5 |
| Price | $0 | $15 to $29, one time |
| Skills with a proof | 40 (37 still in the directory) | 2 |
| Safety scan (Nov 9) | 1,905 clear, 47 review, 14 flagged | Not in the weekly scan of GitHub skills; sold here, not on GitHub |
| License recorded | MIT 613, Apache-2.0 345, BSD 1, other 100, none 907 | Use and change in your own projects; no resale or publishing |
| Read every file before installing | Yes, on GitHub | Proof pages open before buying; files after payment |
Counts by script from data/skills.json, data/scan.json and data/proofs.json on November 10, 2026. Store terms from the store pages and the site's terms. No proof was commissioned by a skill author.
The proofs are the part to read. Price does not predict whether a skill changes anything. Several free skills changed the output in every run, and several changed little, because Claude already does the job well without them.
What did the paid skills change that free ones did not?
Each paid skill sits next to a free skill proven on a similar job. The briefs differ, so read each row against its own runs without the skill, not against the other row.
| Skill | Price | Brief | What changed with the skill (3 runs each side) |
|---|---|---|---|
| launch-page | $29 | Launch page for a bookkeeping app; no customer quotes supplied | Invented customer quotes: 0 of 3 runs (3 quotes in each of 3 runs without); median file size 47 KB to 32 KB; median ARIA attributes 19 to 28; skip link 1 of 3 (0 of 3 without) |
| frontend-design | Free | Landing page for a calendar app | Skip link 2 of 3 (0 of 3 without); median ARIA attributes 18 to 36; median file size 56 KB to 37 KB |
| nextjs-test-writer | $15 | Test plan and tests for a coupon feature in a Next.js app | Plan ordered by risk 3 of 3 (0 of 3 without); a table of code breaks each test must catch 3 of 3 (0 of 3 without) |
| tdd | Free | Cron parser in TypeScript, test-first | Tests on the public interface only 3 of 3 (1 of 3 without); median output tokens 27,884 to 16,704; median time 230 s to 138 s |
launch-page counted by script in its six published pages on November 10, 2026. frontend-design from best frontend design skills; nextjs-test-writer and tdd from best skills for writing tests. Both store proofs ran on October 22, 2026, before tokens and time were recorded.
The clearest paid-only change is a rule the free design skill does not state. The launch-page brief gave a real fact, about 400 private-beta users, and no customer quotes. Without the skill, every run added three quotes from customers who do not exist. With it, no run did, because its SKILL.md says "no fake testimonials, no fake logos." If you ship landing pages for real products, that rule matters more than any layout choice.
The free skills hold their own. tdd moved tests onto the public interface and cut output and time by about 40 percent, for nothing. frontend-design doubled the ARIA attributes. If one of these covers your job, a paid skill has to show something beyond it to be worth the price.
When is a free skill enough?
A free skill is enough when its proof shows the change you want, or when the job is one Claude already does well. Skills that mostly set a look, such as theme-factory and web-artifacts-builder, changed little in their proofs, and so would a paid skill of the same kind. Before paying for a design or writing skill, look for a free one in the same category on proven skills and read its six pages.
Free is also the easier choice to check. Claude Code's documentation describes a skill as a SKILL.md file with instructions, plus any reference files and scripts in its folder. On GitHub you can read every one of them before you install. Anthropic's Agent Skills overview advises using skills "only from trusted sources: those you created yourself or obtained from Anthropic," and auditing anything else thoroughly (both checked November 10, 2026). That advice applies to a paid skill as much as a free one.
What should I check before paying for a skill?
| Check | Why it matters | Where to look |
|---|---|---|
| A proof on a brief like yours, every run shown | One good sample can be picked by hand; three runs a side show what is typical | The seller's page; on this site, the skill's page |
| A free skill already doing the same job | If one is proven, the paid skill must beat it | Proven skills, by category |
| What the files can do | Scripts and pre-approved tools can run commands on your machine | Paste a GitHub link into the live skill check; for files you receive, read them before installing |
| License | Whether your team, clients or a product can use it | The seller's terms; this store allows use and changes in your own projects, not resale |
| Refund | A skill is text you keep once downloaded | The seller's terms; this store refunds within 14 days if a skill does not work as described |
| Updates | Agents and models change; a skill written for last year's Claude may age | Whether the price includes updates; this store's order link serves the latest version |
Is a free skill free to reuse?
Not always. 907 of the 1,966 skills in the November 9 crawl have no license recorded for their repository. choosealicense.com says that without a license, a work "is under exclusive copyright by default," and that finding software without one "generally means you have no permission from the creators of the software to use, modify, or share the software" (checked November 10, 2026). If you plan to change a skill and share it with a team or put it in a product, a free skill with an MIT or Apache-2.0 license, or a paid skill whose terms cover that use, is the safer choice. This is not legal advice.
How were these numbers counted?
The directory counts, scan results and licenses come from the weekly crawl of November 9, 2026, which reads every skill folder in 47 public repositories and scans each file for patterns such as downloading and running code in one step, sending data out, or text that tries to override your instructions. A clear result is a static check, not a guarantee; are agent skills safe? explains its limits.
The launch-page figures come from a script run on November 10, 2026 over the six published pages: file size, aria- attributes, a "skip to content" link, and quoted customer statements in the visible text. The other rows come from the counts in the linked guides. The rules for every proof are on how a proof works.