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.
Control-plane workflow for coordinating multi-agent, multi-session project work from a single Codex, GitHub Copilot, or agent-app control session.
Install Control Session Orchestrator
$ npx skills add pskoett/pskoett-ai-skills --skill control-session-orchestrator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pskoett/pskoett-ai-skills control-session-orchestrator --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/pskoett/pskoett-ai-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/control-session-orchestrator .claude/skills/control-session-orchestrator && 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 "control-session-orchestrator" agent skill from https://github.com/pskoett/pskoett-ai-skills/tree/main/skills/control-session-orchestrator into .claude/skills/control-session-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "control-session-orchestrator", 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/pskoett/pskoett-ai-skills/tree/main/skills/control-session-orchestratorType 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 pskoett/pskoett-ai-skills --skill control-session-orchestrator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pskoett/pskoett-ai-skills control-session-orchestrator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pskoett/pskoett-ai-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/control-session-orchestrator .agents/skills/control-session-orchestrator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "control-session-orchestrator" agent skill from https://github.com/pskoett/pskoett-ai-skills/tree/main/skills/control-session-orchestrator into .agents/skills/control-session-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "control-session-orchestrator", 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 pskoett/pskoett-ai-skills --skill control-session-orchestrator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pskoett/pskoett-ai-skills control-session-orchestrator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pskoett/pskoett-ai-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/control-session-orchestrator .cursor/skills/control-session-orchestrator && 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 "control-session-orchestrator" agent skill from https://github.com/pskoett/pskoett-ai-skills/tree/main/skills/control-session-orchestrator into .cursor/skills/control-session-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "control-session-orchestrator", 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/pskoett/pskoett-ai-skills.git --path skills/control-session-orchestrator--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 pskoett/pskoett-ai-skills --skill control-session-orchestrator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pskoett/pskoett-ai-skills control-session-orchestrator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pskoett/pskoett-ai-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/control-session-orchestrator .gemini/skills/control-session-orchestrator && 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 "control-session-orchestrator" agent skill from https://github.com/pskoett/pskoett-ai-skills/tree/main/skills/control-session-orchestrator into .gemini/skills/control-session-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "control-session-orchestrator", 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 pskoett/pskoett-ai-skills control-session-orchestratorInstalls 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 pskoett/pskoett-ai-skills --skill control-session-orchestrator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pskoett/pskoett-ai-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/control-session-orchestrator .github/skills/control-session-orchestrator && 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 "control-session-orchestrator" agent skill from https://github.com/pskoett/pskoett-ai-skills/tree/main/skills/control-session-orchestrator into .github/skills/control-session-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "control-session-orchestrator", 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 pskoett/pskoett-ai-skills --skill control-session-orchestrator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pskoett/pskoett-ai-skills control-session-orchestrator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pskoett/pskoett-ai-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/control-session-orchestrator .opencode/skills/control-session-orchestrator && 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 "control-session-orchestrator" agent skill from https://github.com/pskoett/pskoett-ai-skills/tree/main/skills/control-session-orchestrator into .opencode/skills/control-session-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "control-session-orchestrator", 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
control-session-orchestrator- GitHub stars
- 311
- Token cost
- ~5.5k tokens
- SKILL.md length
- 2,483 words
- Files
- 2
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- None found
At a glance
Control-plane workflow for coordinating multi-agent, multi-session project work from a single Codex, GitHub Copilot, or agent-app control session.
- Works in 9 steps: Rehydrate (resume an in-flight mission) → Frame the mission → Detect the control surface → …
- The user asks to orchestrate agents
- SKILL.md covers Mental model, Supported control apps, When to use and Machine-checkable contracts, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Control Session Orchestrator is an agent skill from pskoett/pskoett-ai-skills. Control-plane workflow for coordinating multi-agent, multi-session project work from a single Codex, GitHub Copilot, or agent-app control session. Use this skill whenever the user asks to orchestrate agents, create or steer worker sessions, run a workflow-like effort, fan out audits/research/migrations, coordinate parallel implementation streams, monitor other project sessions, or compare this control-session pattern to Claude Code dynamic workflows. This skill is especially relevant when the current session can…
Its SKILL.md is about 5.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/evals.json`).
It sits in Agent Workflows, covering Multi-agent orchestration and Subagents.
When your agent uses it
- The user asks to orchestrate agents
- Steer worker sessions
- Run a workflow-like effort
- Fan out audits/research/migrations
Example prompts
- “/control-session-orchestrator”
Workflow steps
9 steps, taken from the step headings in SKILL.md.
- Rehydrate (resume an in-flight mission)
- Frame the mission
- Detect the control surface
- Choose the topology
- Dispatch workers with complete prompts
- Track state centrally
- Route follow-ups (result-gate)
- Iterate waves to convergence
- Verify and consolidate
What it can do on your machine
Read from SKILL.md and the folder at commit 5a836dc. 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 json and markdown).
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
Control Session Orchestrator loads about 5.5k tokens when it runs. Until then it costs about 169 tokens; SKILL.md has 2,483 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 2,483 words (~5,524 tokens).
“Use the current session as the control plane for project work that is too broad, risky, or stateful for one conversation. The control session owns intent, decomposition, routing, status, verification, and consolidation. Worker sessions own scoped execution. Worker subagents are…”
- name
- control-session-orchestrator
Files
SKILL.md and 1 other file in skills/control-session-orchestrator of pskoett/pskoett-ai-skills.
- SKILL.md
- evals/evals.json
Open the folder on GitHubat commit 5a836dc
Compare with similar skills
Control Session Orchestrator 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 |
|---|---|---|---|---|---|---|
| Control Session Orchestrator this skillpskoett/pskoett-ai-skills | 311 | — | ~5.5k | Automated safety check: Pass | None | |
| 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 | |
| Kimi Code DelegationCherryHQ/cherry-studio | 52k | 1 repos | ~504 | 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 |
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.
Kimi Code Delegation
CherryHQ/cherry-studio
Delegates one bounded repository task to Kimi Code in non-interactive prompt mode and reads back the final result from its JSON event stream.
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.
More from pskoett/pskoett-ai-skills
All 24 skills in this repoSelf Improvement
pskoett/pskoett-ai-skills
Captures learnings, errors, corrections, and feature requests to enable continuous improvement.
Self Improvement
pskoett/pskoett-ai-skills
Captures learnings, errors, corrections, and feature requests to enable continuous improvement.
Self Healing
pskoett/pskoett-ai-skills
Active runtime recovery for coding agents: when something breaks mid-task, diagnose the root cause, write a fix, VERIFY by re-running the broken thing, then file a HEAL- entry to .learnings/HEALS.md…
Skill Tester
pskoett/pskoett-ai-skills
Validates all interactive skills in this repo against the Agent Skills spec, project conventions, and structural requirements.
Skill Tester CI
pskoett/pskoett-ai-skills
Validates all CI skills in this repo. An agent skill from pskoett/pskoett-ai-skills.
Context Decay
pskoett/pskoett-ai-skills
Revalidate persistent agent knowledge by classifying why it can become stale and how quickly it changes, then retain, revise, externalize, or retire it.
Related
Categories
Questions about Control Session Orchestrator
What does Control Session Orchestrator do?
Control-plane workflow for coordinating multi-agent, multi-session project work from a single Codex, GitHub Copilot, or agent-app control session. Control Session Orchestrator is an agent skill from pskoett/pskoett-ai-skills. Control-plane workflow for coordinating multi-agent, multi-session project work from a single Codex, GitHub Copilot, or agent-app control session.
When should I use Control Session Orchestrator?
Control Session Orchestrator fits situations like: the user asks to orchestrate agents; steer worker sessions; run a workflow-like effort; fan out audits/research/migrations.
How do I install Control Session Orchestrator in Claude Code?
Run `npx skills add pskoett/pskoett-ai-skills --skill control-session-orchestrator -a claude-code`. Or copy the skill folder (skills/control-session-orchestrator in pskoett/pskoett-ai-skills) into .claude/skills/control-session-orchestrator in your project. Claude Code loads it when a task matches its description.
How do I install Control Session Orchestrator in Codex?
Run `npx skills add pskoett/pskoett-ai-skills --skill control-session-orchestrator -a codex`. Or copy the skill folder (skills/control-session-orchestrator in pskoett/pskoett-ai-skills) into .agents/skills/control-session-orchestrator in your project. Codex loads it when a task matches its description.
Can I use Control Session Orchestrator 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 pskoett/pskoett-ai-skills --skill control-session-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/control-session-orchestrator, .gemini/skills/control-session-orchestrator, .github/skills/control-session-orchestrator and .opencode/skills/control-session-orchestrator in your project.
What does Control Session Orchestrator need to run?
SKILL.md names no scripts, command-line tools or credentials: Control Session Orchestrator is instructions for the agent only.
Does Control Session Orchestrator 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 Control Session Orchestrator 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 Control Session Orchestrator use?
No licence was found for Control Session Orchestrator or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Control Session Orchestrator use?
About 5.5k tokens (SKILL.md is roughly 22k 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 Control Session Orchestrator?
Skills that share tags, products or a category with Control Session Orchestrator: Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars), Kimi Code Delegation (CherryHQ/cherry-studio, 52k stars) and Harness Agent Team Designer (revfactory/harness, 9.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Control Session Orchestrator?
pskoett (a GitHub user) maintains it in pskoett/pskoett-ai-skills, which has 311 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 5, 2026.
Source: pskoett/pskoett-ai-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.