execution-router

Route tasks to local, remote SSH, or subagent execution lanes.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Ocean326/Agents --skill execution-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execution-router
Source: https://github.com/Ocean326/Agents/tree/main/skills/global/execution-router
Command: npx skills add https://github.com/Ocean326/Agents --skill execution-router

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Execution Router decides whether to keep work local, dispatch remote SSH compute, or delegate to explicit subagent workflows, enabling efficient task orchestration.

Core Features & Use Cases

  • Route work to the most appropriate execution lane (local, remote, or subagent) based on policy.
  • Support explicit parallelization, delegation, and recoverable remote execution.
  • Use cases include long-running tasks, parallelized work streams, and complex orchestration across agents.

Quick Start

Use the router to decide the execution path for a given task.

Frequently Asked Questions about execution-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does task routing work for agent workflows?

Task routing for agent workflows applies explicit decision rules to select an execution lane, choosing between local processing, remote SSH compute, or subagent delegation. This routing policy produces a deterministic output format to ensure clear execution-lane selection.

When do I need to route work to remote SSH compute instead of running locally?

You need to route work to remote SSH compute instead of running locally when handling long-running tasks or parallelized work streams that require recoverable remote execution. Execution routing enables efficient task orchestration by dispatching heavy compute loads away from the local environment.

Can I use subagent delegation for parallelized work streams?

Yes, you can use subagent delegation for parallelized work streams. The execution router supports explicit parallelization by delegating tasks to subagent workflows, enabling complex orchestration and parallelized execution across multiple agents.

What is the best way to orchestrate complex tasks across multiple agents?

The best way to orchestrate complex tasks across multiple agents is to apply an execution routing policy with explicit decision rules. This approach determines whether to keep work local, dispatch remote SSH compute, or delegate to subagents for efficient task orchestration.

Does the execution router require specific dependencies for task delegation?

No, the execution router does not require specific dependencies for task delegation. It operates independently to apply decision rules and a clear routing policy, orchestrating tasks locally, on remote SSH compute, or via subagents without external component requirements.