claude-skills MCP — Use Cases, Install & Live Demo

Why use it

Key features

Cloudflare Workers / D1 / R2 / Pages scaffolding
React 19 idioms (Server Components where applicable)
Tailwind v4 config + design tokens
AI integration adapters (multi-provider)
Production-ready — not tutorial sketches

Live Demo

What it looks like in practice

claude-skill-5.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "claude-skill-5": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/secondsky/claude-skills",
        "~/.claude/skills/claude-skills"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "claude-skill-5": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/secondsky/claude-skills",
        "~/.claude/skills/claude-skills"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "claude-skill-5": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/secondsky/claude-skills",
        "~/.claude/skills/claude-skills"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "claude-skill-5": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/secondsky/claude-skills",
        "~/.claude/skills/claude-skills"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "claude-skill-5",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/secondsky/claude-skills",
        "~/.claude/skills/claude-skills"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "claude-skill-5": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/secondsky/claude-skills",
          "~/.claude/skills/claude-skills"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add claude-skill-5 -- git clone https://github.com/secondsky/claude-skills ~/.claude/skills/claude-skills

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use claude-skills

Ship a new Cloudflare-hosted React app in one session

👤 Devs building on the CF stack ⏱ ~60 min intermediate

When to use: You want Workers + Pages + D1 wired up without reading 5 Cloudflare docs.

Prerequisites

Cloudflare account + wrangler — npm i -g wrangler; wrangler login
Skill installed — git clone https://github.com/secondsky/claude-skills ~/.claude/skills/claude-skills

Flow

Scaffold

Use claude-skills. Scaffold a React 19 + Tailwind v4 app deployed to Cloudflare Pages with a Workers API and D1 DB.✓ Copied

→ Monorepo structure with apps/web, apps/api (Worker), wrangler.toml
Add a feature

Add a 'notes' feature — D1 schema, CRUD Worker endpoints, React UI with Tailwind v4 styling.✓ Copied

→ Migration + Worker + React page
Deploy

Deploy to Cloudflare.✓ Copied

→ wrangler deploy output; URLs returned

Outcome: Live URL within an hour.

Pitfalls

Wrangler config drift between environments — Use wrangler environments from the start — dev/staging/prod sections

Combine with: cloudflare · cloudflare-api

Migrate a Tailwind v3 project to v4

👤 Teams on v3 hitting the v4 release ⏱ ~45 min intermediate

When to use: You want the new engine + CSS-first config without breaking everything.

Flow

Audit current

Use claude-skills. Audit my tailwind.config.js for v4 breaking changes.✓ Copied

→ Change list with severity
Migrate config

Convert to v4 CSS-first config with @theme directives.✓ Copied

→ New globals.css with @theme block
Fix utilities

Find v3 utilities that changed or were removed; rewrite usage.✓ Copied

→ Grep + rewrite pass

Outcome: Project on v4 without visual regressions.

Pitfalls

Plugin ecosystem not v4-ready yet — Check each plugin's v4 status; stay on v3 if a critical one lags

Combine with: filesystem

Wrap multiple AI providers behind one adapter

👤 Devs who want to swap Claude / GPT / local models without rewriting ⏱ ~45 min advanced

When to use: Locking into one provider feels wrong and you want a clean interface.

Flow

Define interface

Use claude-skills ai-adapter pattern. Define a TS interface that abstracts chat completion across Claude, OpenAI, and a local model.✓ Copied

→ Interface + 3 implementations
Wire up streaming

Add SSE streaming support to the adapter.✓ Copied

→ Streaming implementation consistent across providers

Outcome: A swappable AI layer.

Pitfalls

Over-abstracting and losing provider-specific features — Keep a provider-specific escape hatch alongside the shared interface

Combinations

Pair with other MCPs for X10 leverage

claude-skill-5 + cloudflare

Deploy + manage the CF resources the scaffold creates

After scaffold, use cloudflare MCP to verify DNS and tail Worker logs.✓ Copied

claude-skill-5 + cloudflare-api

Bulk CF config operations

Configure cache rules and WAF for the deployed Pages project.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call
cf_scaffold	app type, features	New CF app
tailwind_migrate	v3 config	Tailwind upgrade
ai_adapter_scaffold	providers list	Multi-provider AI setup

Cost & Limits

What this costs to run

API quota: None in skill
Tokens per call: Moderate
Monetary: Cloudflare has a generous free tier; paid features as you grow
Tip: Use wrangler dev locally; reserve cloud deploys for staging/prod.

Security

Permissions, secrets, blast radius

Credential storage: Wrangler handles CF auth; AI provider keys via env / CF secrets

Data egress: CF, AI providers you configure

Use CF secrets (wrangler secret put) for API keys, never commit .dev.vars.

Troubleshooting

Common errors and fixes

D1 migration fails

Wrangler D1 migrations are finicky; run with --local first and inspect the SQL

Verify: wrangler d1 migrations list <db>

Tailwind v4 styles not applying

Check the @source directive captures your content paths

Deploy succeeds but Worker returns 500

wrangler tail to see the actual error

Verify: wrangler tail <worker>

Alternatives

claude-skills vs others

Alternative	When to use it instead	Tradeoff
Vercel / Next.js stack	You prefer Next ecosystem	Different deployment model, pricing
cc-frontend-skill	You care most about visual identity	Not stack-specific

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills