/ Annuaire / Playground / metaskill
← Tous les serveurs ↗ GitHub
● Communauté xvirobotics ⚡ Instantané

metaskill

par xvirobotics · xvirobotics/metaskill

/metaskill command that researches your domain, then builds a 4-6 agent team with routing docs, skills, coding standards, and MCP config.

xvirobotics/metaskill is a Claude Code skill that generates AI agent teams from one prompt. Four phases: Research (web searches on industry team structures, existing agents, MCPs, best practices) → Build (routing docs, 4-6 specialized agents, 2-4 skills, coding standards, MCP config) → Credentials (optional API key collection) → Verify. Detects intent to route between team generation, single-agent creation, and single-skill creation. Default output: tech-lead (Opus) + specialists (Sonnet) across frontend/backend/testing/design with mandatory code review gates.

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

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

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

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

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

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "metaskill-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/xvirobotics/metaskill",
        "~/.claude/skills/metaskill"
      ],
      "_inferred": true
    }
  }
}

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

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

Continue utilise un tableau d'objets serveur plutôt qu'une map.

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

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

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

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

Cas d'usage

Usages concrets : metaskill

Bootstrap an AI agent team for a fullstack project

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

Quand l'utiliser : Starting a new project and you'd like proper agent separation instead of one overloaded Claude.

Prérequis
  • Skill cloned — git clone https://github.com/xvirobotics/metaskill ~/.claude/skills/metaskill
Déroulement
  1. Describe the project
    /metaskill fullstack web app with React, TanStack, Postgres, Stripe subscriptions.✓ Copié
    → Research phase runs web searches; then build phase produces routing + agents + skills
  2. Review the generated team
    Walk me through each agent's scope and the routing rules between them.✓ Copié
    → Clear per-agent responsibility with no overlap
  3. Provide credentials (optional)
    Skip credentials for now — I'll add them later.✓ Copié
    → Skill proceeds to verification without blocking

Résultat : A working multi-agent setup you can start using immediately.

Pièges
  • Generated team has too many roles for a 1-person project — Use the single-agent mode instead ('create a single agent for X')
Combiner avec : 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

Quand l'utiliser : You need a 'security reviewer' agent but already have everything else.

Déroulement
  1. Invoke single-agent mode
    /metaskill — a single security reviewer agent for a Node.js API.✓ Copié
    → Targeted agent file with scope, not a full team

Résultat : 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

Quand l'utiliser : You keep running the same deploy steps manually and want a skill for it.

Déroulement
  1. Invoke single-skill mode
    /metaskill — a deploy-to-staging skill for Cloudflare Workers with rollback on health-check failure.✓ Copié
    → SKILL.md with triggers and steps

Résultat : A reusable skill you can install right away.

Combiner avec : skillcheck-free-skill

Combinaisons

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

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.✓ Copié
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.✓ Copié

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
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

Coût et limites

Coût d'exécution

Quota d'API
Uses web search during research phase
Tokens par appel
High for team generation (research + build); lower for single-agent/skill modes
Monétaire
Free — skills are local files. Web search may count against your own MCP's quotas.
Astuce
Use single-agent mode when you don't need a full team; it's much cheaper.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : No credentials in the skill itself. Credentials phase asks for your API keys if you opt-in.
Sortie de données : Research phase performs web searches

Dépannage

Erreurs courantes et correctifs

Skill not invoked — Claude sets up agents manually

Use '/metaskill' as a literal trigger.

Vérifier : ls ~/.claude/skills/metaskill/SKILL.md
SKILL.md frontmatter wrong

Re-clone; description drives activation.

Vérifier : 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.

Alternatives

metaskill vs autres

AlternativeQuand l'utiliserCompromis
Manual agent designYou have strong opinions about role structureMore control, much slower
rootnode-skillYou want Project-level engineering rather than agent-team generationDifferent axis — Claude Projects vs Claude Code multi-agent

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills