Awesome Claude Skills by Composio
Awesome Claude Skills
A curated list of Claude skills and plugins, plus Composio's own automation skills for 78 SaaS apps
- 78,221 ★ on the repository
- Last commit
Broad access
Why this level
- connect-apps gives the agent actions in email, chat and CRM accounts
- Requires a third-party gateway API key
- The list links to third-party skills without uniform review
Install
- Works in
Manual install
claude --plugin-dir ./connect-apps-pluginThen /connect-apps:setup and restart Claude Code
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- connect-apps gives the agent actions in email, chat and CRM accounts
- Requires a third-party gateway API key
- The list links to third-party skills without uniform review
This is third-party code. Review the repository files before installing.
What it does
The repository combines a categorized list of third-party skills with its own skills, including changelog-generator, mcp-builder and skill-creator. The connect-apps plugin connects Claude to 1000+ services through Composio to send emails, create issues and post to Slack. Dedicated skills for 78 apps, from HubSpot and Jira to Stripe and Notion, describe tool call sequences via Rube MCP.
Who it is for. Claude users looking for ready skills, and teams automating work across SaaS apps.
Good fit when
- You are looking for a ready skill and want to browse options
- You need the agent to take actions in Gmail, Slack, GitHub or a CRM
- You need guidance on a specific SaaS API through Composio
Not a fit when
- You cannot grant a third-party gateway access to work accounts
- You need Russian service integrations: none are listed
Example request
Create a Linear issue from this bug report and post the link to the team Slack channelLimitations
Most of the list links to third-party repos of varying quality. connect-apps and the automation skills need a Composio API key. The README's manual install instruction uses the ~/.config/claude-code/skills path.
How to disable. Delete the skill folder from the skills directory and stop launching Claude Code with --plugin-dir ./connect-apps-plugin.
FAQ
How do skills differ from MCP?
Per the README, MCP handles connections to external systems, tools are individual actions, and skills define the workflow and order.
Do I need a paid Composio account?
connect-apps needs an API key, and the README points to a free key in the Composio dashboard.
Discussion
No questions or reviews yet.
Related
SkillsSDKs, a CLI and MCP access to over a thousand prebuilt SaaS integrations for agents, with auth and per-user sessions
A plugin from the n8n team: 13 skills and a bundled MCP connection teach Claude Code and Codex to build, edit and validate n8n workflows
Zapier's official MCP plugin: the agent gets actions across thousands of apps through your Zapier account
Connects Claude Code, Cursor, Codex or OpenCode to Telegram, Slack and Discord: teammates message a bot, an agent replies
A Claude Code skill that edits and deploys Home Assistant configuration: YAML automations, validation, deploy and Lovelace dashboards
AI Agent Skills by sanjay3290
AI Agent Skills
Cross-platform agent skills: read-only PostgreSQL, MySQL and MSSQL queries, Google Workspace, Jira, Telegram, text-to-speech and research
README in short
A curated list of 1000+ skills and plugins for Claude.ai, Claude Code, Codex, Cursor, Gemini CLI and Antigravity. Skills are grouped into documents, development, data, marketing, communication, media, productivity, project management and security. A separate section holds automation skills for 78 SaaS apps via Composio. It includes usage instructions and a template for your own skills, Apache 2.0 license.
README badge
Original SKILL.md
--- name: artifacts-builder description: Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts. license: Complete terms in LICENSE.txt --- # Artifacts Builder To build powerful frontend claude.ai artifacts, follow these steps: 1. Initialize the frontend repo using `scripts/init-artifact.sh` 2. Develop your artifact by editing the generated code 3. Bundle all code into a single HTML file using `scripts/bundle-artifact.sh` 4. Display artifact to user 5. (Optional) Test the artifact **Stack**: React 18 + TypeScript + Vite + Parcel (bundling) + Tailwind CSS + shadcn/ui ## Design & Style Guidelines VERY IMPORTANT: To avoid what is often referred to as "AI slop", avoid using excessive centered layouts, purple gradients, uniform rounded corners, and Inter font. ## Quick Start ### Step 1: Initialize Project Run the initialization script to create a new React project: ```bash bash scripts/init-artifact.sh <project-name> cd <project-name> ``` This creates a fully configured project with: - ✅ React + TypeScript (via Vite) - ✅ Tailwind CSS 3.4.1 with shadcn/ui theming system - ✅ Path aliases (`@/`) configured - ✅ 40+ shadcn/ui components pre-installed - ✅ All Radix UI dependencies included - ✅ Parcel configured for bundling (via .parcelrc) - ✅ Node 18+ compatibility (auto-detects and pins Vite version) ### Step 2: Develop Your Artifact To build the artifact, edit the generated files. See **Common Development Tasks** below for guidance. ### Step 3: Bundle to Single HTML File To bundle the React app into a single HTML artifact: ```bash bash scripts/bundle-artifact.sh ``` This creates `bundle.html` - a self-contained artifact with all JavaScript, CSS, and dependencies inlined. This file can be directly shared in Claude conversations as an artifact. **Requirements**: Your project must have an `index.html` in the root directory. **What the script does**: - Installs bundling dependencies (parcel, @parcel/config-default, parcel-resolver-tspaths, html-inline) - Creates `.parcelrc` config with path alias support - Builds with Parcel (no source maps) - Inlines all assets into single HTML using html-inline