freemcplab / Directorio / Playground / Vibe-Skills

● Comunidad foryourhealth111-pixel ⚡ Instantáneo

Vibe-Skills

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

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

▶ Ver demo 📦 Instalar 💡 Casos de uso

Por qué usarlo

Características clave

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

Demo en vivo

Cómo se ve en la práctica

vibe-skill.replay ▶ listo

0/0

Instalar

Elige tu cliente

~/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
    }
  }
}

Abre Claude Desktop → Settings → Developer → Edit Config. Reinicia después de guardar.

~/.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 usa el mismo esquema mcpServers que Claude Desktop. La configuración del proyecto prevalece sobre la global.

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

Haz clic en el icono MCP Servers de la barra lateral de Cline y luego en "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
    }
  }
}

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

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

Continue usa un array de objetos de servidor en lugar de un mapa.

~/.config/zed/settings.json

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

Añádelo a context_servers. Zed recarga en caliente al guardar.

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

Un solo comando. Verifica con claude mcp list. Quita con claude mcp remove.

Casos de uso

Usos del mundo real: Vibe-Skills

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

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

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

Flujo

State the goal

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

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

Plan looks right, execute.✓ Copiado

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

Continue where we left off.✓ Copiado

→ VCO restores memory and proceeds

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

Errores comunes

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

Combinar con: filesystem · github

Run parallel agents on independent parts of a large refactor

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

Cuándo usarlo: You have 5 modules to update with the same pattern and want them done in parallel.

Flujo

Describe the parallel work

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

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

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

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

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

Errores comunes

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

Combinar con: filesystem · git

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

vibe-skill + filesystem

VCO drives the work; filesystem MCP is the hands

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

vibe-skill + git

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

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

Herramientas

Lo que expone este MCP

Herramienta	Entradas	Cuándo llamar
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

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API: None
Tokens por llamada: Higher than simple skills — the 4-phase workflow adds overhead
Monetario: Free — skill is local
Consejo: Use grade M for small tasks; XL burns tokens fast.

Seguridad

Permisos, secretos, alcance

Almacenamiento de credenciales: No credentials — skill is prompts

Salida de datos: None from the skill itself

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

Resolución de problemas

Errores comunes y soluciones

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.

Alternativas

Vibe-Skills vs otros

Alternativa	Cuándo usarla	Contrapartida
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

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills