metaskill MCP — Casos de uso, Instalar & Demo en vivo

Por qué usarlo

Características clave

/metaskill single command — no manual role design
Research phase runs live web searches so output reflects current ecosystem
Generates routing doc, agents, skills, standards, and MCP config in one pass
Three intent modes: full team / single agent / single skill
Default architecture uses Opus tech-lead + Sonnet specialists with review gates

Demo en vivo

Cómo se ve en la práctica

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

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

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

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

Mismo formato que Claude Desktop. Reinicia Windsurf para aplicar.

~/.continue/config.json

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

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

~/.config/zed/settings.json

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

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

claude mcp add metaskill-skill -- git clone https://github.com/xvirobotics/metaskill ~/.claude/skills/metaskill

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

Casos de uso

Usos del mundo real: metaskill

Bootstrap an AI agent team for a fullstack project

👤 Founders and solo devs who want structured multi-agent setups ⏱ ~20 min beginner

Cuándo usarlo: Starting a new project and you'd like proper agent separation instead of one overloaded Claude.

Requisitos previos

Skill cloned — git clone https://github.com/xvirobotics/metaskill ~/.claude/skills/metaskill

Flujo

Describe the project

/metaskill fullstack web app with React, TanStack, Postgres, Stripe subscriptions.✓ Copiado

→ Research phase runs web searches; then build phase produces routing + agents + skills
Review the generated team

Walk me through each agent's scope and the routing rules between them.✓ Copiado

→ Clear per-agent responsibility with no overlap
Provide credentials (optional)

Skip credentials for now — I'll add them later.✓ Copiado

→ Skill proceeds to verification without blocking

Resultado: A working multi-agent setup you can start using immediately.

Errores comunes

Generated team has too many roles for a 1-person project — Use the single-agent mode instead ('create a single agent for X')

Combinar con: github · filesystem

Create one specialized agent for an existing workflow

👤 Devs who already have a project and want to add one role ⏱ ~10 min beginner

Cuándo usarlo: You need a 'security reviewer' agent but already have everything else.

Flujo

Invoke single-agent mode

/metaskill — a single security reviewer agent for a Node.js API.✓ Copiado

→ Targeted agent file with scope, not a full team

Resultado: One focused agent integrated into your existing setup.

Generate a single deploy skill without building a whole team

👤 Devs formalizing a workflow ⏱ ~15 min beginner

Cuándo usarlo: You keep running the same deploy steps manually and want a skill for it.

Flujo

Invoke single-skill mode

/metaskill — a deploy-to-staging skill for Cloudflare Workers with rollback on health-check failure.✓ Copiado

→ SKILL.md with triggers and steps

Resultado: A reusable skill you can install right away.

Combinar con: skillcheck-free-skill

Combinaciones

Combínalo con otros MCPs para multiplicar por 10

metaskill-skill + skillcheck-free-skill

Validate Metaskill's generated SKILL.md files against the agentskills spec before using them

After /metaskill, run SkillCheck on every generated SKILL.md.✓ Copiado

metaskill-skill + github

Commit the generated team structure as a first PR to seed your repo

After generation, commit .claude/ and agent docs in a single 'seed' PR.✓ Copiado

Herramientas

Lo que expone este MCP

Herramienta	Entradas	Cuándo llamar	Coste
generate_team	project description	Fresh project	0 + web search tokens
generate_single_agent	role description	Existing team, need one more role	0
generate_single_skill	workflow description	Formalizing a repeated workflow	0
verify	generated files	Auto-run after generation	0

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API: Uses web search during research phase
Tokens por llamada: High for team generation (research + build); lower for single-agent/skill modes
Monetario: Free — skills are local files. Web search may count against your own MCP's quotas.
Consejo: Use single-agent mode when you don't need a full team; it's much cheaper.

Seguridad

Permisos, secretos, alcance

Almacenamiento de credenciales: No credentials in the skill itself. Credentials phase asks for your API keys if you opt-in.

Salida de datos: Research phase performs web searches

Generated agents are suggestions — review them before granting them MCP tool access.

Resolución de problemas

Errores comunes y soluciones

Skill not invoked — Claude sets up agents manually

Use '/metaskill' as a literal trigger.

Verificar: ls ~/.claude/skills/metaskill/SKILL.md

SKILL.md frontmatter wrong

Re-clone; description drives activation.

Verificar: head ~/.claude/skills/metaskill/SKILL.md

Wrong trigger keywords — generates a skill when you wanted a team

Phrase the project description clearly; 'fullstack web app' triggers team mode, 'a skill for X' triggers skill mode.

Alternativas

metaskill vs otros

Alternativa	Cuándo usarla	Contrapartida
Manual agent design	You have strong opinions about role structure	More control, much slower
rootnode-skill	You want Project-level engineering rather than agent-team generation	Different axis — Claude Projects vs Claude Code multi-agent

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills