Get a second opinion on your current task from another AI agent. The skill selects a suitable advisor, provides the context, and summarizes its reasoned recommendation so you can assess design choices, reviews, or investigations without file changes.
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.
Review the instructions the agent will receive before you install.
Single agent. Reads the situation you're in. Gives a judgment. You decide what to do — the advisor doesn't drive the work.
User's request: $ARGUMENTS
Read the paseo skill. Call list_profiles before choosing the advisor. Do not create the advisor until you have read the configured profiles and their notes.
--profile UI Work) → select it by name.notes best fit the question. Match the actual work: design and approach, audit and review, or research and root-cause analysis.Materialize the selected profile into create_agent as described by the paseo skill. If no profile fits, use Paseo's provider discovery fallback.
The advisor has zero context. Make it self-contained:
End with the no-edits suffix:
This is analysis only. Do NOT edit, create, or delete any files. Do NOT write code.
If $ARGUMENTS contains another skill reference — /unslop, /unslop-risk, $unslop, etc. — the user is asking the advisor to run that skill against the current task. Examples:
/paseo-advisor /unslop → advisor runs /unslop on the current diff./paseo-advisor /unslop-risk → advisor does an unslop-risk review./paseo-advisor $diagnose this build failure → advisor invokes /diagnose.Parse the forwarded skill name out of $ARGUMENTS (/<name> or $<name>). In the briefing, tell the advisor explicitly:
Invoke the `<name>` skill against this task. Load it via the Skill tool before doing anything else.
Pass through any remaining arguments after the skill name as the skill's own input. The advisor — not you — runs the skill; you're still just the orchestrator handing it the work.
Create the advisor agent via Paseo with a [Advisor] <topic> title and the briefing as the initial prompt. Wait for it to finish. Read its response. Synthesize for the user — the advisor's verdict + your recommendation.
If the user wants ongoing input ("keep this advisor for the next few decisions"), don't archive after the first reply. Send follow-ups when you need another take. Archive when the user says they're done, or when the topic shifts and a fresh context would serve better.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Manage coding agents and their workspaces in Paseo through its tools or command line. This reference covers project registration, workspace scripts, agent settings, recurring tasks, and reminders that return to the current conversation.
Analyze a difficult problem with two agents chosen for contrasting reasoning styles. They independently investigate causes and plan a solution, then exchange arguments to resolve disagreements and produce a shared recommendation without changing files.
Hand an ongoing task to a fresh agent with a self-contained briefing. The skill gathers context, decisions, failed attempts, acceptance criteria, and constraints, then launches the receiving agent in the current workspace or a requested isolated workspace.
Get help setting up, configuring, and troubleshooting Paseo using current public documentation. Identify the affected host and connection method, then use relevant diagnostics to investigate provider, version, workspace, or connectivity problems.
Build and manage local Paseo plugins that add screens, workspace panels, commands, themes, or searchable attachments. It also covers hooks, code triggered by lifecycle events, and backend handlers for custom integrations and agent configuration changes.
Prepare a beta release of Paseo by following the project's release documentation. The skill directs the agent through the beta workflow and its completion checklist, keeping the task tied to the documented process.