Agent skill

Paseo Agent Orchestration Reference

by getpaseo in getpaseo/paseo

Reference for managing Paseo's projects, workspaces, workspace scripts and agents through its MCP tools or CLI, across a local or remote daemon.

Custom licenceAuto-check passedAgent Workflows

Install Paseo Agent Orchestration Reference

skills CLI
$ npx skills add getpaseo/paseo --skill paseo -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install getpaseo/paseo paseo --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/getpaseo/paseo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/paseo .claude/skills/paseo && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
paseo
GitHub stars
20k
Token cost
~2.1k tokens
SKILL.md length
908 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
Custom licence

At a glance

Reference for managing Paseo's projects, workspaces, workspace scripts and agents through its MCP tools or CLI, across a local or remote daemon.

  • Creating a new workspace with worktree isolation for a specific branch or PR
  • SKILL.md covers Projects, Workspaces, Workspace scripts and Agents, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Starting or stopping a configured workspace script through Paseo

What it does

Covers projects, workspaces and workspace scripts as three nested layers managed through a mix of CLI commands and MCP tool calls. Project commands create, list, rename and delete entries in the daemon's project registry, with a local daemon defaulting to the current directory and resolving relative paths on the CLI machine, while a remote daemon targeted with `--host` always needs an explicit path that it resolves on its own machine; deleting a project archives its active workspaces without touching the project directory itself.

A workspace is created independently of any agent with a required isolation mode of either `local` or `worktree`, where worktree isolation supports branching off a new branch, checking out an existing branch, or checking out a pull request, and a managed path is controlled separately from the branch name. Choosing a base branch is explicit: an `origin/main` style ref selects the remote-tracking branch, a `refs/heads/main` style ref selects local main, and a bare name like `main` prefers local main when it exists; Paseo keeps the resolved ref fixed for later comparisons even if the branch is later rebased or its PR target changes.

Workspace scripts configured in `paseo.json` share one supervised lifecycle across both the CLI and the tools: listing shows each script's lifecycle state, service port, proxy URL, health and exit code, while starting or stopping one goes through Paseo's own managed launcher and supervised terminal rather than a bare process.

When your agent uses it

  • Creating a new workspace with worktree isolation for a specific branch or PR
  • Starting or stopping a configured workspace script through Paseo
  • Managing which projects are registered with a local or remote Paseo daemon
  • Checking a workspace script's health, port and exit status

Example prompts

  • “Create a worktree workspace checking out PR #482 in this project.”
  • “Start the dev-server script in this workspace and tell me its proxy URL.”
  • “List every active workspace registered on the remote Paseo daemon.”

Requirements

  • A running Paseo daemon

What it can do on your machine

Read from SKILL.md and the folder at commit 99fc204. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Paseo Agent Orchestration Reference loads about 2.1k tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 908 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~28
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 908 words (~2,104 tokens).

“Paseo is a remote daemon that manages coding agents, terminals. Control it through MCP tools or the CLI.”

— opening of SKILL.md by getpaseo, Custom licence
name
paseo

Read the full SKILL.md on GitHub

Files

Just SKILL.md in skills/paseo of getpaseo/paseo.

Open the folder on GitHubat commit 99fc204

Compare with similar skills

Paseo Agent Orchestration Reference next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Paseo Agent Orchestration Reference compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Paseo Agent Orchestration Reference this skillgetpaseo/paseo20k—~2.1kAutomated safety check: PassCustom licence
MetaBot CLIxvirobotics/metabot991—~573Automated safety check: PassMIT
DAG Librarycode-yeongyu/oh-my-openagent70k—~1.1kAutomated safety check: PassCustom licence
Agent Kanban Maintainersaltbo/agent-kanban486—~1.6kAutomated safety check: PassCustom licence
Orca CLIstablyai/orca87k2 repos~593Automated safety check: PassMIT
O2 Review Loopopenobserve/openobserve22k—~3.7kAutomated safety check: PassAGPL-3.0

Similar skills

  • MetaBot CLI

    xvirobotics/metabot

    Documents the unified `metabot` CLI for personal memory, the skill hub, durable agent messaging, the agent registry, T5T status and scheduling.

    991 GitHub stars~573 tokensUpdated 23 days ago
    Agent WorkflowsAuto-check passed
  • DAG Library

    code-yeongyu/oh-my-openagent

    Stores a DAG definition once and re-runs it by name, with key rotation controlling whether each run is fresh or reuses an earlier result.

    70k GitHub stars~1.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Agent Kanban Maintainer

    saltbo/agent-kanban

    Acts as a manager in Agent Kanban: reviews the board on scheduled or heartbeat runs, creates and assigns tasks to worker agents, and reviews their submissions.

    486 GitHub stars~1.6k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed
  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    87k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed
  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Mission Control Agent API

    builderz-labs/mission-control

    Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.

    6.3k GitHub stars~2.1k tokensUpdated 10 days ago
    Agent WorkflowsAuto-check passed

More from getpaseo/paseo

  • Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Auto-check passed
  • Paseo Committee

    getpaseo/paseo

    Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.

    20k GitHub starsUsed in 1 repo~496 tokens
    Auto-check passed
  • Paseo Agent Handoff

    getpaseo/paseo

    Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.

    20k GitHub starsUsed in 1 repo~606 tokens
    Auto-check passed
  • Paseo Help

    getpaseo/paseo

    Answers questions about the Paseo app, such as setup, providers, connectivity, updates and logs, by checking the current public docs and working out which daemon is involved.

    20k GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Paseo Plugin Builder

    getpaseo/paseo

    Builds, installs and troubleshoots trusted local Paseo plugins, from lifecycle hooks and slash commands to screens, themes and timeline renderers.

    20k GitHub stars~9.4k tokensUpdated today
    Auto-check passed

Categories

Questions about Paseo Agent Orchestration Reference

What does Paseo Agent Orchestration Reference do?

Reference for managing Paseo's projects, workspaces, workspace scripts and agents through its MCP tools or CLI, across a local or remote daemon. Covers projects, workspaces and workspace scripts as three nested layers managed through a mix of CLI commands and MCP tool calls. Project commands create, list, rename and delete entries in the daemon's project registry, with a local daemon defaulting to the current directory and resolving relative paths on the CLI machine, while a remote daemon targeted with `--host` always needs an explicit path that it resolves on its own machine; deleting a project archives its active workspaces without touching the project directory itself.

When should I use Paseo Agent Orchestration Reference?

Paseo Agent Orchestration Reference fits situations like: creating a new workspace with worktree isolation for a specific branch or PR; starting or stopping a configured workspace script through Paseo; managing which projects are registered with a local or remote Paseo daemon; checking a workspace script's health, port and exit status.

How do I install Paseo Agent Orchestration Reference in Claude Code?

Run `npx skills add getpaseo/paseo --skill paseo -a claude-code`. Or copy the skill folder (skills/paseo in getpaseo/paseo) into .claude/skills/paseo in your project. Claude Code loads it when a task matches its description.

How do I install Paseo Agent Orchestration Reference in Codex?

Run `npx skills add getpaseo/paseo --skill paseo -a codex`. Or copy the skill folder (skills/paseo in getpaseo/paseo) into .agents/skills/paseo in your project. Codex loads it when a task matches its description.

Can I use Paseo Agent Orchestration Reference in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getpaseo/paseo --skill paseo -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/paseo, .gemini/skills/paseo, .github/skills/paseo and .opencode/skills/paseo in your project.

What does Paseo Agent Orchestration Reference need to run?

SKILL.md names no scripts, command-line tools or credentials: Paseo Agent Orchestration Reference is instructions for the agent only. Our summary lists: A running Paseo daemon.

Does Paseo Agent Orchestration Reference access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Paseo Agent Orchestration Reference safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Paseo Agent Orchestration Reference use?

Paseo Agent Orchestration Reference has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Paseo Agent Orchestration Reference use?

About 2.1k tokens (SKILL.md is roughly 8.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Paseo Agent Orchestration Reference?

Skills that share tags, products or a category with Paseo Agent Orchestration Reference: MetaBot CLI (xvirobotics/metabot, 991 stars), DAG Library (code-yeongyu/oh-my-openagent, 70k stars), Agent Kanban Maintainer (saltbo/agent-kanban, 486 stars) and Orca CLI (stablyai/orca, 87k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Paseo Agent Orchestration Reference?

getpaseo (a GitHub organization) maintains it in getpaseo/paseo, which has 20,039 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 7, 2026.

Source: getpaseo/paseo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.