Mohamed BoudraandGitHub
4108960709
* feat(skills): manage orchestration skills per host Agent skills execute on the daemon host, so their bundle, selection, and filesystem convergence must share that owner. Preserve the existing install semantics while letting every capable client manage the selected host and migrating the legacy desktop preference once. * fix(client): keep skill management internal Keep host skill management on the low-level daemon client used by the app. Do not expose daemon settings or the desktop-only compatibility migration through the shared Paseo API handed to plugins. * fix(e2e): declare skills fixture dependencies Use Playwright's required destructuring form for the test-scoped daemon sandbox fixture so CI can collect the real-host skills suite. * test(skills): use native managed paths Assert fixed skill targets relative to the daemon user's real home with platform-native path joining so the ownership contract holds on Windows and POSIX hosts.
3.3 KiB
title, description, nav, order, category
| title | description | nav | order | category |
|---|---|---|---|---|
| Orchestration skills | Paseo orchestration skills: teach coding agents to spawn, coordinate, and manage other agents using slash commands. | Skills | 32 | Orchestration |
Orchestration skills
Paseo ships orchestration skills that teach coding agents how to use Paseo tools and the CLI to spawn, coordinate, and manage other agents. Skills package common workflows as slash commands, so agents know how to orchestrate without you writing the briefing and safety rails each time.
Start with Orchestration if you want the mental model, or Common workflows for prompts you can use without installing skills.
Installation
Two ways to install:
- Paseo app: Connect to the host, then open Settings → Host → Agents → Orchestration skills. The selected host installs the skills on its own machine.
- Manual:
npx skills add getpaseo/paseo, this installs to~/.agents/skills/and sets up symlinks for each agent.
When a daemon finds installed Paseo skills, it keeps the selected bundled skills up to date on startup without removing deselected directories. Use the host's Orchestration skills card to install, update, choose, or uninstall skills. Removal always asks for confirmation.
/paseo, Paseo Reference
The foundational skill. Paseo reference for managing projects, workspaces, and agents. Load it when an agent needs to register a project, create agents, send them prompts, or manage workspace isolation.
Not typically invoked directly by users, it's a reference that other skills depend on.
/paseo show me the Paseo CLI surface for creating an agent in a worktree-isolated workspace
/paseo-handoff, Task Handoff
Hands off the current task to another agent with full context. Use it when you say "handoff", "hand off", "hand this to", or want to pass work to another agent.
The receiving agent gets a self-contained briefing with the task, context, relevant files, current state, what's been tried, decisions, acceptance criteria, and constraints. Provider comes from orchestration preferences unless you name one. Supports worktree-isolated workspaces when you ask for one.
/paseo-handoff hand off the auth fix to codex in a worktree-isolated workspace
/paseo-handoff hand this to claude opus for review
/paseo-committee, Committee Planning
Forms a committee of two high-reasoning agents to step back, do root cause analysis, and produce a plan. Use it when stuck, looping, tunnel-visioning, or facing a hard planning problem.
Committee members do analysis only. They do not edit, create, or delete files. The orchestrating agent synthesizes their plans, implements, then sends the diff back for review.
/paseo-committee why are the websocket connections dropping under load?
/paseo-committee plan the auth system migration
/paseo-advisor, Advisor
Spins up a single agent as an advisor, a second opinion on the current task. Use it when you say "advisor", "second opinion", "what does X think", or want an outside take without delegating the work itself.
The advisor gives a judgment. You decide what to do. The advisor prompt is analysis-only and ends with a no-edits instruction.
/paseo-advisor did I miss anything in this migration plan?
/paseo-advisor --provider claude/opus what is the UX risk in this flow?