wshobson agents (Claude Skill) — Use Cases, Install & Live Demo

Name: wshobson agents (Claude Skill)
Author: wshobson

Why use it

Key features

83 specialists covering full stack
Orchestrator agent for multi-agent workflows
Each agent has clear delegation rules in its frontmatter
Tested on real customer projects
MIT licensed, easy to fork and customize

Live Demo

What it looks like in practice

ready

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "wshobson-agents-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wshobson/agents",
        "~/.claude/agents"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

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

{
  "mcpServers": {
    "wshobson-agents-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wshobson/agents",
        "~/.claude/agents"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "wshobson-agents-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wshobson/agents",
        "~/.claude/agents"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "wshobson-agents-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/wshobson/agents",
        "~/.claude/agents"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

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

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

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

Add to context_servers. Zed hot-reloads on save.

claude mcp add wshobson-agents-skill -- git clone https://github.com/wshobson/agents ~/.claude/agents

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use wshobson agents

Build a feature end-to-end with auto-routed specialists

👤 Solo devs building full-stack features ⏱ ~60 min intermediate

When to use: You want backend + frontend + tests + review without context-switching prompts.

Prerequisites

Claude Code installed — npm install -g @anthropic-ai/claude-code
Agents cloned — git clone https://github.com/wshobson/agents ~/.claude/agents

Flow

Kick off with orchestrator

Use orchestrator-agent. Build a CRUD feature for 'invoices' — backend (FastAPI), frontend (Next.js), tests, review.✓ Copied

→ Plan with subtasks routed to specialist agents
Watch each handoff

Show me each agent's contribution as it goes. Pause for my approval after backend before frontend starts.✓ Copied

→ Per-agent diff with checkpoints
Final security pass

Run security-auditor on the diff. Anything risky?✓ Copied

→ Security report with findings

Outcome: Full-stack feature shipped with appropriate specialists per layer.

Pitfalls

Orchestrator over-delegates trivial tasks — Override with --no-orchestrator for simple changes

Combine with: desktop-commander-mcp

Run a code review with the dedicated code-reviewer agent

👤 Anyone who wants more than 'looks good' on their PR ⏱ ~20 min beginner

When to use: You want a thorough review that doesn't just rubber-stamp.

Flow

Stage the diff

Run code-reviewer on the current branch's diff vs main. Group findings by severity.✓ Copied

→ Sev-1/2/3 grouped findings
Apply fixes

Apply the sev-1 findings now. Park sev-2/3 for later.✓ Copied

→ Diff updated; suggestions tracked

Outcome: Higher signal review than 'lgtm'.

Combine with: wshobson-commands-skill

Invoke a specific specialist directly without orchestration

👤 Devs who know exactly which expertise they need ⏱ ~30 min intermediate

When to use: Targeted task; no need for plan-and-route.

Flow

Pick the agent

Use database-architect agent. Design a schema for multi-tenant orders with audit trail.✓ Copied

→ Schema with rationale
Iterate with same agent

Stay in database-architect. Now add a hot/cold partition strategy for 100M rows.✓ Copied

→ Refined design

Outcome: Domain-specific output without orchestrator overhead.

Combinations

Pair with other MCPs for X10 leverage

wshobson-agents-skill + wshobson-commands-skill

Slash commands trigger specific agents fast

/review triggers code-reviewer; /audit triggers security-auditor.✓ Copied

wshobson-agents-skill + desktop-commander-mcp

Agents plan, desktop-commander executes

Backend-architect plans; desktop-commander writes the files.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
orchestrator-agent	high-level goal	Multi-domain features	Coordinator overhead — multi-step
backend-architect	service spec	Backend decisions	0
frontend-developer	ui spec	UI work	0
code-reviewer	diff	Pre-merge gate	0
security-auditor	diff or code	Risky changes	0

Cost & Limits

What this costs to run

API quota: N/A — local skill
Tokens per call: High in orchestrator mode (multi-agent coordination)
Monetary: Free (MIT)
Tip: Skip orchestrator for single-domain tasks; call specialist directly

Security

Permissions, secrets, blast radius

Minimum scopes: filesystem-read

Credential storage: None — pure prompts

Data egress: None (skill is local files)

Agents will execute whatever tools you grant Claude Code; tighten Claude's permissions, not the skill

Troubleshooting

Common errors and fixes

Agent not found

Make sure files are in ~/.claude/agents/ with .md extension and proper frontmatter

Verify: claude --list-agents

Orchestrator loops forever

Add explicit termination criteria to your prompt; orchestrator obeys 'stop when X'

Wrong specialist routed

Check frontmatter description fields — orchestrator routes by description match

Alternatives

wshobson agents vs others

Alternative	When to use it instead	Tradeoff
wshobson/skills (sibling)	You want skills (Anthropic skill format) not subagents	Different format; same author
obra/superpowers	Curated multi-skill bundle with different opinions	Smaller, more opinionated

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills