Paseo Committee
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.
mkdir -p ~/.claude/skills/paseo-committee && curl -fsSL 'https://raw.githubusercontent.com/getpaseo/paseo/main/skills/paseo-committee/SKILL.md' -o ~/.claude/skills/paseo-committee/SKILL.md
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Paseo Committee when an AI agent needs a reusable SKILL.md workflow for this job: 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.
When not to use it
Skip Paseo Committee when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/paseo-committee && curl -fsSL 'https://raw.githubusercontent.com/getpaseo/paseo/main/skills/paseo-committee/SKILL.md' -o ~/.claude/skills/paseo-committee/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/paseo-committee/SKILL.md. For a shared project, commit the folder at .claude/skills/paseo-committee/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Paseo Committee skill for this task: Write a problem-level prompt. Confirm any required inputs or files before making changes.
What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Committee Skill
Two agents from contrasting profiles, fresh context, planning a solution in parallel.
Use the user's request and current conversation as input, including any arguments supplied with the skill invocation.
## Prerequisites
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`.
## Composition
Two members with different reasoning styles, selected from configured Agent profiles:
- one whose notes fit planning, research, or root-cause analysis - one contrasting high-reasoning profile from another provider family
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.
## Hard rules
- **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.
## Workflow
1. Write a problem-level prompt 2. Create both agents in parallel via Paseo with `[Committee] <task>` titles and the same prompt 3. Wait for both responses 4. Resolve disagreements by passing their arguments between each other 5. Keep going until they converge into a response
Share the consensus with the user. Summarize where the agents diverged and how they resolved it.
Intended uses
- Write a problem-level prompt
- Create both agents in parallel via Paseo with [Committee] <task> titles and the same prompt
- Wait for both responses
- Resolve disagreements by passing their arguments between each other
- Keep going until they converge into a response
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.