How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

code-routing-diagram - Skill

Name: code-routing-diagram
Author: nextstage-brasil

Imported from nextstage-brasil/skills (.cursor/skills/code-routing-diagram/SKILL.md). Install upstream with npx skills add nextstage-brasil/skills --skill code-routing-diagram. Copyright stays with the author.

Code routing diagram (this repo only)

Audience: maintainers of nextstage-brasil/skills. Not a catalog skill for consumer projects.

Produce an accurate Mermaid flowchart of runtime handoffs between implementation skills — especially ns-execution-gitlab-issue and ns-coder (C2 under autonomous).

When to use

Routing changed in catalog skills and the diagram must match
You need a visual map of issue → autonomous → coder → reviewer
Personal note under docs/ (gitignored) — copy mermaid there after updating canonical source

Source of truth (read before drawing)

Path	Role
`skills/ns-harness/references/code-skill-routing.md`	Priority table, handoffs, canonical ```mermaid block
`skills/ns-execution-gitlab-issue/references/entry-triggers.md`	Priority 1
`skills/ns-spec-driven/references/entry-triggers.md`	Priority 2
`skills/ns-autonomous/references/entry-triggers.md`	Priority 3
`skills/ns-investigator/references/entry-triggers.md`	Priority 4
`skills/ns-coder/references/entry-triggers.md`	Priority 5
`skills/*/SKILL.md` routing sections	Handoffs out
`skills/ns-autonomous/references/routing.md`	Engine anti-cycle

Details: references/canonical-sources.md, references/mermaid-conventions.md.

Workflow

1. Reconcile

Read all sources above. If diagram and skills disagree, edit skills first — never only the diagram.

2. Update canonical mermaid

Edit the block under Skill handoffs (diagram source) in:

skills/ns-harness/references/code-skill-routing.md

Follow references/mermaid-conventions.md. Commit this file with any routing skill changes.

3. Personal copy (optional)

If the maintainer wants a local file (e.g. docs/coder-routing.mmd — often gitignored):

node packages/harness/scripts/export-code-routing-mermaid.mjs docs/coder-routing.mmd

Or paste the mermaid block manually. Do not treat docs/ as source of truth.

4. Report

What changed in harness reference / routing skills
Whether a personal copy was written (path)
Reminder: catalog skills drive runtime; diagram is documentation for maintainers

Forbidden

Adding this skill to catalog.json or harness presets
Drawing from memory or stale exports
C2 → G as an active edge (engine anti-cycle)
Confusing install depends with runtime routing

Install code-routing-diagram and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "nextstage-brasil-skills-code-routing-diagram", "kind": "skill", "name": "code-routing-diagram", "description": "Maintainer-only skill for the nextstage-brasil/skills repo. Create or update the Mermaid flowchart that shows GitLab issue execution, coder entry, investigator, spec-driven, and autonomous handoffs. Use when working IN this repository and the user asks for routing diagram, coder flow mermaid, issue resolution chart, or after changing routing in ns-code-* skills. NOT installed via harness — lives in .cursor/skills/. Skills are source of truth; the diagram is derived from them. Do NOT invent routing in the diagram alone.", "publisher": "nextstage-brasil", "version": "1.0.0", "capabilities": { "domains": [ "coding", "data_analysis" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Maintainer-only skill for the nextstage-brasil/skills repo. Create or update the Mermaid flowchart that shows GitLab issue execution, coder entry, investigator, spec-driven, and autonomous handoffs. Use when working IN this repository and the user asks for routing diagram, coder flow mermaid, issue resolution chart, or after changing routing in ns-code-* skills. NOT installed via harness — lives in .cursor/skills/. Skills are source of truth; the diagram is derived from them. Do NOT invent routing in the diagram alone." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/nextstage-brasil/skills", "path": ".cursor/skills/code-routing-diagram/SKILL.md", "ref": "HEAD", "url": "https://github.com/nextstage-brasil/skills/blob/HEAD/.cursor/skills/code-routing-diagram/SKILL.md", "key": "nextstage-brasil/skills/.cursor/skills/code-routing-diagram/SKILL.md" } }, "instructions": "# Code routing diagram (this repo only)\n\n**Audience:** maintainers of `nextstage-brasil/skills`. **Not** a catalog skill for consumer projects.\n\nProduce an accurate Mermaid flowchart of runtime handoffs between implementation skills — especially `ns-execution-gitlab-issue` and `ns-coder` (`C2` under autonomous).\n\n## When to use\n\n- Routing changed in catalog skills and the diagram must match\n- You need a visual map of issue → autonomous → coder → reviewer\n- Personal note under `docs/` (gitignored) — copy mermaid there after updating canonical source\n\n## Source of truth (read before drawing)\n\n| ", "cost": { "context_tokens": 600 } }

code-routing-diagram

About

Code routing diagram (this repo only)

When to use

Source of truth (read before drawing)

Workflow

1. Reconcile

2. Update canonical mermaid

3. Personal copy (optional)

4. Report

Forbidden

Install code-routing-diagram and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews