MCPInstall

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.

Installs
4.8K
Last 24h
+31
Trending rank
#4312
Security
Pass

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/getpaseo/paseo --skill paseo-committee
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads paseo-committee automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

Security audits

Independent scans of the skill's instructions and bundled files.

Gen Agent Trust Hub PassSAFE ·The skill incorporates user-provided arguments directly into prompts for sub-agents, creating a surface for potential prompt injection. It includes defensive suffixes to restrict the actions of these sub-agents, mitigating the risk of unauthorized file modifications.
Socket PassNo alerts
Snyk PassLOW ·Risk: LOW · No issues
Runlayer PassNONE ·1 file scanned · No issues
ZeroLeaks PassNONE ·Score: 93/100 · 2 sections analyzed

SKILL.md

The instructions your agent reads when the skill is triggered.

Committee Skill

Two agents from contrasting profiles, fresh context, planning a solution in parallel.

User's additional context: $ARGUMENTS

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.

FAQ

What does the paseo-committee skill do?

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.

How do I install paseo-committee?

Run npx skills add https://github.com/getpaseo/paseo --skill paseo-committee in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/paseo-committee/ (personal) or .claude/skills/paseo-committee/ (project).

Which AI agents can use paseo-committee?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is paseo-committee safe to install?

Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk passed; Runlayer passed; ZeroLeaks passed. As with any skill, read the SKILL.md and bundled scripts before installing.

Who maintains paseo-committee?

It is published by getpaseo in getpaseo/paseo. It has 4,783 recorded installs.

More from getpaseo/paseo

View all →

paseo

getpaseo/paseo

Paseo reference for managing hosts, projects, workspaces, workspace scripts, agents, schedules, and heartbeats.

5.3K installs

paseo-handoff

getpaseo/paseo

Hand off the current task to another agent with full context. Use when the user says "handoff", "hand off", "hand this to", or wants to pass work to another agent.

paseo-advisor

getpaseo/paseo

Spin up a single agent as an advisor — second opinion on the current task. Use when the user says "advisor", "second opinion", "what does X think", or wants an outside take without delegating the work itself.

paseo-loop

getpaseo/paseo

Run an agent loop until an exit condition is met. Use when the user says "loop", "babysit", "keep trying until", "check every X", "watch", or wants iterative autonomous execution.

2.6K installs

release-stable

getpaseo/paseo

Cut a stable release of Paseo (fresh patch or minor, or promote from beta). Use when the user says "release stable", "ship stable", "promote", "release:patch", "release:minor", "release:promote", or "/release-stable".

2.3K installs

release-beta

getpaseo/paseo

Cut a beta release of Paseo. Use when the user says "release beta", "cut a beta", "ship a beta", "beta release", or "/release-beta".

2.2K installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.