Awesome Claude Skills by Composio

Install

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

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.

Example request

Create a Linear issue from this bug report and post the link to the team Slack channel

Limitations

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.

Security check

• 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

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.

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

Related