/ Directory / Playground / metaskill
← All servers ↗ GitHub
● Community xvirobotics ⚡ Instant

metaskill

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

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Live Demo

What it looks like in practice

metaskill-skill.replay ▶ ready
0/0

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use metaskill

Bootstrap an AI agent team for a fullstack project

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

When to use: Starting a new project and you'd like proper agent separation instead of one overloaded Claude.

Flow
  1. Describe the project
    /metaskill fullstack web app with React, TanStack, Postgres, Stripe subscriptions.✓ Copied
    → 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.✓ Copied
    → Clear per-agent responsibility with no overlap
  3. Provide credentials (optional)
    Skip credentials for now — I'll add them later.✓ Copied
    → Skill proceeds to verification without blocking

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

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

When to use: You need a 'security reviewer' agent but already have everything else.

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

Outcome: 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

When to use: You keep running the same deploy steps manually and want a skill for it.

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

Outcome: A reusable skill you can install right away.

Combine with: skillcheck-free-skill

Combinations

Pair with other MCPs for X10 leverage

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.✓ Copied
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.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
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

Cost & Limits

What this costs to run

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

Security

Permissions, secrets, blast radius

Credential storage: No credentials in the skill itself. Credentials phase asks for your API keys if you opt-in.
Data egress: Research phase performs web searches

Troubleshooting

Common errors and fixes

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 others

AlternativeWhen to use it insteadTradeoff
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

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills

Continue exploring

Related tools and workflows

Choose another guide for your workflow, or explore a collection.

Shared context · team

Wegent

Skill

Shared context · team

Expo Skills

Build, deploy, upgrade, and debug Expo applications with official Expo team guidance.

Skill

Browse all topic collections → · See 29 new official additions →