Claude Code Skills Marketplace 101

Claude Code's real power isn't just the model. It's what you can build on top of it.

Skills extend what your agents can do: web search, calendar access, Slack integration, custom workflows. But right now there's no single official Claude Code skills marketplace. What exists is a patchwork of community repos and platform catalogs that each solve part of the problem.

This guide maps out where to find skills today, how to publish your own, and what separates a good skill from a frustrating one.

The Current Ecosystem

The Claude Code skills ecosystem is young. Anthropic hasn't shipped an official marketplace yet, so the community has filled the gap in two ways: open GitHub repos that anyone can contribute to, and platform-specific catalogs like Duet's that validate skills before listing them.

Both have their place. The community repos move fast and cover a lot of ground. The platform catalogs are slower but more reliable.

Community Sources

awesome-claude-code

The go-to starting point for community skills is the awesome-claude-code GitHub repository. It's a curated list of Claude Code resources including skills, MCP servers, custom CLAUDE.md configurations, and utility scripts that the community has built and shared.

Strengths: breadth, freshness, and the fact that anyone can contribute. New skills appear regularly as people share what they've built for their own workflows.

Limitations: variable quality. Because there's no formal review process, some skills are polished and well-documented while others are rough drafts or narrowly specific to the author's setup. You'll need to read the source yourself and decide if it's worth integrating.

For developers comfortable reading code, this is a great place to browse. For people who want something they can install with confidence, a validated catalog is a better first stop.

Duet's Skills Catalog

Duet maintains a curated catalog of skills that have been validated, documented, and tested before listing. When you open the skills section in Duet, you're browsing a set of extensions the team has confirmed actually work as described.

The current catalog includes:

• Web Search — real-time search results surfaced directly in agent sessions
• Calendar Access — read and write events from Google Calendar or Outlook
• Slack Integration — send messages, read channel history, and trigger actions
• GitHub Tools — open PRs, review diffs, and query repo state without leaving the agent
• Email (via Resend) — send transactional emails and notifications from agent workflows
• Custom Webhooks — trigger or receive external events to connect Claude Code to any service

What makes Duet's catalog different: every skill goes through validation before it's listed. That means tested inputs and outputs, a working SKILL.md, and known-good configuration. When you install from the catalog, you're not debugging someone else's prototype; you're dropping in something confirmed to work.

Skills install in one click from the catalog. No manual file copying, no PATH configuration, no guessing at environment variables. You install, configure the required inputs (API keys, settings), and the skill is live in your agents.

How to Publish Your Own Skill

Publishing to Duet's catalog is open to anyone. If you've built something useful for your own Claude Code workflow, you can share it with every other Duet user.

The process:

1. Create the skill locally. Build and test your skill in your own Duet environment until it does what you need reliably.
2. Write a clear SKILL.md. This is the skill's documentation: what it does, what inputs it needs, what outputs to expect, and any caveats. Good documentation is the difference between a skill people use and one they ignore.
3. Run validation. Duet's CLI includes a validation step that checks your skill's structure, catches common issues, and confirms the inputs/outputs are well-formed.
4. Submit through the contribution flow. Once validation passes, you submit the skill for review. The Duet team checks it, tests it against the documented behavior, and either approves it or comes back with feedback.
5. It ships to the catalog. After approval, your skill appears in the catalog for every Duet user to install.

You can also share skills by publishing them to GitHub (your own repo or a community list like awesome-claude-code). This skips the review process and gets your skill out faster, but it also skips the validation and one-click distribution. For serious tools, the Duet catalog route is worth the extra step.

What Good Skills Look Like

The best skills in any ecosystem, community or official, share four qualities. Before you install or publish, it's worth checking these:

Fit. A good skill does one thing and does it well. Skills that try to be general-purpose tools usually end up being awkward at everything. The Slack integration skill sends messages and reads channels. It doesn't also try to manage your calendar. Narrow scope means reliable behavior.

Scope. Related to fit: a good skill has a clear boundary. You should be able to state in one sentence what it does and what it doesn't do. If the description requires a paragraph of caveats, the scope is probably too fuzzy.

Documentation. The SKILL.md is the skill's contract with its users. It should tell you exactly what inputs are required, what the outputs look like, and what can go wrong. Skills with vague or missing documentation create support burdens for the author and frustration for users.

Reliability. A skill that works 80% of the time is worse than no skill, because the 20% failures happen in the middle of agent runs and leave you debugging rather than shipping. Before publishing, test edge cases: empty inputs, API rate limits, network timeouts. Before installing, look at whether the skill has active maintenance and recent issues closed.

Epilogue

The Claude Code skills ecosystem is early. What exists today, community GitHub repos and platform catalogs, is the first layer. The range will expand as more builders contribute and as Anthropic develops official tooling.

For now: start with Duet's catalog for reliability, explore awesome-claude-code for breadth, and build your own when neither has what you need. The contribution path from "I built this for myself" to "anyone can install it in one click" is shorter than it looks.

Frequently Asked Questions

Is there a Claude Code skills marketplace?

Not an official one from Anthropic yet. The closest equivalents are community curation repos like awesome-claude-code on GitHub and platform-specific catalogs like Duet's validated skills catalog. Both give you a browseable set of skills, but the platform catalogs add validation and one-click install on top.

Where can I find Claude Code skills to install?

Two main places. Community repos on GitHub (start with awesome-claude-code) give you raw, open-source skills. Duet's skills catalog gives you validated, one-click-install skills that are already tested and documented. Most users start in Duet's catalog for reliability, then explore GitHub for more experimental options.

How do I publish a skill?

Inside Duet you create the skill locally, write a clear SKILL.md, run validation, and submit through the contribution flow. After review it appears in the public catalog. You can also share skills on GitHub, but publishing to Duet gives you one-click distribution and version management.

Do I need to be a developer to use skills from the catalog?

No. Once a skill is published, any Duet user can install it into their personal server with one click. You don't need to understand the underlying code — you just configure the inputs (API keys, search terms, etc.) and let it run.

Can I make money from skills I publish?

Not directly through Duet's catalog today. The main benefit is visibility, usage by other Duet customers, and establishing yourself as a builder in the ecosystem. Some creators also use their skills as portfolio pieces when offering custom agent work.

How often are new skills added to Duet's catalog?

New skills are added regularly as the team and community contribute them. Because every skill goes through validation, the pace is measured rather than explosive — quality over quantity.