ci-routing SKILL.md skillA
ci-routing from higoralves/orc is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add higoralves/orc/ci-routing@git:20261020.7a1f356Pins git:20261020.7a1f356 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- higoralves/orc
- Path
orc/skills/ci-routing/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261020.7a1f356, committed Oct 20, 2026
- First version recorded
- Aug 20, 2026
- Size
- 3,340 bytes
- Repository stars
- 7
- License
- MIT
The canonical route-on-verdict protocol for a red CI diagnosis — fixable/flake/infra/needs-debug handling, the single-render rule, and the fix-then-re-watch loop.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# CI Routing
The single source of truth for acting on an `orc-ci-investigator` diagnosis — `/orc:ci` and `/orc:flow`'s post-open CI gate both execute this protocol instead of restating it. Input: the diagnosis (verdict + evidence table + fix list), already saved verbatim to `${ORC_STATE_DIR}/<branch>/files/ci-diagnosis.md`.
**Single-render rule:** the diagnosis is saved via `Write` — never echoed wholesale into conversation. It gets ONE capped rendering: the fix list + one evidence line per root cause + the file path. Every later step references the saved file; quotes are capped at 3 evidence lines.
## `green`
Say so — one line, run ID cited. Mark the session step complete and stop.
## `fixable`
Render the one preview (`> **📋 Preview — CI fix list**`: N root causes across M jobs, then the numbered `<file>:<line> — <change> — clears <job>` list), then `AskUserQuestion` — **one call, two questions** (the landing decision is collected up front, so a green fixer report lands without a second stop):
…Read the whole file at its exact version.
How to install
mdr add higoralves/orc/ci-routing@sha256:e5811f21dfd59f65The line at the top of this page pins the label git:20261020.7a1f356, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_crjjgrxpjjmkz745)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Aug 20, 2026 and Oct 20, 2026, about one every 61 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261020.7a1f356 latest | 2026-10-20 | 7a1f356 | 3,340 B | A | view · diff |
| git:20260820.17364f9 | 2026-08-20 | 17364f9 | 3,328 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3340 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
higoralves/orc · 7 stars · license MIT · pushed 2026-10-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_crjjgrxpjjmkz745 GET https://markdownregistry.com/api/v1/resolve?ref=higoralves/orc/ci-routing GET https://markdownregistry.com/api/v1/blob/e5811f21dfd59f658750fbd1c9f98c58a4fb7ab9f9ea4d5c1b7cbecdfe2e1a3f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.