MoonBoi9001/agent-teams
skills/agent-teams/SKILL.md
Use when creating agent teams (or agent squads), spawning teammates, or coordinating parallel work that benefits from inter-agent communication. Applies when the user asks for a "agent team" or "agent squad", or when the task involves competing hypotheses, parallel review, cross-layer coordination, or multi-component features where agents need to discuss findings. Do not use for subagents or background agents.
$ install --global
skillsauthnpx skillsauth add MoonBoi9001/claude-code-cli-tools agent-teamsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 12:32 AM164.5s1 file scanned
SKILL.md
- name:
- agent-teams
- description:
- Use when creating agent teams (or agent squads), spawning teammates, or coordinating parallel work that benefits from inter-agent communication. Applies when the user asks for a "agent team" or "agent squad", or when the task involves competing hypotheses, parallel review, cross-layer coordination, or multi-component features where agents need to discuss findings. Do not use for subagents or background agents.
- user-invocable:
- false
Agent Teams Guide
When to Use Agent Teams
Agent teams are the right choice when teammates need to communicate with each other — sharing findings, challenging assumptions, or coordinating across components. The strongest use cases are:
- Research and review: multiple teammates investigate different aspects simultaneously, then share and challenge each other's findings
- Competing hypotheses: teammates test different theories in parallel and debate toward the answer
- Cross-layer coordination: changes spanning frontend, backend, and tests, each owned by a different teammate
- New modules or features: teammates each own a separate piece without stepping on each other
If the subtasks are independent and only the result matters, use subagents instead — they're cheaper and simpler.
Team Sizing
Start with 3-5 teammates. More than that increases coordination overhead with diminishing returns. Aim for 5-6 tasks per teammate to keep everyone productive without excessive context switching.
Teammate Context
Teammates load project context automatically (CLAUDE.md, MCP servers, skills) but do not inherit the lead's conversation history. Include task-specific details in the spawn prompt — the same principle as subagents: provide everything a brand new team member would need.
Critical Thinking
Teammates should evaluate whether the proposed approach makes logical sense before implementing. If requirements seem contradictory or counterproductive, teammates should flag concerns and explain their reasoning rather than blindly implementing.
Task Design
- Too small: coordination overhead exceeds the benefit
- Too large: teammates work too long without check-ins, increasing risk of wasted effort
- Right size: self-contained units that produce a clear deliverable — a function, a test file, a review
Break work so each teammate owns a different set of files. Two teammates editing the same file leads to overwrites.
Model Selection
Always use the latest available Opus model for teammates. Never use Sonnet or Haiku.
Plan Approval
For complex or risky tasks, require teammates to plan before implementing. The teammate works in read-only plan mode until the lead approves their approach. Give the lead criteria for approval, such as "only approve plans that include test coverage."
Cleanup
Always shut down teammates before cleaning up the team. Only the lead should run cleanup — teammates may leave resources in an inconsistent state if they attempt it.
Related Skills
MoonBoi9001/deep-review
development
VerifiedTrustedCommunity
Run a deep multi-agent review of a GitHub PR — 6 specialized agents covering architecture, correctness, security, tests, code quality, and integration. ONLY trigger when the user's message contains the explicit phrase 'deep review' (e.g. 'deep review this PR', 'deep review PR #1234', 'do a deep review of 1234', '/deep-review'). Do NOT trigger on bare 'review', 'review this', 'review the PR', 'code review', 'what do you think of this PR', or pasted PR URLs without 'deep review' in the message — those are handled by the lighter /review skill. The literal phrase 'deep review' must appear in the user's message; absence of that phrase means do not invoke this skill.
4SKILL.mdUpdated May 12, 2026
MoonBoi9001/skills/re-explain
data-ai
VerifiedTrustedCommunity
--- name: re-explain description: Re-explain a concept from the ground up when an earlier explanation didn't land. Trigger aggressively whenever the user signals confusion about recent technical content — phrases like "i don't get it", "from scratch", "ground up", "explain again", "this makes no sense", "try again", "you need to work better", "what's X" (where X was something just mentioned), or invoking /re-explain directly. Also trigger on quieter cues like the user re-quoting a phrase from th
4SKILL.mdUpdated May 5, 2026
MoonBoi9001/load-prior-session
development
VerifiedTrustedCommunity
Load a high-fidelity recap of a prior Claude Code session into the current session's context. The goal is to be LESS lossy than running /compact would be — the user is invoking this skill precisely because /compact discards detail they need. Use this when the user wants to "resume", "pick up", "continue", or "load context from" a previous session — especially a long one (hundreds of thousands of tokens) where actually resuming the session would be prohibitively expensive, or where the session was auto-compacted mid-flow and a lot of detailed work happened after the last compaction that another /compact pass would crush. Also trigger on phrases like "recap the last session", "what was I working on yesterday", "load the prior chat", or "/load-prior-session". The skill extracts via a subagent so the full transcript never enters the current session's context.
4SKILL.mdUpdated May 5, 2026
MoonBoi9001/review-todo
development
VerifiedTrustedCommunity
Convert the most recent code review in the conversation into a grouped numbered checklist (Decisions needed / Fixes / Polish) of issues to fix. Use this skill whenever the user wants to extract, list, summarize, or triage the issues a reviewer raised — including phrasings like "list the issues from that review", "make me a todo from the review", "turn the review into a checklist", "what did the review flag", "summarize that review as a list", "give me every nit from above", or "/review-todo". Trigger especially as a natural follow-up to /review, /deep-review, /security-review, /ultrareview, or any pasted PR / inline review the user wants to act on. The output is a numbered list of every concrete issue the review raised, grouped under bold section headings, with file:line references appended in parentheses, and decision items rendered with a `→` arrow callout below the description posing the specific question — and lettered choices below that when the reviewer named discrete alternatives.
4SKILL.mdUpdated Apr 30, 2026