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.

Install it, pinned

mdr add higoralves/orc/ci-routing@git:20261106.693b476

Pins git:20261106.693b476 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: higoralves/orc
Path: codex/orc/content/skills/ci-routing/SKILL.md
Versions recorded: 1
Latest version: git:20261106.693b476, committed Nov 6, 2026
Size: 3,442 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 `the available user-question tool (or ask in chat)` — **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

The exact contents, by fingerprint

mdr add higoralves/orc/ci-routing@sha256:bac248daa4ce29eb

The line at the top of this page pins the label git:20261106.693b476, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_ppojpcqxgdoeatmq.svg)](https://markdownregistry.com/a/art_ppojpcqxgdoeatmq)

0 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Nov 6, 2026.

version	committed	commit	size	audit
git:20261106.693b476 latest	2026-11-06	693b476	3,442 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (3442 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

GitHub

higoralves/orc · 7 stars · license MIT · pushed 2026-11-06 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ppojpcqxgdoeatmq
GET https://markdownregistry.com/api/v1/resolve?ref=higoralves/orc/ci-routing
GET https://markdownregistry.com/api/v1/blob/bac248daa4ce29eb00f6dcf5eff3b0a69fe21d946673b50c9b2a8bb78757e089

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.