deployment-strategies SKILL.md skillA
deployment-strategies from okhp3/skillz is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add okhp3/skillz/deployment-strategies@git:20260828.866dec6Pins git:20260828.866dec6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- okhp3/skillz
- Path
community/deployment-strategies/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260828.866dec6, committed Aug 28, 2026
- Size
- 4,723 bytes
- Repository stars
- 3
- License
- MIT
Gets a change into production safely — blue-green, canary, rolling, feature flags, and the rollback that makes each of them safe. Use this whenever the user is planning a release, asks how to deploy without downtime, mentions canary or blue-green, is adding a feature flag, or is nervous about a risky change going out. For deploying an AI agent specifically, use agent-deployment; for the pipeline that runs the deploy, use ci-pipelines.
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
# Deployment strategies Every deployment strategy is a way of buying information before you are fully committed. They differ in what they cost and how much they tell you. The question that decides everything: **how quickly can you undo it, and what does undo not cover?** A strategy without a tested rollback is not a strategy. ## 1. Separate deploy from release The most useful idea here, and the one that unlocks the rest. Deploying is shipping the code; releasing is turning the behaviour on. When they are the same event, every deploy is risky and every rollback is a deploy. Split them with a flag, and you can ship code continuously, turn a feature on for one account, and turn it off in seconds without a build. **Done when:** you can change behaviour without shipping code. ## 2. Choose the strategy the risk warrants | Strategy | Buys you | Costs | | --- | --- | --- | | **Rolling** | Simple, no extra capacity | Both versions live at once; slow rollback | | **Blue-green** | Instant switch and instant rollback | Double capacity during the switch | | **Canary** | Real traffic on a small blast radius | Needs traffic splitting and per-version metrics | …
Read the whole file at its exact version.
How to install
mdr add okhp3/skillz/deployment-strategies@sha256:af93c03d9f6b0653The line at the top of this page pins the label git:20260828.866dec6, 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_p34u2ssrrvlvmf45)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 28, 2026.
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 (4723 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
okhp3/skillz · 3 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_p34u2ssrrvlvmf45 GET https://markdownregistry.com/api/v1/resolve?ref=okhp3/skillz/deployment-strategies GET https://markdownregistry.com/api/v1/blob/af93c03d9f6b06533b661eb10e2c79b79d1ab4cc69ed425519738379749e201c
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.