Paseo Advisor Second Opinion
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.
Decompose work across parallel subagents properly — task slicing that avoids collisions, briefs that stand alone, and result integration that catches contradictions.
Install Subagent Orchestration
$ npx skills add mohitagw15856/pm-claude-skills --skill subagent-orchestration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills subagent-orchestration --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/subagent-orchestration .claude/skills/subagent-orchestration && rm -rf skills-srcUse ~/.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/
Install the "subagent-orchestration" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/subagent-orchestration into .claude/skills/subagent-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "subagent-orchestration", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/subagent-orchestrationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill subagent-orchestration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills subagent-orchestration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/subagent-orchestration .agents/skills/subagent-orchestration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "subagent-orchestration" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/subagent-orchestration into .agents/skills/subagent-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "subagent-orchestration", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill subagent-orchestration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills subagent-orchestration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/subagent-orchestration .cursor/skills/subagent-orchestration && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "subagent-orchestration" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/subagent-orchestration into .cursor/skills/subagent-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "subagent-orchestration", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/subagent-orchestration--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill subagent-orchestration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills subagent-orchestration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/subagent-orchestration .gemini/skills/subagent-orchestration && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "subagent-orchestration" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/subagent-orchestration into .gemini/skills/subagent-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "subagent-orchestration", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills subagent-orchestrationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill subagent-orchestration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/subagent-orchestration .github/skills/subagent-orchestration && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "subagent-orchestration" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/subagent-orchestration into .github/skills/subagent-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "subagent-orchestration", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill subagent-orchestration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills subagent-orchestration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/subagent-orchestration .opencode/skills/subagent-orchestration && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "subagent-orchestration" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/subagent-orchestration into .opencode/skills/subagent-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "subagent-orchestration", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
subagent-orchestration- GitHub stars
- 1.4k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 582 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Decompose work across parallel subagents properly — task slicing that avoids collisions, briefs that stand alone, and result integration that catches contradictions.
- Works in 6 steps: Decide IF before HOW. Delegation costs:… → Slice by ownership boundary, not by… → Write briefs that stand alone. A… → …
- Work can genuinely parallelise (research fan-outs
- SKILL.md covers What This Skill Produces, Orchestration Method, Output Format and Quality Checks, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Subagent Orchestration is an agent skill from mohitagw15856/pm-claude-skills. Decompose work across parallel subagents properly — task slicing that avoids collisions, briefs that stand alone, and result integration that catches contradictions. Use when work can genuinely parallelise (research fan-outs, multi-file changes, independent analyses), when deciding whether to delegate or do it yourself, or when past multi-agent runs produced conflicts and duplicated effort. Produces an orchestration plan: the parallel/sequential split, per-agent briefs, and the integration protocol.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Subagents and Multi-agent orchestration. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Work can genuinely parallelise (research fan-outs
- Multi-file changes
- Independent analyses)
- Deciding whether to delegate
Example prompts
- “/subagent-orchestration”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Decide IF before HOW. Delegation costs: brief-writing, context loss, integration, and review of work you didn't watch. Worth it when…
- Slice by ownership boundary, not by topic. The test per pair of subtasks: do they write to the same artifact, or does one's output change…
- Write briefs that stand alone. A subagent doesn't share your conversation. Each brief carries: the goal as an outcome test · the context…
- Pin the shared assumptions. If any decision affects multiple agents (naming, interface shapes, the version of truth), make it BEFORE…
- Integrate with suspicion. On return: check each result against its brief (subagents drift too) · diff for cross-agent contradictions…
- Sequence the merge. Integrate in dependency order, verifying at each join, not all-at-once at the end. A bad result caught at merge #1…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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.
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
Subagent Orchestration loads about 1.2k tokens when it runs. Until then it costs about 132 tokens; SKILL.md has 582 words of instructions outside code blocks.
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
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 582 words, ~1,198 tokens.
Download SKILL.mdSave it as
.claude/skills/subagent-orchestration/SKILL.md (or your agent's skills folder).- name
- subagent-orchestration
- description
- Decompose work across parallel subagents properly — task slicing that avoids collisions, briefs that stand alone, and result integration that catches contradictions. Use when work can genuinely parallelise (research fan-outs, multi-file changes, independent analyses), when deciding whether to delegate or do it yourself, or when past multi-agent runs produced conflicts and duplicated effort. Produces an orchestration plan: the parallel/sequential split, per-agent briefs, and the integration protocol.
Subagent Orchestration Skill
Parallel agents multiply speed exactly when the decomposition is right — and multiply mess when it isn't: two agents editing one file, three agents making inconsistent assumptions, results that can't be merged. Orchestration is a design discipline: slice for independence, brief for standalone execution, integrate with suspicion.
What This Skill Produces
- A decomposition decision: what runs parallel, what stays sequential, what isn't worth delegating at all
- Per-agent briefs that survive without shared context
- An integration protocol: merge order, conflict checks, and the verification of the combined result
Orchestration Method
- Decide IF before HOW. Delegation costs: brief-writing, context loss, integration, and review of work you didn't watch. Worth it when subtasks are genuinely independent AND individually substantial. A task you could finish in the time it takes to write two good briefs is yours to do.
- Slice by ownership boundary, not by topic. The test per pair of subtasks: do they write to the same artifact, or does one's output change the other's input? Yes → sequential or merged into one task. The safe cuts: different files/directories · different data sources to research · different independent deliverables. The classic collision: "agent A refactors, agent B adds tests" on the same module — topically distinct, physically overlapping.
- Write briefs that stand alone. A subagent doesn't share your conversation. Each brief carries: the goal as an outcome test · the context it can't infer (constraints, conventions, decisions already made — stated, not referenced) · what it must NOT touch (the other agents' territory, named) · the exact deliverable shape (so integration is mechanical) · when to stop and return rather than improvise.
- Pin the shared assumptions. If any decision affects multiple agents (naming, interface shapes, the version of truth), make it BEFORE dispatch and put it in every brief. Two agents each "reasonably deciding" an interface produces two interfaces.
- Integrate with suspicion. On return: check each result against its brief (subagents drift too) · diff for cross-agent contradictions (terminology, duplicate implementations, conflicting claims — the research fan-out that returns three different revenue numbers is a finding, not an averaging opportunity) · then run whole-result verification, because parts that pass individually can fail composed.
- Sequence the merge. Integrate in dependency order, verifying at each join, not all-at-once at the end. A bad result caught at merge #1 costs one redo; at merge #4 it costs archaeology.
Show full SKILL.md (194 more words)Show less
Output Format
Orchestration plan: [task]
Do-it-yourself instead? [no, because … / partially — these bits stay with me: …]
| Lane | Subtask (outcome test) | Territory (writes to) | Must not touch | Deliverable shape |
|---|---|---|---|---|
| parallel-1 | ||||
| sequential-after-1&2 |
Pinned shared assumptions (in every brief): … Integration protocol: [merge order · contradiction checks · the composed-result verification]
Quality Checks
- The delegate-vs-do decision was made explicitly, with the brief-writing cost counted
- No two parallel lanes write to the same artifact
- Every brief contains its territory, its must-not-touch, and a stop condition
- Shared assumptions were pinned before dispatch, not discovered at merge
- Integration verifies the composed whole, not just each part
Anti-Patterns
- Do not parallelise for the feeling of speed — two colliding agents are slower than one sequential pass
- Do not write briefs that reference your context ("as discussed", "the usual way") — subagents weren't in the room
- Do not average contradictory results — a contradiction is a defect to resolve, with a cause
- Do not merge everything then verify once — verify at each join while causes are still traceable
- Do not delegate the judgment-bearing core (the decision, the synthesis, the taste) — delegate the legwork around it
Example Trigger Phrases
- "Work can genuinely parallelise."
- "Decide whether to delegate."
- "Do it yourself?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/subagent-orchestration of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Subagent Orchestration 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Subagent Orchestration this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Paseo Advisor Second Opiniongetpaseo/paseo | 20k | 1 repos | ~756 | Automated safety check: Pass | Custom licence | |
| O2 Review Loopopenobserve/openobserve | 22k | — | ~3.7k | Automated safety check: Pass | AGPL-3.0 | |
| Harness Agent Team Designerrevfactory/harness | 9.1k | — | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| ClawTeam Multi-Agent Swarmwin4r/ClawTeam-OpenClaw | 1.5k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Sub-Agent Delegationcodewhale-hq/Codewhale | 41k | — | ~790 | Automated safety check: Pass | MIT |
Similar skills
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.
Harness Agent Team Designer
revfactory/harness
Designs a project-specific agent harness: defines specialist agents, writes the skills they follow, picks an execution mode and model for each, and keeps the setup maintained.
ClawTeam Multi-Agent Swarm
win4r/ClawTeam-OpenClaw
Launches a swarm of specialist Hermes agents in git-worktree-isolated tmux windows with a kanban board and file-based inboxes, using built-in templates like hedge-fund and code-review.
Sub-Agent Delegation
codewhale-hq/Codewhale
Guides when and how to split multi-step coding, research or verification work into focused sub-agent runs while the parent keeps integration and final checks.
Parallel Agents
xenitV1/Antigravity-Workflows
Native multi-agent orchestration using Claude Code's Agent Tool.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Subagent Orchestration
What does Subagent Orchestration do?
Decompose work across parallel subagents properly — task slicing that avoids collisions, briefs that stand alone, and result integration that catches contradictions. Subagent Orchestration is an agent skill from mohitagw15856/pm-claude-skills. Decompose work across parallel subagents properly — task slicing that avoids collisions, briefs that stand alone, and result integration that catches contradictions.
When should I use Subagent Orchestration?
Subagent Orchestration fits situations like: work can genuinely parallelise (research fan-outs; multi-file changes; independent analyses); deciding whether to delegate.
How do I install Subagent Orchestration in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill subagent-orchestration -a claude-code`. Or copy the skill folder (skills/subagent-orchestration in mohitagw15856/pm-claude-skills) into .claude/skills/subagent-orchestration in your project. Claude Code loads it when a task matches its description.
How do I install Subagent Orchestration in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill subagent-orchestration -a codex`. Or copy the skill folder (skills/subagent-orchestration in mohitagw15856/pm-claude-skills) into .agents/skills/subagent-orchestration in your project. Codex loads it when a task matches its description.
Can I use Subagent Orchestration 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 mohitagw15856/pm-claude-skills --skill subagent-orchestration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/subagent-orchestration, .gemini/skills/subagent-orchestration, .github/skills/subagent-orchestration and .opencode/skills/subagent-orchestration in your project.
What does Subagent Orchestration need to run?
SKILL.md names no scripts, command-line tools or credentials: Subagent Orchestration is instructions for the agent only.
Does Subagent Orchestration 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 Subagent Orchestration 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 Subagent Orchestration use?
Subagent Orchestration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Subagent Orchestration use?
About 1.2k tokens (SKILL.md is roughly 4.8k 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 Subagent Orchestration?
Skills that share tags, products or a category with Subagent Orchestration: Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars), Harness Agent Team Designer (revfactory/harness, 9.1k stars) and ClawTeam Multi-Agent Swarm (win4r/ClawTeam-OpenClaw, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Subagent Orchestration?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.