There are now enough open skills libraries that “which one should I install” is a real question, and the honest answer is that most of them are not competing. They occupy different axes: one changes how your agent writes software, another gives it channel-level marketing playbooks, another ships the file-format handlers, another supplies named frameworks from books. Install the wrong one for your job and you conclude that skills do not work; install two covering different axes and the idea clicks.
We maintain one of the libraries below, which is a reason to be suspicious of this page and also the reason it is worth writing. Where another is the better answer, it says so — a roundup that concludes “install ours” is not a comparison.
One note: all star counts here were checked on 17 August 2026 and are approximate. They move quickly and measure attention rather than fit. If you have not installed a skill yet, how to install Claude Code skills covers the mechanics; this page is about choosing.
Which Claude Code skills library should I install first?
The short version, before the detail:
- Your coding agent should work differently — plan before it codes, test properly, review its own work: Superpowers.
- You are doing marketing execution yourself: Corey Haines’ marketing skills.
- You need Claude to handle documents — Word, Excel, PowerPoint, PDF — or you are authoring skills: Anthropic’s own repo.
- You want named frameworks from books applied to your decisions: a book-derived library, ours among them.
- Your method lives in one specific book nobody has packaged: book-to-skill, and do it yourself.
Superpowers: a development methodology, not a grab bag
obra/superpowers (roughly 273,000 stars, MIT) is the most-used skills project in the ecosystem and the most opinionated. It is not a catalogue of independent skills; it is a software development methodology assembled from about fourteen composable ones plus the instructions that make the agent actually use them. The pieces are the lifecycle: brainstorming a spec out of a vague request, writing plans, executing plans, subagent-driven development, TDD, systematic debugging, code review, git worktrees, verification before completion, finishing a branch.
The bet is different from everything else here. Most libraries wait to be relevant; Superpowers front-loads a behaviour change — the agent stops jumping straight to code, extracts a spec, produces a plan, then works through it with subagents while checking its own output. Long autonomous stretches that stay on plan are the product, not the individual skills.
Install this if your complaint is about how your agent builds software: dives in too fast, skips tests, declares victory early. Do not install it expecting domain knowledge — it has nothing to say about pricing, positioning or conversion, and it asserts a strong process, so an existing workflow you like will meet friction.
Worth flagging whichever library you choose: its writing-skills skill, particularly the notes on testing skills with subagents, is one of the better public resources on authoring, and we link it from our own guide to writing a skill.
Corey Haines’ marketing skills: channel-level execution
coreyhaines31/marketingskills (roughly 44,600 stars, MIT, built by marketer Corey Haines) is about fifty skills covering the surface a founder actually has to operate: SEO audits, programmatic SEO, schema, CRO, signup and onboarding, popups, paywalls, copywriting, cold email, email sequences, social, video, ads, A/B testing, analytics, pricing, launches, PR, referrals, competitor profiling, ASO.
The structural idea is a shared foundation: a product-marketing skill holds your product, audience and positioning, and the others read it first, so the copywriting skill knows who it is writing to. That is why the collection behaves like a system rather than fifty disconnected prompts.
If the sentence you are about to type is “write the launch email sequence,” this is the library that answers it. A framework library will hand you a framework instead — which is not what you asked for.
Install this if you are a founder or technical marketer doing go-to-market work yourself and want operational playbooks per channel. Its skills are execution-shaped: they produce the artefact. That is a real difference from ours — our marketing skills are framework-shaped, applying StoryBrand or the Value Equation to what you already have and arguing with your positioning. For “write me the paywall copy,” theirs is the better fit.
Anthropic’s official skills repo: the reference implementation
anthropics/skills (roughly 170,000 stars) plays three roles at once. It carries the document skills that make Claude useful on real files — docx, xlsx, pptx, pdf — plus a set covering frontend design, brand guidelines, artifact building and webapp testing. It carries skill-creator and mcp-builder, the official on-ramps for authoring a skill or an MCP server. And it carries the Agent Skills specification and a template, which makes it the reference for the format rather than merely a collection in it.
Install this if you need the file-format skills — that alone justifies it for most people — or you are writing skills and want the canonical template. Do not expect a curated methodology; it is a deliberately broad first-party toolkit, not a point of view about how you work. For what is genuinely specified versus one vendor’s convention, see the agent skills standard.
Book-derived skills: the closest peers to what we do
This is the category we are in, so treat it with appropriate suspicion and go read the repos.
virgiliojr94/book-to-skill (roughly 22,500 stars, MIT) is not a library at all — it is a tool that turns a technical book you own, in PDF, EPUB, DOCX, Markdown or other formats, into an agent skill, working with Claude Code, GitHub Copilot CLI and Amp. This is the honest answer to the commonest gap in any curated catalogue: your method comes from one specific book and nobody has packaged it. Waiting for someone to cover your book is a worse plan than spending twenty minutes converting it, and it is also the right tool for internal material no public library will contain. The trade-off: generated output is a starting point, not an edited skill, so expect to trim it and rewrite the description.
DamiMartinez/book-skills (MIT, very small and new — a handful of skills, single-digit stars at the time of writing) is a hand-written one-skill-per-book collection with a design goal we endorse: each skill triggers on the book’s concepts, not its title, so “how do I validate this before building it” pulls in Build-Measure-Learn without you naming The Lean Startup. Its selection leans toward computer-science textbooks nobody else has covered — Russell and Norvig’s Artificial Intelligence: A Modern Approach, Mitchell’s Machine Learning, Kernighan and Ritchie’s The C Programming Language. The size is a reason to read it rather than skip it: eight skills you can audit in an afternoon beats fifty you never will.
wondelai/skills is ours (roughly 1,900 stars, MIT — comfortably the smallest audience on this page). It is 50 book frameworks spanning both halves of the problem: engineering (Clean Code, Refactoring, Clean Architecture, Domain-Driven Design) and business, marketing, product and UX (Influence, $100M Offers, StoryBrand, The Mom Test), plus 12 guided journeys that sequence them end to end. Pick it over the other two for coverage across both domains plus the sequencing; pick one of them when your book is one we do not have. Our method is on the about page, the catalogue on the skills index.
Can I install more than one skills library at the same time?
Yes, and most people should. Skills are folders; two libraries do not conflict at the file level unless two skills share a name, and the real interaction is trigger overlap — two descriptions competing for one request. Since these libraries mostly occupy different axes, that overlap is smaller than you would guess: Superpowers plus a book-framework library is a comfortable pairing.
The failure mode is quantity. Selection degrades as the number of installed descriptions grows, because the agent chooses from a longer list of near-neighbours. Install globally only what you want everywhere, and scope the rest to the projects that need them.
How do I judge a skills library before installing it?
Four checks, and none of them is the star count.
Read three descriptions. The description field is the part that actually runs; it decides whether a skill ever loads. Descriptions that name situations and quote the phrases a user would type signal a maintained library. Descriptions that summarise a topic signal that nothing will ever fire.
Read one SKILL.md end to end. Pick the skill whose subject you know best and ask whether it would change what your agent does. Instructions, thresholds and mistake tables change behaviour; a well-written summary of something the model already knows does not.
Check the licence and the last commit. Most libraries here carry an explicit MIT licence, which matters if you plan to fork or vendor skills into a company repo — but it is not universal, so look before you copy.
Ignore the star count. It measures how many people heard about a repo, not whether it fits your work. The most-starred project here is useless to a marketer, and the smallest is the only one packaging a couple of classic CS textbooks.
Frequently asked questions
If I only install one, which should it be?
Pick by what you do most days. Shipping code: Superpowers, the biggest single delta available. Running marketing: Corey Haines’ collection. Struggling to get Claude to open a spreadsheet: Anthropic’s document skills. Framework libraries like ours are usually the second install, because they change the quality of decisions rather than the mechanics of work — a subtler improvement to notice on day one.
Do I need a book-framework library if I already run Superpowers?
Depends which complaint you still have. Superpowers governs how your agent works — planning, testing, reviewing, finishing. A framework library governs what method it applies to a decision inside that work. If your agent now plans well and tests properly but still produces pricing with no theory behind it and code reviews with no named smells, that is the gap a framework library fills. If the process is what is still broken, frameworks will not fix it. They compose cleanly, so running both is normal.
Are these libraries Claude Code only, despite the name?
Mostly not. The SKILL.md convention is shared across agents, and Superpowers, Corey Haines’ collection, book-to-skill and ours all document use with Codex, Cursor and others alongside Claude Code — the differences are in where each agent looks for skills, not in the file. Anthropic’s repo is naturally Claude-shaped and some of its skills lean on Claude-specific surfaces.
Does a bigger catalogue mean a better library?
No, and past a point it is a liability. Every installed skill adds a description to the list the agent chooses from, so two hundred skills with mediocre descriptions select worse than twenty with sharp ones. The more useful number is how many of a library’s skills you can imagine firing this month.
Where can I see all of these listed in one place?
There is no complete registry, which is part of why this page exists. agentskills.io documents the open format these libraries build on, and each repo’s README lists its catalogue. If you know a library that belongs here and is not, open an issue on our repo — we would rather this page be accurate than flattering.
The useful conclusion
There is no best skills library, and any page telling you otherwise is selling something — including, potentially, this one. There is a best library for the complaint you have right now: process, channel execution, file handling, or domain method. Name the complaint and the choice makes itself; usually the answer is two libraries covering two axes rather than one covering everything badly.
If your complaint is that your agent produces confident work with no method behind it, that is the gap we built our 50 skills and 12 guided journeys to close. If it is one of the other complaints, install the library above that matches — we would rather you solve the problem than use our thing.