freemcplab / Verzeichnis / Playground / Vibe-Skills

● Community foryourhealth111-pixel ⚡ Sofort

Vibe-Skills

Name: Vibe-Skills MCP Server
Author: foryourhealth111-pixel

von foryourhealth111-pixel · foryourhealth111-pixel/Vibe-Skills

A super-skill that routes between 340+ governed sub-skills with a clarify→plan→execute→verify workflow and cross-session memory.

VibeSkills is more than a collection — the VCO (Vibe Code Orchestrator) runtime routes tasks to the right sub-skill, enforces a 4-phase workflow, and maintains memory across sessions in the same workspace. It supports 3 execution grades (M/L/XL) for task complexity and coordinates parallel agents on large jobs.

▶ Demo ansehen 📦 Installieren 💡 Anwendungsfälle

Warum nutzen

Hauptfunktionen

340+ sub-skills coordinated by the VCO orchestrator
Enforced workflow: clarify → plan → execute → verify
3 execution grades (M/L/XL) matched to task complexity
Cross-session memory per workspace — picks up where you left off
Multi-agent parallelization with conflict prevention

Live-Demo

In der Praxis

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

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

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

{
  "mcpServers": {
    "vibe-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/foryourhealth111-pixel/Vibe-Skills",
        "~/.claude/skills/Vibe-Skills"
      ],
      "_inferred": true
    }
  }
}

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

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "vibe-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/foryourhealth111-pixel/Vibe-Skills",
        "~/.claude/skills/Vibe-Skills"
      ],
      "_inferred": true
    }
  }
}

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

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "vibe-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/foryourhealth111-pixel/Vibe-Skills",
        "~/.claude/skills/Vibe-Skills"
      ],
      "_inferred": true
    }
  }
}

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

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "vibe-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/foryourhealth111-pixel/Vibe-Skills",
        "~/.claude/skills/Vibe-Skills"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "vibe-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/foryourhealth111-pixel/Vibe-Skills",
          "~/.claude/skills/Vibe-Skills"
        ]
      }
    }
  }
}

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

claude mcp add vibe-skill -- git clone https://github.com/foryourhealth111-pixel/Vibe-Skills ~/.claude/skills/Vibe-Skills

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

Anwendungsfälle

Praxisnahe Nutzung: Vibe-Skills

Ship a medium-complexity feature end-to-end with governed phases

👤 Developers who want structure instead of improv ⏱ ~90 min intermediate

Wann einsetzen: A feature that touches 3+ files and a data migration — too big to yolo, not big enough for a full project.

Ablauf

State the goal

Use VibeSkills. Add role-based access to our admin panel — execution grade L.✓ Kopiert

→ VCO enters clarify phase, asks focused questions
Approve the plan

Plan looks right, execute.✓ Kopiert

→ VCO executes phases in order, verifies at each boundary
Resume later

Continue where we left off.✓ Kopiert

→ VCO restores memory and proceeds

Ergebnis: A feature shipped without the usual agent-drift.

Fallstricke

Wrong grade chosen, over/under-engineered result — Set M for quick tasks, XL only for multi-day efforts

Kombinieren mit: filesystem · github

Run parallel agents on independent parts of a large refactor

👤 Devs tackling a refactor that touches many modules ⏱ ~60 min advanced

Wann einsetzen: You have 5 modules to update with the same pattern and want them done in parallel.

Ablauf

Describe the parallel work

VibeSkills — parallelize: update each of these 5 modules to use the new auth client. Grade L.✓ Kopiert

→ VCO spawns parallel workers with conflict guards
Review the verify output

Show the verify-phase report for each worker.✓ Kopiert

→ Per-worker pass/fail with the concrete checks run

Ergebnis: Several modules updated in one session with a clean audit trail.

Fallstricke

Shared-state conflicts (e.g. same config file) — VCO serializes writes to shared files; you'll see delays on contested paths

Kombinieren mit: filesystem · git

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

vibe-skill + filesystem

VCO drives the work; filesystem MCP is the hands

VibeSkills + filesystem — scaffold the new feature structure.✓ Kopiert

vibe-skill + git

Checkpoint each phase as a git commit so you can roll back

VibeSkills — commit after each phase with a descriptive message.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen
VCO orchestrator	task + optional grade	Start of any non-trivial task
Clarify phase	task brief	Auto — first phase
Plan phase	clarified task	Auto — second phase
Execute phase	approved plan	Auto — after plan approval
Verify phase	execution results	Auto — before reporting success

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None
Tokens pro Aufruf: Higher than simple skills — the 4-phase workflow adds overhead
Kosten in €: Free — skill is local
Tipp: Use grade M for small tasks; XL burns tokens fast.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials — skill is prompts

Datenabfluss: None from the skill itself

Memory is stored per-workspace; be aware of what Claude retains across sessions.

Fehlerbehebung

Häufige Fehler und Lösungen

VCO doesn't route to expected sub-skill

Name the sub-skill explicitly: 'use VibeSkills > <sub-skill>'

Clarify phase asks too many questions

Set grade M explicitly — XL invokes deeper clarification.

Memory seems to leak between projects

Memory scopes to working directory; switch folders to switch context.

Alternativen

Vibe-Skills vs. andere

Alternative	Wann stattdessen	Kompromiss
planning-with-files-skill	You just want the 3-file persistence pattern without the full orchestrator	Simpler, less structured
skillforge	You want an intelligent skill router without the governed workflow overhead	Lighter weight

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen