Results for “team-analysis”

Browse available agent personas and compose ad-hoc teams of up to 5 agents to work in parallel on a task, then synthesize their results.

Decompose a task into parallel workstreams, assign agent ownership, run integration at dependency boundaries, and synthesize results.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Benchmarks language model agents on the C2C multi-agent negotiation task, reporting win rate across starting positions.

Use this skill for reproduction-first debugging, root cause isolation, minimal fixes, regression tests. Trigger when the task involves agent profile work related to Staff Debugger Agent, implementation, audits, debugging, strategy, or validation.

Use when work requires inter-agent communication, cross-layer coordination, or configurable autonomy with Claude Code Agent Teams

Designing red team attack scenarios, threat models, MITRE ATT&CK/OWASP application, Purple Team exercises, and AI/LLM red teaming. Use when adversarial security validation is needed.

Run three agents as a newsroom — a Writer, an Editor, and a Fact-checker — that draft, critique, and verify in parallel and argue until the writing survives with zero flags. This is the level above a single self-review loop, for the pieces that matter most. Best run in Claude Cowork against the user's files. Use for high-stakes writing the user wants bulletproof: a newsletter, a launch post, a client email, a public announcement. Trigger whenever the user says 'run the team', 'use the swarm', 'writer editor fact-checker', 'spawn agents to work on this', or wants the strongest possible version of a piece. For a lighter single-agent loop, use red-pen instead.

Defines an inter-agent communication protocol for C-suite agent teams, including invocation syntax, loop prevention, isolation rules, and response formats to coordinate cross-functional analysis and board meetings.

Expert startup business analyst specializing in market sizing, financial modeling, competitive analysis, and strategic planning for early-stage companies. Use PROACTIVELY when the user asks about market opportunity, TAM/SAM/SOM, financial projections, unit economics, competitive landscape, team planning, startup metrics, or business strategy for pre-seed through Series A startups.

Use to analyse average handle time, resolution time or time-in-queue without being misled by the skew, and to find where time actually goes. Trigger for "why is our AHT increasing", "our call handling times are up", "which contact reasons take longest", "how long do tickets take", handle time by agent or team, or an AHT target being set.