deployment-readiness SKILL.md skillA
deployment-readiness from frnkgns/gentjinskills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add frnkgns/gentjinskills/deployment-readiness@git:20260928.a142223Pins git:20260928.a142223 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- frnkgns/gentjinskills
- Path
skills/deployment-readiness/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260928.a142223, committed Sep 28, 2026
- Size
- 4,394 bytes
- Repository stars
- 7
- License
- none declared
Assess whether a project is safe to ship to production. Use when the user asks about deployment, release, production readiness, going live, launch safety, environment or config parity, CI/CD pipelines, rollback plans, migration safety before shipping, or secret and credential exposure. Also use when release or deployment-sensitive work is being finished. Delegate per-layer code correctness to the review skills; this skill owns the ship-readiness question.
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 Readiness Answer one question: is it safe to ship this to production right now? Produce an evidence-based verdict, not a reassurance. Report `READY`, `READY WITH WARNINGS`, or `BLOCKED`, then the evidence for each. ## Scope Inspect the current project and the change in front of it. Determine what actually ships: the branch, the diff, the build artifacts, the environment configuration, and the data layer. Record unrelated existing files only when the deployment touches them. Do not broaden into a general code review; use the review skills for that. ## Checks ### Build and CI - Does the project's real build command succeed from a clean state? Run it; do not assume. - Do typecheck and lint run in CI, and do they pass on the current branch? - Do tests run in CI, and are any skipped, flaky, or failing? - Are CI failures pre-existing on the base branch, or introduced by this change? Distinguish them; a pre-existing failure is a warning, not a new blocker. - Are secrets, tokens, or credentials reachable from the build context, the bundle, or the client payload? ### Environment parity …
Read the whole file at its exact version.
How to install
mdr add frnkgns/gentjinskills/deployment-readiness@sha256:5fb298a82d0090a1The line at the top of this page pins the label git:20260928.a142223, 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_kanfwxqbiizkwb34)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 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 (4394 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
frnkgns/gentjinskills · 7 stars · license none declared · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kanfwxqbiizkwb34 GET https://markdownregistry.com/api/v1/resolve?ref=frnkgns/gentjinskills/deployment-readiness GET https://markdownregistry.com/api/v1/blob/5fb298a82d0090a1fdb2b8d26eddad08862c9181f03d2b1708667ab9adeba9eb
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.
More from frnkgns/gentjinskills
Every file in frnkgns/gentjinskills