freemcplab / Annuaire / Playground / Vibe-Skills

● Communauté foryourhealth111-pixel ⚡ Instantané

Vibe-Skills

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

par 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.

▶ Voir la démo 📦 Installer 💡 Cas d'usage

Pourquoi l'utiliser

Fonctionnalités clés

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

Démo en direct

Aperçu en pratique

vibe-skill.replay ▶ prêt

0/0

Installer

Choisissez votre 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
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.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 utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la 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
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "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
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

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

Continue utilise un tableau d'objets serveur plutôt qu'une 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"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : Vibe-Skills

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

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

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

Déroulement

State the goal

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

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

Plan looks right, execute.✓ Copié

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

Continue where we left off.✓ Copié

→ VCO restores memory and proceeds

Résultat : A feature shipped without the usual agent-drift.

Pièges

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

Combiner avec : filesystem · github

Run parallel agents on independent parts of a large refactor

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

Quand l'utiliser : You have 5 modules to update with the same pattern and want them done in parallel.

Déroulement

Describe the parallel work

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

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

Show the verify-phase report for each worker.✓ Copié

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

Résultat : Several modules updated in one session with a clean audit trail.

Pièges

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

Combiner avec : filesystem · git

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

vibe-skill + filesystem

VCO drives the work; filesystem MCP is the hands

VibeSkills + filesystem — scaffold the new feature structure.✓ Copié

vibe-skill + git

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

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

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler
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

Coût et limites

Coût d'exécution

Quota d'API: None
Tokens par appel: Higher than simple skills — the 4-phase workflow adds overhead
Monétaire: Free — skill is local
Astuce: Use grade M for small tasks; XL burns tokens fast.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : No credentials — skill is prompts

Sortie de données : None from the skill itself

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

Dépannage

Erreurs courantes et correctifs

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.

Alternatives

Vibe-Skills vs autres

Alternative	Quand l'utiliser	Compromis
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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills