What is a skills hub, and which one should you use?

A skills hub is a directory of skills for AI apps. Each entry points to a small folder with a SKILL.md file that teaches an app such as Claude, ChatGPT or Codex how to do a task. The hub's job is to help you find the right one and show you how to install it. For the file itself, read what SKILL.md is.

People also say skills marketplace, skills directory or skills registry. They overlap. A marketplace suggests buying and selling. A hub suggests a central meeting point. In practice, they all do the same basic thing: list skills.

Ignore the headline number of skills. Look for these instead.

• A readable page per skill, in plain words, not only a file dump.
• Clear install steps for the app you use, whether that is Claude, ChatGPT or Cursor.
• The publisher and licence, so you know who made it and what you may do with it.
• A way to browse by job, such as writing or data analysis, not just a search box.
• Some sign that someone looked, whether that is a human pick, an audit or both.

Open hubs list almost everything that exists in public code repositories. You get reach, and you also get copies, abandoned experiments and the odd risky skill. They suit people who already know what to look for.

Ranked hubs sort skills by installs. Popularity is a useful hint, but it rewards whatever got attention early, and a high number is not a quality check.

Curated hubs keep the list short and put effort into each entry. You see less, and what you see has been read. That is the approach we take. Our categories group skills by the result you want, such as slides, documents or research.

You do not have to use a hub. Claude can take a .zip you upload yourself. Codex can install from OpenAI's curated list with a short command. Developer tools can copy a folder into place. A hub just makes finding easier and installing less error-prone.

If you want the command-line route, see npx skills. If you would rather click and read, a curated hub with install steps in words is the easier road.

Pick a job you repeat. If you write a lot, look at Humanizer or Copy Editing. If you do research, try Customer Research. Read the page, follow the install steps for your app, and test it on something small.

Our approach is simple: fewer skills, each explained properly. Free and Premium tiers are coming, and the pricing page says what is planned.

A hub is a middleman. It does not make the skills, it points you to them. That means its value is in what it adds: explanations, checks, structure and honesty about what it does not know. When you land on a new hub, spend one minute on four things.

First, find its about page and see who runs it. Second, open a single skill and see how much help you get. Is there anything beyond a file listing? Third, look for the date. Skills change, and information that is months old can be wrong. Fourth, check whether the hub says anything about risk. A hub that is open about its limits, such as saying you should review a skill before you install it, is behaving well.

Good hubs also tell you what they leave out. We keep our list short on purpose and say so. If you want something we do not list, our guide to finding skills points at other places to look and how to check what you find.