Install for Claude Code
Claude Code support starts with v2.1.0; the published release is v2.1.1. The marketplace commands below install the Plugin from the repository’s default branch.
Requirements
Section titled “Requirements”- Claude Code with Plugin support
- Node.js 24 or newer on the
PATHthat launches Claude Code - Python 3.11 or newer
The Plugin contains the MCP bundle and Python runtime archive. It ships no package.json, so Claude Code installs no npm dependencies.
Install from the marketplace
Section titled “Install from the marketplace”Run these commands inside Claude Code:
/plugin marketplace add eric861129/Workflow-skill-router/plugin install workflow-skill-router@workflow-skill-routerOr run them from a shell:
claude plugin marketplace add eric861129/Workflow-skill-routerclaude plugin install workflow-skill-router@workflow-skill-routerThe Plugin manifest carries the product version, so Claude Code offers an update when that version changes. Update with claude plugin update workflow-skill-router@workflow-skill-router.
Load a development checkout
Section titled “Load a development checkout”To test repository changes without installing them, start Claude Code from the repository root with the Plugin directory:
claude --plugin-dir plugins/claude-code/workflow-skill-routerRun python scripts/sync-claude-plugin.py first if you changed the MCP server, the Python core, or the canonical Skill references. CI runs the same script with --check.
Verify
Section titled “Verify”- Run
/mcpand confirm thatplugin:workflow-skill-router:workflow-skill-routeris connected. - Ask Claude Code: “Show the Workflow Skill Router status and explain which capabilities are available in this environment.” The answer should come from
get_router_statusand showbundled-local-r0. - For an offline check, run the bundled runtime with the host set. The output must include
"host": "claude-code".
WORKFLOW_SKILL_ROUTER_HOST=claude-code python plugins/claude-code/workflow-skill-router/runtime/workflow_skill_router.pyz doctorIf /mcp reports a failed server, Claude Code could not start Node.js or the runtime could not find Python 3.11+. The SKILL then runs as skill-only-fallback and must not claim durable state.
How Claude Code differs from Codex
Section titled “How Claude Code differs from Codex”| Topic | Claude Code behavior |
|---|---|
| Host setting | The Plugin’s .mcp.json sets WORKFLOW_SKILL_ROUTER_HOST=claude-code. An unknown value stops the MCP server before it reads any workspace file. |
| Workspace Profile | .claude/workflow-skill-router.json first, then .codex/workflow-skill-router.json. Workspace Memory policy files use the same order. |
| Personal Profiles and state | Shared with the Codex Plugin in the same external data directory. WORKFLOW_SKILL_ROUTER_DATA_DIR still overrides it. |
| Native Goal | Claude Code has none. Managed Goal work uses only the Router-owned local work graph and reports authority_mode=router-local. |
| Tool names | mcp__plugin_workflow-skill-router_workflow-skill-router__<tool> |
| Workspace trust | The server reads workspace files only inside MCP Client roots or WORKFLOW_SKILL_ROUTER_WORKSPACE_ROOTS. |
A repository used from both hosts can keep one .codex/workflow-skill-router.json. Add .claude/workflow-skill-router.json only when Claude Code needs a different Skill Tree.
Uninstall
Section titled “Uninstall”claude plugin uninstall workflow-skill-router@workflow-skill-routerRouter state lives outside the Plugin cache, so uninstalling keeps your Profiles, plans, and consent history. Review the local state guide before removing audit history.