arthai-marketplace

/router-setup

One-command Arth Router install — discovers your Claude plan, generates a real pool config, starts the service, and wires the triage hook.

Synopsis

/router-setup

When to use it

• First-time setup: you want substantive prompts routed by the Arth Router (model/harness/platform decisions that are plan/credit-aware and budget-governed)
• Repairing a partial install (service down, env var missing, no pool config)
• Not for: day-to-day operation — that’s /router

Quickstart

/router-setup

What you’ll see: a state check (service running? config present? env wired?), plan discovery from your local Claude account (Max 20x / Max 5x / Pro → a capacity estimate for your 5-hour window), pool config generation, service start (Docker or a local venv — you confirm first), env wiring into ~/.claude/settings.json (you confirm first), and an end-to-end proof that a test prompt gets an ARTH ROUTER DECISION block.

Examples

/router-setup      # the only form — the skill takes no arguments

Typical runs:

• First time → plan discovered → pools generated → service started → hook wired → proof shown
• Service already running → reports status and skips to whatever is missing
• No repo access → tells you to request access to ArthTech-AI/arth-router and stops

What it does

1. Detects current state — health-checks the service, checks ~/.arthai/arth-router/policy.yaml and the ARTH_ROUTER_URL env var; runs only the missing steps.
2. Installs the service — Docker if the daemon is running, otherwise a local venv install from the arth-router repo.
3. Generates YOUR pool config — reads your plan tier from ~/.claude.json and writes a subscription pool with a per-tier capacity estimate (flagged as an estimate — calibrate later with /router calibrate).
4. Starts the service and (optionally) the outcomes bridge — a user-confirmation checkpoint.
5. Wires the env — merges ARTH_ROUTER_URL / ARTH_ORG into ~/.claude/settings.json (read-merge-write) — a user-confirmation checkpoint. New sessions pick it up automatically.
6. Proves it end-to-end — runs the triage hook against a test prompt and shows the injected decision block.

Requirements

• Python 3.11+ (or Docker), curl, and access to ArthTech-AI/arth-router
• Works with the router bundle’s triage-router hook (ships the fast path)

Output

Step-by-step progress ending in a proof block: the triage hook run against a test prompt showing the injected ARTH ROUTER DECISION (model/harness/platform, task type, pace, decision_id). Also prints your discovered plan tier and the capacity estimate written to the pool config.

Troubleshooting

Symptom	Fix
No repo access	Request access to ArthTech-AI/arth-router, re-run.
Port 8600 in use	Another router instance is running — /router status first; kill it or change ARTH_ROUTER_PORT.
Decision block missing in sessions	Env vars load at session START — open a new session. Verify with the proof step.
Plugin update removed the fast path	The router bundle ships the hook; re-install/update the bundle (or re-run this skill’s proof step to confirm).
Plan tier shows “unknown”	Capacity left unset — the router treats unknown capacity as on-pace and never guesses; set capacity_usd manually and calibrate.

Related

• /router — day-to-day operation (summary, pools, calibrate, outcomes)
• /otel-setup — telemetry for the Arth Intelligence dashboard (pairs well: outcomes + scores)