Skip to content
Workflow Skill Router

Workflow Skill Router

Your Skill library in the contract phase

  • api-designerleads now
  • api-guidelines-skillsupports now
  • csharp-developernext phase
  • qa-test-plannerlater
  • playwrightlater
  • systematic-debuggingnot needed
  • Routes each phase on its own
  • Keeps the Skill you name in charge
  • Asks before adding support
  • One Profile for both hosts
  • Local state, no telemetry
> /plugin install workflow-skill-router@workflow-skill-router
> Deliver the api contract, implementation, and tests.

workflow-skill-router · plan_work
  route_source        workspace-profile
  routing_envelope    phased
  current phase       contract
  lead                api-designer
  support             api-guidelines-skill
  later phases        csharp-developer, qa-test-planner
  activation_status   intended-unverified

One lead Skill per phase, for Claude Code and Codex.

Claude Code and Codex

v2.1.2 published

MIT licence on GitHubInstructions only? Use Skill onlyInstall the Plugin

One lead
per phase

1+3

One lead Skill and up to three support Skills in each phase.

As your Skill library grows, every task starts with the same questions: which Skill should lead, when should another one help, and what belongs in the next phase? Claude Code and Codex can answer them on their own, but the answers drift from task to task. Workflow Skill Router writes your answers down. A Profile maps kinds of work to a lead Skill, up to three support Skills, and an exit gate for each phase. The Router reads the request, applies the Profile, checks which Skills this environment can really use, and shows the route before your agent continues. Your agent and your Skills still do the work.

Nine recorded routes

Each row is a trace produced by the Router core. Open one to see its route. Where the request locked a Skill, try approving or rejecting the support.

Request

Decision

Envelope

MCP calls

Work graph

Audit trail

    Evidence boundary

    Drawn from core-derived data. Read-only.

    How a route forms

    Deliver the api contract, implementation, and tests.

    domain
    api

    First it reads the request.

    Deliver the api contract, implementation, and tests.

    domain
    api
    profile
    workspace · api-delivery
    envelope
    phased, 3 phases

    Then it picks the shape of the work.

    Deliver the api contract, implementation, and tests.

    domain
    api
    profile
    workspace · api-delivery
    envelope
    phased, 3 phases
    lead
    api-designer
    support
    api-guidelines-skill
    activation
    intended-unverified

    Then one Skill leads the phase.

    Deliver the api contract, implementation, and tests.

    domain
    api
    profile
    workspace · api-delivery
    envelope
    phased, 3 phases
    lead
    api-designer
    support
    api-guidelines-skill
    activation
    intended-unverified
    gate
    contract-reviewed passed
    next lead
    csharp-developer

    At each gate, it routes again.

    What stays in your hands

    Scoped consent

    Support outside the Skill you named waits for your answer. A rejected Skill never becomes active.

    Explicit Skill Lock

    The Skill you name leads the route.

    Workflow Memory

    Off until you turn it on. No background learning.

    Runtime check

    A planned Skill that is not installed is reported, never swapped.

    Two hosts, one Profile

    Claude Code and Codex read the same personal Profile.

    Usage report

    Planned and actual Skills, side by side when the work ends.

    Workspace Profile

    Claude Code reads .claude/ first, then .codex/.

    Two commands, then one question.

    Read the install guides

    Claude Code

    • Add/plugin marketplace add eric861129/Workflow-skill-routerAdds this repository as a plugin marketplace.
    • Install/plugin install workflow-skill-router@workflow-skill-routerInstalls the Plugin with its MCP server and Skill.
    • CheckShow the Workflow Skill Router status and explain which capabilities are available in this environment.Expect the bundled-local-r0 runtime.
    • NeedsNode.js 24+ and Python 3.11+No npm install. State stays outside the Plugin cache.
    Claude Code guide

    Codex

    • Addcodex plugin marketplace add eric861129/Workflow-skill-router --ref v2.1.2Pins the v2.1.2 release.
    • Installcodex plugin add workflow-skill-router@workflow-skill-routerThen run codex plugin list to confirm it.
    • CheckShow the Workflow Skill Router status and explain which capabilities are available in this environment.Ask in a new Codex task.
    • NeedsNode.js 24+ and Python 3.11+The release already includes the MCP bundle and runtime.
    Codex guide

    Skill only

    • Downloadworkflow-skill-router-skill-v2.1.2.zipFrom the v2.1.2 GitHub Release.
    • ExtractThe inner workflow-skill-router/ folderInto your Codex Skills directory.
    • LimitsInstructions onlyNo durable state, no consent records, no MCP tools.
    Skill-only guide

    What we measured

    6

    routing cases

    1

    run per case and arm

    26–28%

    more input tokens in this setup

    3/6 → 6/6

    final route fields, Sol retest

    0/6 → 3/6

    stricter full contract, Sol retest

    v2.1.0

    release gate run with a Claude model

    What the tests show so far

    On 2026-10-19, we compared routing with and without the Router using GPT-6.1 Sol, GPT-6 Astra, and GPT-6 Luna at medium reasoning. The six-case exploration showed some more consistent workflow decisions. It did not execute development tasks or measure code quality.

    After clarifying ambiguous case assumptions and updating the instructions, only Sol was retested. These single-run observations do not establish repeatability, formal model qualification, or full Plugin/host integration. The complete instruction package increased input tokens; lower cost and faster delivery have not been demonstrated.

    Start with the published release

    v2.1.2 contains the routing instructions, the local MCP runtime, the Claude Code Plugin, and opt-in Workflow Memory, which is off by default. It fixes plan_work for Skills named without the skill: prefix; the routing instructions are unchanged from v2.1.0. The current exploration does not qualify v2.1.2. The release gate was a separate paired run with a Claude model on v2.1.0.

    Read the evaluation method and limits

    Memory Flight Recorder

    Included in v2.1.0. These existing records cover five sanitized scenarios for policy, proposals, profile updates, and purge events. Workflow Memory is off by default.

    deterministic-local-pilotnot Model Evidence

    Policy resolution

    fixture-trace

    Personal sets the ceiling; Workspace may only reduce it.

    1. personal-policyreviewed · personal-ceiling
    2. workspace-policyobserve · workspace-reduction
    3. effective-policyobserve · workspace-cannot-elevate
    Records
    20
    Single
    6
    Phased
    8
    Goal-like
    6
    Profile-assisted
    12

    Questions

    Does it install or run my Skills?

    No. The Router plans which Skill leads and which support each phase needs. Installing Skills, activating them, and granting permissions stay with you and with Claude Code or Codex.

    Which model does it use?

    None of its own. The local runtime classifies work and matches Profiles with deterministic rules, and your agent keeps the model you chose.

    Does it send data anywhere?

    No. Plans, consent records, and Profiles live in a local data directory outside the Plugin cache, and telemetry is off.

    What if Python is missing?

    The MCP server cannot start, so the Skill runs as skill-only-fallback: routing instructions without durable state. It says so instead of claiming the full mode.

    Can Claude Code and Codex share my setup?

    Yes. Both read the same personal Profiles and local state. A repository can keep one .codex/workflow-skill-router.json, or add .claude/workflow-skill-router.json when Claude Code needs a different Skill Tree.

    Is it ready for my team?

    v2.1.2 is published for Claude Code and Codex. The evaluation so far covers routing decisions only, so try it on your own workflow first.