marketplace MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

Security-audited skill inventory
One-click install via CLI
Signed skill manifests (known publisher)
Permission declarations up front
Compatibility badges: Claude, Codex, Claude Code
Update/rollback support

Live-Demo

In der Praxis

marketplace-skill.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": {
    "marketplace-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/aiskillstore/marketplace",
        "~/.claude/skills/marketplace"
      ],
      "_inferred": true
    }
  }
}

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

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

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

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

VS Code → Cline → MCP Servers → Edit

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

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

~/.codeium/windsurf/mcp_config.json

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

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

~/.continue/config.json

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

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

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

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

claude mcp add marketplace-skill -- git clone https://github.com/aiskillstore/marketplace ~/.claude/skills/marketplace

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

Anwendungsfälle

Praxisnahe Nutzung: marketplace

How to install a vetted skill instead of a random GitHub repo

👤 Enterprise and regulated users who can't install arbitrary code ⏱ ~10 min beginner

Wann einsetzen: Your org requires reviewed dependencies and you want skills without going through procurement each time.

Voraussetzungen

Marketplace installed — git clone https://github.com/aiskillstore/marketplace ~/.claude/skills/marketplace

Ablauf

Browse catalog

List marketplace skills for GA4/analytics use cases.✓ Kopiert

→ Catalog subset with audit status + permissions
Inspect permissions

Show me what permissions the 'ga4-setup' skill requests and what it sends externally.✓ Kopiert

→ Explicit permission + egress disclosure
Install

Install ga4-setup from marketplace.✓ Kopiert

→ Skill added to ~/.claude/skills with manifest

Ergebnis: A reviewed skill installed without audit overhead.

Fallstricke

Audit status ages with updates — Check manifest timestamp; re-review if >90 days since last audit

Migrate from random git clones to marketplace equivalents

👤 Teams cleaning up ~/.claude/skills after months of accretion ⏱ ~30 min intermediate

Wann einsetzen: Your skills folder has 20+ repos, nobody remembers why half of them are installed.

Ablauf

Inventory

List every skill in ~/.claude/skills and check if a marketplace equivalent exists.✓ Kopiert

→ Per-skill: keep, migrate, drop
Migrate

Replace matched skills with marketplace versions. Preserve any local config overrides.✓ Kopiert

→ Backups + fresh installs

Ergebnis: A reviewable skills folder with known provenance.

Publish your own skill to the marketplace

👤 Skill authors wanting wider distribution with the audit badge ⏱ ~60 min intermediate

Wann einsetzen: You built a skill and want the credibility of a vetted store listing.

Voraussetzungen

Working skill with clean SKILL.md — Use claude-code-skill-factory-skill /validate-output first

Ablauf

Prepare listing

Prepare a marketplace listing for my skill: description, permissions, egress list, screenshots.✓ Kopiert

→ Listing draft following marketplace conventions
Submit for audit

Open a PR to aiskillstore/marketplace with the listing.✓ Kopiert

→ PR opened; audit checklist surfaces

Ergebnis: Skill submitted with a clean audit checklist.

Kombinieren mit: claude-code-skill-factory-skill

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

marketplace-skill + agent-skills-cli-skill

Use the CLI for install + marketplace for curation

Browse marketplace to find a vetted SEO skill, then install with agent-skills-cli.✓ Kopiert

marketplace-skill + claude-code-skill-factory-skill

Build with Factory, publish to marketplace

/build my skill with Factory, then publish to marketplace with the publish flow.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen
Catalog browse	query?	Finding a vetted skill
Permission inspect	skill_name	Before install
Install	skill_name	After inspection
Migrate	local_path	Cleaning up accretion
Publish	skill_path, listing	Submitting new skills

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None
Tokens pro Aufruf: 0 at marketplace level; depends on each skill
Kosten in €: Free
Tipp: Prefer marketplace installs over raw clones to cut audit overhead.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials at marketplace level

Datenabfluss: Marketplace itself doesn't egress; each listed skill declares its own egress

Audit ≠ zero risk. Still review each skill's declared egress and permissions before enabling for sensitive work.

Fehlerbehebung

Häufige Fehler und Lösungen

Skill install fails signature check

Update marketplace clone; signing keys may have rotated

Prüfen: git -C ~/.claude/skills/marketplace pull

A marketplace skill behaves differently from raw upstream

Marketplace sometimes pins older versions for audit stability; check manifest for pinned commit

Alternativen

marketplace vs. andere

Alternative	Wann stattdessen	Kompromiss
agent-skills-cli-skill	You want a larger, less-curated catalog	Less audit, more options
awesome-llm-skill	You want community breadth	Quality varies widely

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen