ComposioHQ/awesome-claude-skills
Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.
ComposioHQ/awesome-claude-skills
ComposioHQ/awesome-claude-skills is a large, active curated collection of Claude Skills and related resources for Claude.ai, Claude Code, and the Claude API. It is especially notable for its Composio automation focus: the repo includes a connect-apps plugin, Composio skill packs, and many task-specific skills spanning productivity, writing, development, media, and app automation. With 49,350 stars and 5,107 forks, it is a high-interest upstream for forks that want a broad catalog plus practical automation entry points.
Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.
Choose a fork to inspect
Prefer this fork if you want OpenCode-native workflow support and MCP-driven skill management. Prefer upstream if you want the freshest Claude-oriented catalog and the broadest upstream ecosystem coverage.
Choose upstream unless you specifically need an older, unmodified snapshot; this fork appears stale and adds no visible value on its own.
Prefer upstream unless you specifically want a pinned snapshot; this fork adds no new capabilities and is already behind recent upstream automation work.
Prefer upstream unless you need a frozen baseline. This fork adds no visible capabilities and lags behind recent upstream automation and cleanup work.
Choose this fork only if you want the upstream catalog exactly as of early February 2026. If you want the latest Claude/Composio skill coverage or active maintenance, use upstream instead.
Choose this fork if your priority is Chinese documentation and easier local adoption; choose upstream if you need the newest automation skills, plugin changes, and latest catalog updates.
Prefer upstream unless you specifically want an older, stable snapshot; this fork adds no visible capabilities and is materially behind recent upstream updates.
Prefer upstream unless you specifically want a near-mirror snapshot; this fork adds no clear capabilities and is already lagging by one upstream commit.
Choose this fork if you want a narrower, customized skill set with a few added workflows and do not need the full upstream document-processing depth or latest Composio-heavy expansion. Choose upstream if completeness and ongoing breadth matter more than pruning.