ci-cd is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Design the shape of a delivery pipeline — what each stage actually proves, what gates what, where verification belongs, and how a run reports the truth instead of a green tick. Use when a pipeline is being designed or restructured, when a release got through a passing pipeline broken, when deciding what blocks a merge or a deploy, or when a stage claims more than it ran. Not for provider-specific workflow YAML (github-actions), image authoring (docker), writing the tests themselves (test-design).
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Pipeline design
A pipeline is a chain of claims about a commit. Each stage is entitled to exactly one claim, and
almost every bad release is a stage that made a bigger one than it earned.
Keep the words apart, because the pipeline will not:
- **built** — it compiled and packaged. Nothing ran.
- **executed** — the code ran. Nobody asserted anything about what it did.
- **tested** — assertions ran against it and passed. Only the assertions that exist.
- **reviewed** — a human or an agent read it. No execution is implied.
- **deployed** — the artifact reached an environment. It may be crash-looping.
- **verified** — the deployed thing was observed doing the intended work, in that environment.
A pipeline that reports "deployed" as "verified" is the single most expensive defect in this
document.
## When this fires
A pipeline is being designed, restructured, or reviewed; something broken reached an environment
through a passing pipeline; the gate policy is in question; or a stage's reported meaning does not
match what it ran. It does not fire for one workflow file's syntax, nor during an active incident,
where restoring service outranks fixing the pipeline that let it through.
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_mdsmx3vqby5zg6e3
GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/ci-cd
GET https://markdownregistry.com/api/v1/blob/522ad265aaf94490f172da23d1c7e25eae2b6c12355eee1709238c4f2d567a7b
Your agent 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.
nahid-sparktales/agent-dispatcher · skills/agent-dispatcher/SKILL.md · Route work to a specialist role and load its task-specific guidance. Use when the user invokes /agent-dispatcher, names…
nahid-sparktales/agent-dispatcher · skills/ai/agent-design/SKILL.md · Scope an agent or subagent before it is built — the one job it owns, the smallest tool set that closes that job, what…
nahid-sparktales/agent-dispatcher · skills/ai/agent-evals/SKILL.md · Build an eval suite that can actually detect a regression — cases pulled from real traffic, graders that check…
nahid-sparktales/agent-dispatcher · skills/ai/context-engineering/SKILL.md · Decide what actually occupies the model's window — progressive disclosure through an index, retrieval versus inlining…
nahid-sparktales/agent-dispatcher · skills/ai/llm-observability/SKILL.md · See what an agent actually did — one trace per run with nested model, tool and retrieval spans, token and latency…
nahid-sparktales/agent-dispatcher · skills/ai/mcp-design/SKILL.md · Build an MCP server, or bring an existing one into a project — choosing the transport, deciding which tools, resources…
nahid-sparktales/agent-dispatcher · skills/ai/memory-design/SKILL.md · Decide what an agent should remember, which layer holds it, who it is scoped to, and how a stale or contradicted memory…
nahid-sparktales/agent-dispatcher · skills/ai/model-routing/SKILL.md · Pick a model per job and degrade sensibly when one fails — a quality bar per call site, candidates compared on the same…
nahid-sparktales/agent-dispatcher · skills/ai/prompt-engineering/SKILL.md · Write or revise a prompt so it holds up — output contract, instruction placement, examples that earn their place, an…
nahid-sparktales/agent-dispatcher · skills/ai/prompt-injection-defense/SKILL.md · Treat everything an agent reads but did not author as data rather than instructions — an explicit trust boundary, a…
nahid-sparktales/agent-dispatcher · skills/ai/retrieval-rag/SKILL.md · Build and fix retrieval that actually returns the right passage — structure-aware chunking, one pinned embedding model…
nahid-sparktales/agent-dispatcher · skills/ai/structured-output/SKILL.md · Get parseable, trustworthy structured results out of a model — schema design, the enforcement mechanism the provider…
outlinedriven/outline-driven-development · .devin/skills/ci-cd/SKILL.md · Use when setting up or modifying CI/CD pipelines, quality gates, test runners, or deployment pipeline configuration…
outlinedriven/odin-claude-plugin · plugins/odin-infra/skills/ci-cd/SKILL.md · Use when setting up or modifying CI/CD pipelines, quality gates, test runners, or deployment pipeline configuration…
kalarislabs/skill-doctor · skills/ci-cd/SKILL.md · GitHub Actions, required checks, TestMu, OS matrix, and merge gates for Skill Doctor. Use when editing workflows…
