awesome-claude-skills: 1000+ Claude skills and plugins

A catalog of 1000+ Claude Skills that extends Claude Code from text generation to document and app actions.

GitHub ComposioHQ/awesome-claude-skills Updated 2026-09-04 Branch master Stars 73.9K Forks 8.5K

Claude Skills AI workflows MCP Gateway Claude Code

🧭 Decision Guide

Try it if you

You need to load local skills such as docx, pdf, or xlsx in Claude Code.
The README's “Using Skills in Claude Code” section places skills in ~/.config/claude-code/skills/; “Document Processing” lists docx, pdf, and xlsx.
You want Claude to send Slack messages or email, or create issues.
The README's “Quickstart: Connect Claude to 1000+ Apps” explicitly lists sending emails, creating issues, and posting to Slack.
You want to reuse the same workflow instructions across Claude, Codex, Cursor, or Gemini CLI.
The README's “What Are Claude Skills?” section says Skills support Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, and Gemini CLI.

Skip it if you

Your goal is only to connect external systems and you do not need workflow instructions.
The README explicitly distinguishes Skills from MCP: MCP handles external-system access while Skills define workflow behavior; see the MCP Gateway section.
Your environment cannot provide a Composio API key or does not allow access to 1000+ external apps.
The connect-apps setup requires pasting an API key at /connect-apps:setup and connects to 1000+ apps.
You must confirm an open-source license and recent maintenance activity before adoption.
Project data marks the license and maintenance status as Unknown, with 0 contributors and 0 releases.

Requirements

A local Claude Code environment; the README specifies ~/.config/claude-code/skills/ as the skill directory.
connect-apps requires a Composio API key, which the README says to paste at /connect-apps:setup.
Using the Claude Skills API requires the anthropic client and an API key; the example model is claude-3-5-sonnet-20241022.

First step (verbatim from README)

claude --plugin-dir ./connect-apps-plugin

Watch out

After installing connect-apps, you must run /connect-apps:setup and restart Claude.
The README's Quickstart has three steps: Install the Plugin, Run Setup, and Restart & Try It.
The SKILL.md body is typically under 5,000 tokens, and auxiliary files load on demand.
The README's “What Are Claude Skills?” section says the full SKILL.md body is typically under 5,000 tokens and scripts and references load on demand.
A skill directory requires SKILL.md; scripts, templates, and resources are optional directories.
The README's “Skill Structure” marks SKILL.md as Required and scripts, templates, and resources as Optional.

Alternatives

Composio MCP Gateway：Better when you need a single MCP endpoint with built-in authentication, team access controls, and audit logs rather than only reusable Skill workflows.
Give your skills real-world actions
Use the Claude Skills API directly：Better when your program must load skills with skills=["skill-id-here"] instead of placing a local directory in Claude Code.
Using Skills via API

Not stated in the README

The README materials do not specify versions, dependency installation methods, or test results for each Skill.
The README materials do not specify the licensing boundaries for Claude Skills, Composio, or external Skills.
The README materials do not specify the permission scope, data-processing location, or cost of the connect-apps API key.
The README materials do not provide the latest update date; project metadata marks maintenance status as Unknown.
The README materials do not provide language distribution; the technology stack is marked Mixed/Unknown.

💡 Deep Analysis

What technical requirements should be considered when using ComposioHQ/awesome-claude-skills?

Technical Requirements Assessment ¶

Using ComposioHQ/awesome-claude-skills requires consideration of the following key requirements:

Environment Compatibility ¶

Language Environment: Ensure Unknown environment compatibility
Version Requirements: Check specific version dependencies
Related Dependencies: Evaluate project dependency requirements

License Compliance ¶

License Type: Project uses Unknown license
Usage Restrictions: Confirm if it meets your use case requirements

Implementation Recommendations ¶

Documentation First: Review installation and configuration instructions in project documentation
System Requirements: Understand specific system requirements and dependencies
Testing Validation: Conduct testing in development environment first

Important: It’s recommended to perform thorough compatibility testing before production use

What core problems does ComposioHQ/awesome-claude-skills solve?

Core Positioning: Based on project information analysis, ComposioHQ/awesome-claude-skills primarily addresses problems related to A curated list of awesome Claude Skills, resources, and tools for customizing Claude AI workflows.

Technology Stack ¶

Primary Language: Unknown
Target Domain: Focus on specific needs within this language ecosystem

Understanding Recommendations ¶

Review Documentation: Learn about specific features through project documentation
Evaluate Applicability: Confirm whether it fits your use case

Tip: It’s recommended to start with the project’s README and example code

What use cases is ComposioHQ/awesome-claude-skills suitable for?

Use Case Analysis ¶

Based on ComposioHQ/awesome-claude-skills’s technical characteristics, it’s suitable for the following use cases:

Technology Stack Alignment ¶

Primary Fit: Projects requiring Unknown technology stack
Ecosystem Compatibility: Scenarios with good integration with related technology ecosystems

Evaluation Recommendations ¶

Specific applicability should be determined based on the project’s core functionality:

Documentation Review: Read project documentation to understand functional boundaries
Example Analysis: Review example code to understand usage patterns
Community Research: Learn about community use cases and best practices
Maintenance Assessment: Consider project maintenance status and long-term development plans

Decision Points ¶

Feature Alignment: Whether project features meet specific requirements
Technical Debt: Maintenance costs of adopting the project
Alternative Solutions: Whether more suitable alternatives exist

Recommendation: Consider conducting small-scale proof-of-concept testing before final decision

✨ Highlights

Curates 1000+ production-ready Claude Skills and Plugins
Covers document processing for docx, pdf, pptx, and xlsx
connect-apps connects Claude to 1000+ apps for actions
Skills load progressively, with about 100 tokens per description
Repository metadata shows 0 contributors and 0 releases

🔧 Engineering

Defines reusable workflows with SKILL.md and YAML frontmatter
docx, pdf, pptx, and xlsx cover common document tasks
connect-apps uses Composio to connect to 1000+ apps
Supports Claude.ai, Claude Code, the API, and Cursor

⚠️ Risks

The license is unknown; the README's License section was not provided
Maintenance is unknown; metadata shows 0 recent commits and 0 releases
connect-apps requires a Composio API key and access to external apps
Dependencies, permissions, and quality of external Skills are not uniformly documented

👥 For who?

Developers using Claude Code who want to load local SKILL.md files
Teams needing automation for docx, pdf, pptx, or xlsx
Users who need Claude to act on Slack, email, and issues
Agent developers using the Claude API, Cursor, or Gemini CLI