deployment-automation SKILL.md skillA
deployment-automation from akillness/jeo-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add akillness/jeo-skills/deployment-automation@v2.1.0Pins v2.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- akillness/jeo-skills
- Path
.agent-skills/deployment-automation/SKILL.md- Versions recorded
- 5
- Latest version
- v2.1.0, committed Jul 28, 2026
- First version recorded
- Mar 19, 2026
- Size
- 10,930 bytes
- Repository stars
- 52
- License
- none declared
Plan and review release execution for web, backend, and fullstack systems: preview releases, staging-to-production promotion, rollout strategy, post-deploy verification, rollback response, and release-hardening checklists. Use when the system can already build and the main job is shipping or recovering a release safely, choosing between preview / promotion / canary / rollback paths, or tightening deploy gates around health checks and sign-off. CI workflow and release-job authoring belongs here…
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 Automation Use this skill when the job is **safe release execution after the system is already buildable**. `deployment-automation` is the repo's release-execution anchor for: - preview releases and shareable review environments - staging → production promotion and sign-off gates - rollout strategy choice: replace, rolling, blue-green, canary, progressive - post-deploy verification and stop conditions - rollback response and bad-release containment - release-hardening packets around an existing deploy path Read these support docs before deciding the packet: - [references/deployment-modes-and-boundaries.md](references/deployment-modes-and-boundaries.md) - [references/release-packet-templates.md](references/release-packet-templates.md) - [references/strategy-selection-and-stop-conditions.md](references/strategy-selection-and-stop-conditions.md) - [references/rollout-and-rollback-checklist.md](references/rollout-and-rollback-checklist.md) - [references/platform-routing-notes.md](references/platform-routing-notes.md) ## When to use this skill - A preview or branch deployment exists, but nobody agrees what it is supposed to prove before merge. …
Read the whole file at its exact version.
How to install
mdr add akillness/jeo-skills/deployment-automation@sha256:7a6a895765ea89a3The line at the top of this page pins the label v2.1.0, 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_zozibu3rat5wzfrk)
7 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Mar 19, 2026 and Jul 28, 2026, about one every 33 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.1.0 latest | 2026-07-28 | 4f971c4 | 10,930 B | A | view · diff |
| v2.1.0 | 2026-06-16 | ceeea9d | 11,139 B | A | view · diff |
| v2.1.0 | 2026-04-17 | 3faaf97 | 11,141 B | A | view · diff |
| v2.0.0 | 2026-04-13 | 2593d7c | 15,891 B | A | view · diff |
| git:20260319.0905165 | 2026-03-19 | 0905165 | 12,038 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 (10930 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
akillness/jeo-skills · 52 stars · license none declared · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zozibu3rat5wzfrk GET https://markdownregistry.com/api/v1/resolve?ref=akillness/jeo-skills/deployment-automation GET https://markdownregistry.com/api/v1/blob/7a6a895765ea89a3cdcc6221b7a56b2cf63c9f57fcb5468af2367ea77914b9b9
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.