External Skills Catalog

Document & Content

Development & Code

Security & Compliance

Data & Analytics

Marketing & Growth

Creative & Design

Project Management

Platform & Infrastructure

Install Instructions

Claude Code (CLI)

# MCP-based skills: add to ~/.claude/mcp.json or project .mcp.json
{
  "mcpServers": {
    "skill-name": {
      "command": "npx",
      "args": ["-y", "@package/mcp-server"]
    }
  }
}

# Prompt-based skills: add to ~/.claude/commands/ or project .claude/commands/
mkdir -p .claude/commands
echo "skill content here" > .claude/commands/skill-name.md

Claude.ai (Web)

MCP skills can be added via Settings > Integrations > MCP Servers.

Fallback Strategy

When the needed skill doesn't exist:

Step 1: WORKAROUND
  → Can an existing vibecosystem skill handle it partially?
  → Example: No "email" skill? Use copywriter agent + manual send

Step 2: COMBO
  → Can 2+ existing skills combine to solve it?
  → Example: No "API mock" skill? Use mocksmith + backend-dev

Step 3: CREATE
  → Is it worth creating a new internal skill?
  → Use /skill-create to generate from session patterns

Step 4: EXTERNAL
  → Search this catalog for a community skill
  → Check: https://github.com/topics/claude-code
  → Check: https://github.com/topics/mcp-server
  → Web search: "claude code [capability] skill 2026"

Discovering New Skills

The external ecosystem grows fast. When this catalog doesn't have what you need:

1. Search GitHub: claude code skill [keyword] or mcp server [keyword]
2. Check MCP server directories for new integrations
3. Look at Claude Code community discussions
4. Consider building and contributing your own

Tips

• Always verify external skills before recommending (check repo activity, stars, last commit)
• Prefer MCP-based skills for deeper integration
• Prompt-based skills are easier to install but less powerful
• When recommending, include the install command so the user can act immediately
• If a skill has known issues, mention them upfront