Skill catalog
otherIndex skills by domain.
README.md
Open component record →What ComposioHQ/awesome-claude-skills is—in plain language
Large curated Agent Skills/plugin catalog plus a Composio-powered connect-apps plugin for authenticated actions across many external services.
Mental model: This repository extends a host application. The host loads its commands, skills, hooks, or agents; most day-to-day use happens inside that host rather than by launching a separate app.
Interfacesskill, plugin, MCP gateway
Primary languageNone documented
Typical useDiscover skills by domain or connect agents to SaaS actions such as messaging, issue creation, and database operations.
Your first 15 minutes
- Complete the linked Installation Guide and its verification step.
- Create a disposable test folder or use non-sensitive sample data.
- Run the small example below and observe what files, ports, or prompts appear.
- Read the result before approving writes, network calls, account access, or costs.
- Only then repeat the workflow with a real project.
Starter workflow
open "https://github.com/ComposioHQ/awesome-claude-skills#readme"Complete indexed functionality map
Each card below corresponds to a component identified in the repository research. Open a component record for its path, purpose, capabilities, dependencies, risks, and relationships.
connect-apps
pluginConnect agents to apps through Composio.
connect/
Open component record →Builder/testing examples
skillMCP Builder/Skill Creator/Webapp Testing examples.
README.md
Open component record →Upstream feature-by-feature guide
These capabilities are derived from the current first-party README and supporting documentation. Names follow upstream terminology so you can search the source documentation precisely.
Upstream capability
Give your skills real-world actions
Upstream treats this as a distinct part of ComposioHQ/awesome-claude-skills. In plain language, use this area when your task concerns give your skills real-world actions. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Quickstart: Connect Claude to 1000+ Apps
Upstream treats this as a distinct part of ComposioHQ/awesome-claude-skills. In plain language, use this area when your task concerns quickstart: connect claude to 1000+ apps. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
3. Restart & Try It
Upstream treats this as a distinct part of ComposioHQ/awesome-claude-skills. In plain language, use this area when your task concerns 3. restart & try it. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Contents
Upstream treats this as a distinct part of ComposioHQ/awesome-claude-skills. In plain language, use this area when your task concerns contents. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
What Are Claude Skills?
Upstream treats this as a distinct part of ComposioHQ/awesome-claude-skills. In plain language, use this area when your task concerns what are claude skills?. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Document Processing
Upstream treats this as a distinct part of ComposioHQ/awesome-claude-skills. In plain language, use this area when your task concerns document processing. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Development & Code Tools
Upstream treats this as a distinct part of ComposioHQ/awesome-claude-skills. In plain language, use this area when your task concerns development & code tools. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Data & Analysis
Upstream treats this as a distinct part of ComposioHQ/awesome-claude-skills. In plain language, use this area when your task concerns data & analysis. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Business & Marketing
Upstream treats this as a distinct part of ComposioHQ/awesome-claude-skills. In plain language, use this area when your task concerns business & marketing. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Communication & Writing
Upstream treats this as a distinct part of ComposioHQ/awesome-claude-skills. In plain language, use this area when your task concerns communication & writing. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Creative & Media
Upstream treats this as a distinct part of ComposioHQ/awesome-claude-skills. In plain language, use this area when your task concerns creative & media. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Productivity & Organization
Upstream treats this as a distinct part of ComposioHQ/awesome-claude-skills. In plain language, use this area when your task concerns productivity & organization. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
How to use the main workflows
Choose the smallest relevant function
Start with one capability card instead of asking the repository to do everything at once. This makes permissions, inputs, and output easier to understand.
Prepare a disposable input
Use a sample URL, copied repository, test document, or sandbox account. Keep production credentials and irreplaceable files out of the first run.
Run, observe, and stop
Watch Terminal output or the host application's activity view. If the behavior differs from the README, stop with Control + C or cancel inside the host before retrying.
Inspect the result
Check generated files, diffs, API responses, logs, or previews. Never assume “command finished” means the result is correct.
Save a repeatable recipe
Record the working command and non-secret configuration in your project's README. Store secrets in the documented environment file or password manager.
Copy-paste recipes from upstream documentation
These examples are selected from the repository's first-party documentation. Replace obvious placeholders, keep quotation marks intact, and run them only in the context indicated by the surrounding explanation.
Open the live upstream manual
open "https://github.com/ComposioHQ/awesome-claude-skills#readme"Configuration, accounts, and files
Configuration files
None documented
A configuration file changes behavior without changing source code. Make one change at a time and keep a backup before editing JSON, TOML, YAML, or environment files.
Important directories
connect/
Paths identify where the relevant implementation or generated files live. Paths beginning with ~ are inside your home folder.
Credentials
Composio API key for app actions
Prefer temporary, least-privileged credentials. Never commit .env, tokens, cookies, private keys, or session exports.
External services
Composio
Check pricing, data retention, rate limits, and account permissions before enabling optional integrations.
Safe operating habits
- Use test data first and keep a current backup or Git commit.
- Read commands before pasting. A README is useful evidence, not a substitute for judgment.
- Review agent-generated file changes with
git diffbefore committing. - Keep local services bound to
127.0.0.1unless you intentionally secure and expose them. - Do not give plugins or MCP servers broader filesystem, browser, GitHub, or cloud access than their current task requires.
- Confirm API costs and model names before running large batches.
- Stop and investigate repeated authentication failures instead of pasting a token into multiple places.
Reference and source trail
The manual reflects first-party files checked on August 18, 2026. It explains the indexed repository rather than promising that every optional third-party integration is available or safe.