ComposioHQ/awesome-claude-skills

This is a discovery list, not a tool you install to change how your agent behaves. Its value is a maintained index of Claude Skills plus a short explanation of the format, so you can judge whether it saves you a search before cloning anything.

The problem

You want Claude Code, Claude.ai or another compatible agent to handle a recurring task consistently — processing documents, running a code workflow, extracting metadata — instead of re-explaining the procedure every session. Finding trustworthy SKILL.md packages means searching scattered personal repositories and blog posts, and many lists mix skills with unrelated plugins. This project instructions page collects links by category and explains how skills are packaged. The result is a starting point for choosing a skill to inspect, not a guarantee that any listed skill works with your client.

What's different

The README goes beyond links by explaining the format: each skill is a folder with a SKILL.md containing YAML frontmatter and Markdown instructions, optionally with scripts, references and assets. It states that the format was released as an open standard and is supported by Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI, Antigravity and Windsurf. That portability claim is the strongest practical argument: a skill is described as usable across those environments, so you do not rewrite instructions per client.

Two trade-offs matter. First, this is a list, so coverage and link freshness depend on contributions; a listed skill's own repository, license and quality are outside this project's control. The README says individual skills may carry different licenses. Second, the list is maintained by Composio and includes prominent promotion for its MCP Gateway and a plugin that connects Claude to apps through Composio with an API key. Treat the directory as a catalogue and the gateway as a separate product decision.

Who should try it

This fits someone already using a Skills-compatible agent who wants an overview of what skills exist and a compact explanation of the packaging standard before writing their own. It also suits a team lead evaluating whether to standardize recurring procedures as portable skill folders.

It is a poor fit if you want a quality-scored directory: there is no evidence here of testing or ranking of individual skills, and the list spans very different domains from document processing to security forensics. If you only need to connect Claude to external apps, the README's connect-apps quickstart is the relevant path, and the long skill categories may be noise.

Requirements and limitations

Adopting anything from this list requires a supported agent and some way to place the skill folder where that agent looks. The README lists several clients but gives no per-client installation steps for individual skills, so you depend on each linked skill's own instructions; the open-standard skills repository is the reference for the format itself. The MCP quickstart shown here is Claude Code-specific, uses a Composio API key, and requires restarting the session — a separate route from browsing skills.

Ongoing care falls on you: links can rot, and licenses differ per skill, so check the source before bundling a skill into a shared workflow. The excerpts also do not describe versioning or a review policy for entries; treat the directory as a lead generator and verify each skill yourself.

HotRepo's take

HotRepo's tracked window is only 2026-10-24 to 2026-10-25, with 77,840 and 77,849 stars recorded (+73 and +79), so persistence cannot be judged from this sample. The repository was created in October 2025. Before relying on the index, check how recently entries were updated and whether the skill you want names your client in its own documentation.