Paseo Orchestrate
Handles legacy invocations of the old Paseo orchestration skill name by routing you to the current epic workflow.
Overview
paseo-orchestrate is an agent skill for the Build phase that redirects deprecated invocations to `paseo-epic` with an explicit one-sentence user notice.
Install
npx skills add https://github.com/getpaseo/paseo --skill paseo-orchestrateWhat is this skill?
- Automatically loads `paseo-epic` and follows that skill’s instructions
- Tells the user in one sentence that `paseo-orchestrate` is deprecated
- User-invocable stub so old muscle memory and docs links still resolve
- No standalone orchestration logic—pure rename handoff
Adoption & trust: 756 installs on skills.sh; 8k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your prompts, docs, or habits still call `paseo-orchestrate` after the skill was renamed.
Who is it for?
Anyone reusing older Paseo instructions or slash commands that reference `paseo-orchestrate`.
Skip if: New projects where you should invoke `paseo-epic` directly and skip the deprecated alias entirely.
When should I use this skill?
User or agent invokes `paseo-orchestrate` or legacy docs reference the old Paseo orchestrate skill name.
What do I get? / Deliverables
The agent loads `paseo-epic` and continues the epic workflow while telling you the old name is deprecated.
- Redirect to `paseo-epic` execution
- One-sentence deprecation message to the user
Recommended Skills
Journey fit
Paseo skills are agent workflow tooling; the canonical shelf for orchestration-style entry points in Prism is Build → agent-tooling even though this file only redirects. Orchestration and epic planning live in the agent-tooling shelf where multi-step agent runbooks are discovered, not in ship or operate monitoring.
How it compares
A rename stub—not a separate orchestration workflow alongside `paseo-epic`.
Common Questions / FAQ
Who is paseo-orchestrate for?
Solo builders and small teams using the Paseo agent skill pack who still trigger the old orchestrate skill name from legacy prompts or docs.
When should I use paseo-orchestrate?
Only when something explicitly invokes `paseo-orchestrate`; during Build agent-tooling setup the agent will redirect you to `paseo-epic` automatically.
Is paseo-orchestrate safe to install?
It only redirects to another skill in the same repo; review the Security Audits panel on this Prism page and prefer `paseo-epic` for new work.
Workflow Chain
Then invoke: paseo epic
SKILL.md
READMESKILL.md - Paseo Orchestrate
# Deprecated — use `paseo-epic` This skill has been renamed to `paseo-epic`. 1. Load the `paseo-epic` skill and follow it. 2. Tell the user, in one sentence: `paseo-orchestrate` is deprecated — using `paseo-epic` instead.