How do I install the Repo B Mx3 Router Contracts skill?

Run npx skillmds@latest add grtninja/repo-b-mx3-router-contracts in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Repo B Mx3 Router Contracts safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Repo B Mx3 Router Contracts?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Repo B Mx3 Router Contracts free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Repo B Mx3 Router Contracts?

grtninja (@grtninja) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Repo B Mx3 Router Contracts by grtninja

Name: Repo B Mx3 Router Contracts
Rating: 4.666666666666667 (3 reviews)
Author: grtninja

Repo B Mx3 Router Contracts

Validate MX3 shim model-router, ORT provider, and runtime packaging contracts. Use when changing route-mode derivation, router environment mapping, capability metadata, inference routing responses, exact ORT provider builds, or Electron/embedded-Node ABI ownership.

grtninja Updated Sep 10, 2026

File contents

Repo B MX3 Router Contracts

Use this skill for router-profile-aware model routing and ORT runtime-contract checks in the MX3 shim lane.

Workflow

Read repository guardrails and routing docs before code changes.
Set router profile env vars for deterministic scenario testing:
- MX3_NETWORK_PROFILE
- MESHGPT_ROUTER_MODE
- ROUTER_NETWORK_MODE
Run router-focused and ORT-contract tests after every behavior change.
Validate that health and inference responses expose effective routing and provider metadata.
Record profile-to-route evidence (gaming, streaming, wfh, traditional_qos, ai_auto).
Treat exact ORT package/build selection as part of the contract:
- provider package version
- CUDA vs DirectML lane
- expected provider readiness and fail-closed behavior
- Electron/embedded-Node ABI lane when desktop packaging changed

Canonical Commands

Run from <PRIVATE_REPO_B> root:

python -m pytest tests/test_model_router_capabilities.py
python -m pytest inference/router/tests -k router
python -m pytest tests/test_inference_ort_runtime_contract.py

Profile smoke:

$env:MX3_NETWORK_PROFILE="gaming"
python -m pytest tests/test_model_router_capabilities.py -k route_mode
curl -s http://127.0.0.1:9010/v1/router/health

Contract Requirements

Router profile aliases must map deterministically to route mode.
Capability metadata must include network_profile.
Inference policy output must include active profile and effective policy.
No silent fallbacks when profile env vars are explicitly set.
ORT runtime metadata must expose the selected provider/build expectation and readiness state.
Exact ORT package pins and provider assumptions must be documented when GPU/DirectML lanes change.
Do not silently treat a missing expected provider as a successful fallback.

Scope Boundary

Use this skill only for the repo-b-mx3-router-contracts lane and workflow defined in this file and its references.

Do not use this for unrelated lanes; route those through $skill-hub and the most specific matching skill.

Reference

references/router-contract-checklist.md

Loopback

If this lane is unresolved, blocked, or ambiguous:

Capture failing profile, route decision output, and test evidence.
Route back through $skill-hub for chain recalculation.
Resume only after the updated chain returns a deterministic next step.

---name: repo-b-mx3-router-contractsdescription: Validate MX3 shim model-router, ORT provider, and runtime packaging contracts. Use when changing route-mode derivation, router environment mapping, capability metadata, inference routing responses, exact ORT provider builds, or Electron/embedded-Node ABI ownership.---# Repo B MX3 Router ContractsUse this skill for router-profile-aware model routing and ORT runtime-contract checks in the MX3 shim lane.## Workflow1. Read repository guardrails and routing docs before code changes.2. Set router profile env vars for deterministic scenario testing: - `MX3_NETWORK_PROFILE` - `MESHGPT_ROUTER_MODE` - `ROUTER_NETWORK_MODE`3. Run router-focused and ORT-contract tests after every behavior change.4. Validate that health and inference responses expose effective routing and provider metadata.5. Record profile-to-route evidence (`gaming`, `streaming`, `wfh`, `traditional_qos`, `ai_auto`).6. Treat exact ORT package/build selection as part of the contract: - provider package version - CUDA vs DirectML lane - expected provider readiness and fail-closed behavior - Electron/embedded-Node ABI lane when desktop packaging changed## Canonical CommandsRun from `<PRIVATE_REPO_B>` root:```bashpython -m pytest tests/test_model_router_capabilities.pypython -m pytest inference/router/tests -k routerpython -m pytest tests/test_inference_ort_runtime_contract.py```Profile smoke:```bash$env:MX3_NETWORK_PROFILE="gaming"python -m pytest tests/test_model_router_capabilities.py -k route_modecurl -s http://127.0.0.1:9010/v1/router/health```## Contract Requirements- Router profile aliases must map deterministically to route mode.- Capability metadata must include `network_profile`.- Inference policy output must include active profile and effective policy.- No silent fallbacks when profile env vars are explicitly set.- ORT runtime metadata must expose the selected provider/build expectation and readiness state.- Exact ORT package pins and provider assumptions must be documented when GPU/DirectML lanes change.- Do not silently treat a missing expected provider as a successful fallback.## Scope BoundaryUse this skill only for the `repo-b-mx3-router-contracts` lane and workflow defined in this file and its references.Do not use this for unrelated lanes; route those through `$skill-hub` and the most specific matching skill.## Reference- `references/router-contract-checklist.md`## LoopbackIf this lane is unresolved, blocked, or ambiguous:1. Capture failing profile, route decision output, and test evidence.2. Route back through `$skill-hub` for chain recalculation.3. Resume only after the updated chain returns a deterministic next step.

Frequently asked questions