Awesome Claude Plugins (Composio)

What It Does

Composio's awesome-claude-plugins is two things at once. It is a curated awesome-list README indexing 51 Claude Code plugins across 11 categories (integrations, frontend, git, code quality, backend, devops, docs, security, productivity, companion, and image/video generation). And it is also a real, installable Claude Code plugin marketplace shipping 25 production-ready plugins in-repo, registered through a .claude-plugin/marketplace.json manifest that the Claude Code CLI accepts natively.

The headline plugin is connect-apps, which routes Claude Code through Composio's MCP gateway to take actions in 1,000+ services (Gmail, Slack, GitHub, Notion, Linear, Jira, and the rest). Around that, the repo aggregates plugins from multiple authors: Avi Fenesh's perf/ship/audit-project (v3.7.2, 100+ files each), Joey Nguyen's skill-bus (skill composition middleware), and a long tail of one-file community contributions (commit, code-review, bug-fix, debugger). The target user is a Claude Code customer who wants to extend the editor with slash commands, sub-agents, hooks, and MCP integrations without writing the glue themselves.

The Good

The install path is one-command and works. Verified end-to-end on Claude Code 2.1.152: claude plugin marketplace add https://github.com/composio-community/awesome-claude-plugins succeeded, then claude plugin install connect-apps@awesome-claude-plugins installed and enabled the plugin in under two seconds. The same flow worked for perf (the largest plugin, 9 skills + 6 agents). claude plugin details perf@awesome-claude-plugins returned a real component inventory with projected token costs (always-on ~402 tokens, with per-component on-invoke costs broken out). The marketplace manifest itself passes claude plugin validate --strict . cleanly. This is the gold-standard install experience for a Claude Code marketplace.

Three plugins carry real depth, not just prompts. perf (2,114 lines across 115 files, by Avi Fenesh) is a rigorous performance investigation workflow with separate skills for baseline, benchmark, profile, code-paths, theory, and theory-testing, plus six specialized agents (perf-orchestrator, perf-analyzer, perf-theory-gatherer/tester, perf-code-paths, perf-investigation-logger). ship (2,303 lines, 101 files) is a complete commit-to-production PR workflow with collectors, patterns, repo-map, drift-detect, and perf subdirectories containing real JavaScript. skill-bus (2,097 lines, 28 files, by Joey Nguyen) is skill-composition middleware: a Python dispatcher plus shell hooks that wire context, conditions, and downstream skill subscriptions into any skill invocation without modifying it. These three would be serious standalone plugins.

The connect-apps plugin is the killer feature for Claude Code users who want real-world actions. The setup flow is a single slash command (/connect-apps:setup) that asks for a Composio API key, writes the MCP server config to ~/.mcp.json, and tells the user to restart Claude. Once connected, Claude can send emails, create issues, post Slack messages, and update databases across 1,000+ services through one MCP endpoint with built-in auth. For users who want Claude Code to take actions rather than just generate text, this is the shortest path.

The awesome-list curation adds standalone value beyond the bundled plugins. The README indexes 26 external plugins with one-line summaries and links: AgentLint (33-check AI agent compatibility linter), maestro-orchestrate (22-subagent orchestration), security-sweep (OWASP Mobile + LLM Top 10 scanner), context-mode (98% context savings via sandboxed subprocesses), backlog (24 cross-session MCP task tools), CCHub (desktop app for managing the Claude Code ecosystem), and nano-banana (Gemini image generation). Even readers who never install a single in-repo plugin get a useful discovery surface.

The Bad

No LICENSE file exists at the repo root, despite the README badge claiming MIT. Confirmed both locally (ls LICENSE* returns nothing) and via the GitHub API ("license": null). The README's contributing guide invites readers to fork and submit plugins, but without a LICENSE file the default copyright reserves all rights. For a curated marketplace whose entire value proposition is "copy these and use them," this is a real gap, not a paperwork technicality. The per-plugin plugin.json files do declare "license": "MIT" for the Avi Fenesh and Joey Nguyen plugins, but the repo as a whole has no license.

16 of 25 plugins fail claude plugin validate --strict. The marketplace manifest passes strict validation, but per-plugin strict validation reveals uneven quality. Nine plugins are missing the version field (artifacts-builder, canvas-design, changelog-generator, connect-apps, developer-growth-analysis, frontend-design, mcp-builder, senior-frontend, theme-factory), which fails under --strict as a warning. More seriously, five plugins have malformed YAML frontmatter that fails to parse at runtime: backend-architect, create-pr, frontend-developer, skill-bus, and test-writer-fixer. Claude Code silently drops all frontmatter metadata for these plugins, meaning their descriptions, tool lists, and author fields never load. Two more (ship, audit-project) ship command .md files with no frontmatter block at all.

The marketplace manifest omits skill-bus. The repo contains 25 plugin directories with valid plugin.json files, but both marketplace.json (top-level) and .claude-plugin/marketplace.json list only 24 entries. skill-bus is silently missing from the installable manifest, so users who try claude plugin install skill-bus@awesome-claude-plugins will fail despite the plugin existing in the repo and being documented in the README. This is the kind of drift that the validation step should catch.

The documented clone URL points at the org's old name. The README's install instructions (lines 53 and 177) say git clone https://github.com/composiohq/awesome-claude-plugins.git, but the repo actually lives at composio-community/awesome-claude-plugins. The old URL returns HTTP 301 and redirects, so cloning still works, but the documentation is stale. Two clone commands in the same README both use the wrong org.

Quality variance is extreme. The three deep plugins (perf, ship, audit-project) are 100+ files each. The bottom of the distribution is bug-fix (18 lines, one agent file), commit (27 lines, one command), and code-review (22 lines, one command). These are not plugins in any meaningful sense, they are single markdown prompts. The security-guidance plugin is attributionally suspicious: its plugin.json says "author": {"name": "David Dworken", "email": "dworken@anthropic.com"} and the README's frontend-design entry is attributed to Anthropic, but neither attribution is sourced to a canonical Anthropic repo. They may be legitimate imports from claude-plugins-official, but the provenance is not documented.

The headline feature routes through a paid gateway. The 1,000+ apps claim for connect-apps is really "1,000+ apps via Composio's hosted MCP gateway," which requires a Composio API key and routes traffic through connect.composio.dev. The free tier exists but the architecture is vendor lock-in by design. Users who want self-hosted MCP integrations should look at the alternatives below.

270 open issues against 1,843 stars. That is a 14.6% issue-to-star ratio, high even for an awesome-list that accepts community PRs. The PR queue is not being actively triaged, which contributes to the validation drift above.

Smoke Test Results

Host-based structural validation and live install verification against Claude Code 2.1.152, run on macOS aarch64. The repo was cloned shallow to /tmp/composio-awesome-claude-plugins and exercised with the real claude plugin CLI.

Structural validation

$ python3 /tmp/validate-composio.py
[PASS] repo cloned
[PASS] README.md present
[FAIL] LICENSE file present at repo root -- README declares MIT but no LICENSE file exists at repo root
[PASS] top-level marketplace.json present -- 24 plugins declared
[PASS] .claude-plugin/marketplace.json present -- 24 plugins declared
[PASS] every top-level plugin dir has a plugin.json -- 25 plugin dirs, 25 plugin.json files
[PASS] all plugin.json files are valid JSON with name+description -- 25/25 valid
[FAIL] marketplace.json entries match filesystem plugin dirs -- fs-only: ['skill-bus']; mp-only: []
[PASS] every .claude-plugin/marketplace.json source path resolves to a real dir
[PASS] at least 10 SKILL.md files across plugins -- 23 SKILL.md files
[PASS] at least 10 command .md files across plugins -- 26 command files
[PASS] at least 5 agent .md files across plugins -- 12 agent files
[PASS] all README local ./plugin links resolve to real directories
[FAIL] no plugin dir is empty of markdown content -- empty: ['security-guidance']
[PASS] security-guidance plugin has actual content -- Python hook + hooks.json (hook-based plugin, not md-based)

=== SUMMARY: 13/16 checks passed ===

Pass rate: 13 of 16. The three failures are: missing LICENSE at repo root, skill-bus present on disk but missing from marketplace.json, and security-guidance flagged as md-empty (a false positive since it is a hook-based plugin shipping a Python file). The first two are real findings.

Full structural validation log →

Per-plugin strict validation (with `claude plugin validate --strict`)

$ for d in */; do claude plugin validate --strict "$d"; done
PASS: agent-sdk-dev PASS: bug-fix PASS: code-review
PASS: commit PASS: debugger PASS: documentation-generator
PASS: perf PASS: pr-review PASS: security-guidance
FAIL: artifacts-builder FAIL: audit-project FAIL: backend-architect
FAIL: canvas-design FAIL: changelog-generator FAIL: connect-apps
FAIL: create-pr FAIL: developer-growth-analysis
FAIL: frontend-design FAIL: frontend-developer FAIL: mcp-builder
FAIL: senior-frontend FAIL: ship FAIL: skill-bus
FAIL: test-writer-fixer FAIL: theme-factory

Pass rate: 9 of 25. Failure breakdown: 9 plugins missing the version field (warning under strict), 5 plugins with unparseable YAML frontmatter (real bug, metadata silently dropped at runtime), 2 plugins with command files missing the frontmatter block entirely. The marketplace-level strict validation passes because it only checks the manifest, not the per-plugin internals.

Full per-plugin strict log →

Functional verification (does the install flow actually work?)

$ claude plugin marketplace add /tmp/composio-awesome-claude-plugins
✔ Successfully added marketplace: awesome-claude-plugins (declared in user settings)

$ claude plugin install connect-apps@awesome-claude-plugins
✔ Successfully installed plugin: connect-apps@awesome-claude-plugins (scope: user)

$ claude plugin install perf@awesome-claude-plugins
✔ Successfully installed plugin: perf@awesome-claude-plugins (scope: user)

$ claude plugin details perf@awesome-claude-plugins
perf 3.7.2
 Component inventory
 Skills (9) analyzer, baseline, benchmark, code-paths, investigation-logger, perf, profile, theory, theory-tester
 Agents (6) perf-theory-gatherer, perf-theory-tester, perf-orchestrator, perf-investigation-logger, perf-analyzer, perf-code-paths
 Projected token cost
 Always-on: ~402 tok added to every session

$ claude plugin uninstall connect-apps@awesome-claude-plugins
✔ Successfully uninstalled plugin: connect-apps
$ claude plugin uninstall perf@awesome-claude-plugins
✔ Successfully uninstalled plugin: perf
$ claude plugin marketplace remove awesome-claude-plugins
✔ Successfully removed marketplace: awesome-claude-plugins

Functional pass rate: 6 of 6. Marketplace add, single-plugin install (small + large), plugin details with token cost breakdown, uninstall, and marketplace removal all succeeded. The install flow is real and the component inventory data is genuine.

Full functional log →

What the runs tell you

The install path is production-grade: marketplace add, plugin install, plugin details, and uninstall all work as documented, and the manifest passes strict validation. The quality gap is entirely inside the individual plugins: 16 of 25 fail strict validation, mostly for missing versions or broken YAML frontmatter. The runtime tolerates these (plugins still load with empty metadata), but CI does not run claude plugin validate --strict per-plugin, so the drift survives. The missing skill-bus entry in marketplace.json is a clear manifest bug.

Setup Walkthrough

1. Add the marketplace to Claude Code:

 claude plugin marketplace add https://github.com/composio-community/awesome-claude-plugins

1. Install the plugin you want:

 claude plugin install connect-apps@awesome-claude-plugins

1. For connect-apps specifically, run the setup slash command inside Claude Code:

 /connect-apps:setup

Paste a Composio API key from dashboard.composio.dev when prompted. The plugin writes the MCP server config to ~/.mcp.json. Restart Claude Code to activate.

1. To browse components and token cost before committing:

 claude plugin details perf@awesome-claude-plugins

1. To remove everything:

 claude plugin uninstall <name>@awesome-claude-plugins
 claude plugin marketplace remove awesome-claude-plugins

Gotcha: skill-bus is documented in the README but is not in the marketplace manifest. Clone-and-load locally with claude --plugin-dir ./skill-bus if you need it.

Gotcha: the README's clone URL uses the old composiohq org name. It still works via HTTP 301 redirect, but the canonical URL is composio-community/awesome-claude-plugins.

Alternatives

1. anthropics/claude-plugins-official -- the first-party Claude Code plugin marketplace from Anthropic. Smaller, slower-moving, but every plugin is Anthropic-vetted and the license situation is clean. Prefer this for enterprise use.
2. getsentry/skills -- Sentry's internal engineering skill pack (reviewed by GearScope on 2026-07-24). 28 skills following agentskills.io, with a real skill-scanner and skill-writer workflow. Better quality floor, narrower scope (Sentry-flavored engineering). Prefer this for skill-authoring tooling rather than end-user plugins.
3. vercel-labs/skills -- the npx skills package manager (reviewed 2026-07-16). A different model: instead of one marketplace, it is a universal installer that pulls skills from any repo following the agent skills open standard. Prefer this if you want to mix plugins from multiple marketplaces rather than committing to Composio's curation.