claude-skills MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

Cloudflare: Workers, D1, R2, KV, Pages, Durable Objects patterns
React (RSC, Server Actions, suspense idioms)
Tailwind v4 migration + new config shape
AI integrations: OpenAI/Anthropic SDK patterns, embeddings, vector search
Opinionated defaults — biased toward simpler choices

Live-Demo

In der Praxis

claude-skill-3.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren Client

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

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

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

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

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

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

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

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

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

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

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

In context_servers hinzufügen. Zed lädt beim Speichern neu.

claude mcp add claude-skill-3 -- git clone https://github.com/jezweb/claude-skills ~/.claude/skills/claude-skills

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: claude-skills

How to ship a Cloudflare Worker API with D1 backing

👤 Full-stack devs wanting a Worker+D1 API without boilerplate ⏱ ~45 min intermediate

Wann einsetzen: You want a small JSON API with auth and persistence, deployed to Cloudflare.

Voraussetzungen

Skill installed — git clone https://github.com/jezweb/claude-skills ~/.claude/skills/jezweb-skills
wrangler CLI — npm i -g wrangler && wrangler login

Ablauf

Scaffold

Use the Cloudflare skill. New Worker with D1 binding, Hono router, routes: GET /todos, POST /todos, DELETE /todos/:id.✓ Kopiert

→ Worker code + wrangler.toml + schema.sql
Auth

Add bearer token auth using a secret in env.✓ Kopiert

→ Middleware + wrangler secret put instructions
Deploy

wrangler d1 execute + wrangler deploy steps.✓ Kopiert

→ Live URL after deploy

Ergebnis: A deployed Worker API with D1 persistence.

Fallstricke

D1 migrations drift between envs — Use wrangler d1 migrations create + apply; don't ad-hoc exec

Upgrade a Tailwind v3 project to v4

👤 Frontend devs on v3 wanting to move to v4's new engine ⏱ ~60 min intermediate

Wann einsetzen: You're on tailwind@3 and want to adopt v4's Oxide engine + CSS-first config.

Ablauf

Audit current config

Audit tailwind.config.{js,ts} for anything that doesn't port 1:1 to v4.✓ Kopiert

→ Per-config-key migration notes
Generate v4 config

Produce the v4 equivalent: @theme in a CSS entry + package updates.✓ Kopiert

→ CSS entry + package.json diff
Fix breaking utilities

Grep the codebase for removed/renamed utility classes and produce a replace map.✓ Kopiert

→ Codemod suggestions

Ergebnis: A v4 migration PR ready for review.

Fallstricke

PostCSS pipeline conflicts with v4's native engine — Remove PostCSS plugins that v4's engine replaces

Build a lightweight RAG endpoint on Workers

👤 Devs adding AI features to a Cloudflare app ⏱ ~90 min advanced

Wann einsetzen: You want RAG without standing up a vector DB service.

Ablauf

Set up Vectorize

Provision a Vectorize index for embeddings. Use OpenAI text-embedding-3-small.✓ Kopiert

→ wrangler vectorize create + binding
Ingest script

Write a Worker route /ingest that chunks + embeds + upserts.✓ Kopiert

→ Worker code with chunking heuristic
Query route

Write /query that embeds the question, retrieves top-k, and calls Claude/OpenAI with the context.✓ Kopiert

→ End-to-end route

Ergebnis: A small but real RAG endpoint deployed on Cloudflare.

Fallstricke

Chunks too large lose recall; too small hurt context — Start 512 tokens, overlap 64; tune based on your corpus

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

claude-skill-3 + claude-code-owasp-skill

Security-review Worker auth and RAG endpoints

After scaffolding the Worker with auth, run OWASP review on the auth middleware.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
Cloudflare Worker scaffolding	-	New worker projects	Claude tokens
D1 + R2 + KV patterns	-	Persistence wiring	Claude tokens
React RSC patterns	-	RSC-era apps	Claude tokens
Tailwind v4 migration	-	v3→v4 upgrades	Claude tokens
AI integrations	-	OpenAI/Anthropic/embeddings	Claude tokens

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None at skill level
Tokens pro Aufruf: 5-20k per task
Kosten in €: Free skill; Cloudflare + OpenAI/Anthropic have their own pricing
Tipp: Cloudflare free tier covers small Worker APIs; watch Vectorize cost at scale.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials at skill level. Wrangler handles CF secrets.

Datenabfluss: Deploys go to Cloudflare; any AI calls go to the configured provider

Wrangler auth has full account access. Use scoped API tokens for CI, not wrangler login.

Fehlerbehebung

Häufige Fehler und Lösungen

wrangler deploy fails on route

Route patterns require the zone to be in your CF account; check routes vs. workers.dev fallback

Prüfen: wrangler deployments list

D1 migrations apply locally but not remote

Run wrangler d1 migrations apply <DB> --remote explicitly

Alternativen

claude-skills vs. andere

Alternative	Wann stattdessen	Kompromiss
Vercel + Next.js template	You prefer Vercel's DX	Different pricing and platform capabilities

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen