“25 Skills” — And The First Box Is Fifteen Of Them

The card is a wall chart. “Build Your Team with Claude — 25 essential Claude skills, organised like a real company.” In the middle, a single box labelled claude-code with the subtitle The Operating System. Below it, five colour-coded columns — Developers, Designers, Marketing, Social Media, Small Business — and five boxes under each, every one with a job-title nickname. Skill Forge. Docs Fetcher. Word Smith. Ghostwriter. Debt Chaser.

It is a lovely piece of design and a genuinely useful list. It is also not an organisation chart, and the first box gives the game away.

Box one is a grid of its own

Top left, under Developers, sits Superpowers, nicknamed Skill Forge. The card’s own one-line description reads: “14-skill power pack.”

We opened the repository to check. obra/superpowers carries 298,209 stars and describes itself as “an agentic skills framework & software development methodology.” Its skills/ directory currently holds fifteen folders:

brainstorming · diagnosing-superpowers · dispatching-parallel-agents · executing-plans · finishing-a-development-branch · receiving-code-review · requesting-code-review · subagent-driven-development · systematic-debugging · test-driven-development · using-git-worktrees · using-superpowers · verification-before-completion · writing-plans · writing-skills

Fourteen plus an entry point, which is presumably how the card got to fourteen. Either way the arithmetic is the same: the chart shows twenty-five boxes, and the first one contains fifteen. Count what is actually behind the grid and you are nearer forty things than twenty-five.

That is not a gotcha. It is the most useful fact on the card, and it is the one the layout hides: these boxes are not the same size. One of them is a whole methodology with its own internal structure — plans, code review, worktrees, debugging, verification — and it sits in a square the same size as “Chase late invoices.”

And four of the boxes are not skills

The word across the top is “skills”, and in Claude Code a skill is a specific thing: a folder with a SKILL.md in it, which you or Claude invoke by name. Several of these boxes are something else entirely, and we could verify three of them directly.

• Context7 — upstash/context7, 62,948 stars, described as a platform for “up-to-date code documentation for LLMs and AI code editors.” It is an MCP server. It reaches Claude through a line in .mcp.json, not a folder.
• Claude-Mem — thedotmack/claude-mem, 100,099 stars, “persistent context across sessions for every agent… captures everything your agent does during sessions.” That is a hooks-and-capture system, not something you invoke by name.
• Superpowers — a framework that installs a bundle, as above.
• UI UX Pro Max, by contrast, checks out exactly as billed — nextlevelbuilder/ui-ux-pro-max-skill, 135,171 stars, “an AI skill that provides design intelligence.” A real skill.

Why this matters is not pedantry about vocabulary. It is that the card’s own footer says “check each skill’s official page before you install it” — and the four kinds of thing on this chart are not installed the same way at all.

Diagram: one word, four mechanisms

If you want the full version of which of these loads automatically and which sits inert until something registers it, we mapped it last week: what actually loads in a .claude/ folder. The short version is that a skill is found by being in the right folder, and an MCP server or a hook is found only by being named in a settings file.

Five, five, five, five, five

Now count the columns. Developers: five. Designers: five. Marketing: five. Social Media: five. Small Business: five.

No company has ever looked like that. Not one. Real departments are lopsided — engineering is nine people and finance is a part-timer, or the other way round — because headcount follows where the work is, not where the layout is. The grid is five by five because a grid is five by five. It is a design constraint wearing the costume of an organisational insight.

And the consequence is not cosmetic. On this chart, Plan Payroll occupies exactly as much space as Copywriting. For the person this card is aimed at — one operator with a laptop — those two are not remotely the same size of problem. One of them is most of the week. The other happens twelve times a year and probably involves an accountant.

Read as a menu, the card is generous and useful. Read as an org chart, it tells you that your attention should be spread evenly across five areas, which is close to the most expensive thing a solo operator can believe.

All twenty-five, with what each one actually is

The yellow column is a different risk class

Four of the five Small Business boxes — cash flow, invoices, payroll, tax — share something none of the other twenty-one do: the model does not have the data. It has no access to your ledger, your invoice list, your payroll run or your books. Point it at those four with nothing attached and it will produce something that looks exactly like a cash-flow snapshot, assembled entirely out of plausible numbers.

Two of them go further than that. Invoice Chase ends in a message sent to a real client. Tax Prep ends in a filing with legal consequences and a jurisdiction the card never names — payroll and tax rules are not the same in Hanoi, London and Texas, and a prompt has no idea which one you are in.

The card’s footer warns that “skill names and features change often.” That is a warning about the catalogue. The yellow column needs a different warning, about inputs and consequences, and it does not have one. Attach the data or do not run the box.

There is not one line between any two boxes

Here is the thing a real org chart has that this one does not: arrows. Lines showing who hands what to whom. Twenty-five boxes sit on this chart and not one of them connects to another.

And they obviously should. Nine of them are one job. Look:

That chain crosses Marketing, Social Media and Designers — three colours on the card. On a grid they look like three teams. In practice they are one loop that a single person runs in one afternoon, and the handoff between steps is where all the quality lives. A company is not a list of job titles. It is a set of handoffs.

Notice also that step 5 has exactly one candidate. Of the twenty-five boxes, twenty-four produce something and one judges it — Taste, filed under Designers as a “design-taste critic”. That is the same ratio we keep finding on cards like this, and the same conclusion: the thing that makes the output cannot be the thing that grades it.

If you install five, install these

For one person making content, the honest starting set is not one from each column. It is the chain above, truncated: Customer Research, Copywriting, Hook Generator, one of Post Writer or Reels Scripting, and Taste. Five boxes, four from two columns, one deliberate outsider to do the judging. That is a working loop on day one.

Superpowers belongs on a second list, not this one — not because it is weak, but because it is fifteen things, and installing fifteen things on day one is how you end up unable to say which one helped. The card’s own grid makes that mistake look like one tick box.

Four honest caveats

1. We installed none of these. Everything above comes from the card, from four public repositories and from Anthropic’s documentation. We cannot tell you whether any individual skill is good, only what kind of thing it is and how it reaches Claude.
2. Star counts are attention, not quality. We quote them because they establish that a project is real and widely used, nothing more. We have had that lesson the hard way, on a card where the numbers turned out to be understated, and the correction went the opposite way from what we expected.
3. “Unverified” is not “fake”. Eleven boxes carry generic names — Copywriting, Taste, CRO — and a generic name is hard to trace to one canonical page. They may all be real and excellent. We are reporting what we could and could not pin down, which is also a practical warning: budget time for the search.
4. The card is right that this stuff moves. Its footer says skill names and features change often, and that is the correct instruction. Our snapshot is 13 October 2026 and it will rot like any other.

The one-line version

Twenty-five boxes, one of which is fifteen, four of which are not skills, five columns of exactly five because grids are rectangular, and not one arrow between any two of them. It is an excellent menu and a misleading map. Take it as a shopping list, install the five that form one loop, and draw the arrows yourself — because the arrows are the company, and the boxes are just the staff.

The same author’s thirty marketing use cases collapsed into five operations when you looked at the verbs; this chart collapses the same way when you look at the handoffs. Different card, same lesson: the count is never the structure.