How to choose a skill source: collections vs marketplaces vs repos

Choosing a skill source starts by separating discovery from acquisition. A marketplace or directory helps narrow the candidates; the original repository or publisher documentation establishes the actual instructions, dependencies and installation route. One skill can appear on several sites, so the number of listings is not independent evidence of quality.

What the five source types are useful for

Official vendors

Start here to understand a publisher’s skill structure or product conventions. For example, anthropics/skills exposes first-party repository content to inspect. Official identity establishes origin; fit for your host, version and task still requires a separate check. Browse official vendor sources, or browse the specific entries in official vendor sources.

Marketplaces

Use a marketplace to compare capabilities against a defined requirement. Authors, dependencies, service terms and installation methods may differ between entries. Examine the individual item; rankings and reviews are discovery signals, not compatibility evidence. Browse skill marketplaces.

Open-source repositories

Repositories let you read instructions and code, study an implementation or adapt material under its license. First distinguish an actual skill from a configuration example or an awesome list linking to external projects. Readable code is not the same as reviewed code. Browse open-source repository sources.

Community rankings

Community sources can expand a shortlist and reveal projects you have not encountered. Their statistics and editorial methods differ, so trace entries to the original project instead of treating a ranking as a conclusion about safety or compatibility. Browse community sources.

Aggregator directories

Directories support browsing across sources and narrowing by task. SkillFlux is this kind of discovery entry point: resource pages link to original sources. A catalog listing does not establish direct installation support through SkillFlux. Browse aggregator directories.

How to make a decision from a shortlist

1. Write down the task, input, expected output and host; remove candidates that do not fit the environment.
2. Record the original repository, publisher and version to identify duplicate listings of the same resource.
3. Read the entry instructions, scripts, license and dependencies, including file access and external service requirements.
4. Try a small task whose result you can inspect, then decide from the output whether to keep the skill.

Assess maintenance through the project’s own documentation, change history and issue handling. A SkillFlux record date describes our catalog material; it does not prove a recent upstream release. An unchanged project is not necessarily unusable either.

Continue with the task you need to complete

For open-ended discovery, read the source selection scenario. For an existing codebase, see the project connection scenario, and for post-setup maintenance the project skills maintenance scenario. If the goal is an external tool connection, filter the directory by MCP resources.