Form a committee of two high-reasoning agents to step back, do root cause analysis, and produce a plan. Use when stuck, looping, tunnel-visioning, or facing a hard planning problem.
64
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/paseo-committee/SKILL.mdTwo agents from contrasting profiles, fresh context, planning a solution in parallel.
User's additional context: $ARGUMENTS
Read the paseo skill. Call list_profiles before choosing committee members. Do not create committee agents until you have read the configured profiles and their notes.
Contrast is the point of a committee, so pick profiles from different provider families when possible. Materialize each profile into create_agent.
Two members with different reasoning styles, selected from configured Agent profiles:
If the user names profiles, use those. If fewer than two suitable profiles are configured, use Paseo's provider discovery fallback for the missing member and tell the user. Override the selection only when the user explicitly asks for different members.
No edits. Every prompt to a committee member ends with the no-edits suffix:
This is analysis only. Do NOT edit, create, or delete any files. Do NOT write code.Trust the finish notification. Do not poll, send hurry-ups, or interrupt. Models can reason for 15–30 minutes. You can go idle and Paseo will notify you.
[Committee] <task> titles and the same promptShare the consensus with the user. Summarize where the agents diverged and how they resolved it.
8533c5c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.