paseo-committee
- Use it when:
- You or the agent are stuck, going in circles or tunnel-visioned, or facing a hard planning problem.
- It does:
- Starts two agents from contrasting Paseo profiles, ideally from different provider families, gives both the same problem, then passes each one's arguments to the other until they converge.
- You get:
- One agreed plan, with a summary of where the two disagreed and how that was resolved.
- Won't:
- Let the committee change anything: every prompt to a member ends with a line forbidding edits, new files and code.
- Takes:
- As long as the models reason, often 15 to 30 minutes; the agent waits for Paseo's finish notice instead of polling.
- Needs:
- Paseo running with its MCP tools, and the repo's paseo skill.
Needs Paseo running, from its desktop app or the @getpaseo/cli daemon, with its MCP tools. It reads the repo's paseo skill first, which isn't listed, so install it alongside.
TL;DR
A committee is two agents with fresh context and different reasoning styles. The skill reads Paseo's agent profiles and their notes, then picks one whose notes fit planning, research or root-cause analysis and a contrasting high-reasoning one, preferably from another provider family, unless you name the members. When fewer than two profiles fit, it falls back to Paseo's provider list and tells you. Both members get the same problem-level prompt and a [Committee] title. The agent then waits for both answers without hurrying or interrupting them, settles disagreements by passing each member's arguments to the other, and keeps going until they converge. You get the consensus, plus where the two diverged and how they resolved it.
Summarizes the skill at 9f68af0.
npx skills add https://github.com/getpaseo/paseo --skill paseo-committee skills.sh pageSource on GitHubAll skills from getpaseo/paseo
- Total Downloads
- 5,200 on skills.sh, Nov 9, 2026
- Repo stars
- 23,565 getpaseo/paseo
- First seen
- Mar 15, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 185 |
| Sep 28 | 214 |
| Oct 5 | 240 |
| Oct 12 | 206 |
| Oct 19 | 181 |
| Oct 26 | 188 |
| Nov 2 | 210 |
| Nov 9 | 219 |
| Category |
Build agents, orchestrate workers and give agents memory. Make the agent question you and write the plan down before it writes code. Find root causes, review code and test what you built. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A multi-step process the agent follows: interview, debug, run a TDD loop, review. |
| Effect |
Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code. |
| Needs |
A specific command-line tool or desktop app must be installed, such as gh, agent-browser, LibreOffice, Obsidian or a vendor CLI. Needs an MCP server connected. |
| Publisher |
A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates. |
| Topics | |
| Stack |
SKILL.md
From getpaseo/paseo at 9f68af0. Checked daily, last changed Nov 7, 2026.
Frontmatter
name: paseo-committee
description: 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.
user-invocable: trueCommittee 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
- 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
Share the consensus with the user. Summarize where the agents diverged and how they resolved it.