production-readiness skillA
production-readiness is agent-read markdown (skill) from fmind/dot: Assess production readiness, including operability, recovery, rollout, and support evidence..
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
# Production Readiness Decide whether the exact candidate can be operated safely. The audit produces a go/no-go recommendation; deployment, migration, and publication follow the user's existing authorization. ## Workflow 1. **Identify the candidate**: immutable revision/artifact, configuration, environment, schema/dependency versions, proposed rollout, and dirty-tree boundary. 1. **Define acceptance**: critical journeys, correctness/availability, capacity/cost, data-loss tolerance, owners, and hard stop conditions. 1. **Review the delta**: inspect security, identity, migrations, observability, recovery, support, and one-way transitions using the [detailed procedure](references/procedure.md) for the relevant risks. 1. **Qualify**: run `mise run all` against the materialized candidate and only authorized runtime checks; preserve exact evidence, failed gates, and unavailable proof. 1. **Plan recovery**: smallest reversible exposure, observation window, halt thresholds, rollback owner/mechanism, and verification after rollback. 1. **Decide**: GO, GO WITH CHANGES, or NO-GO; report blockers, evidence, remaining actions, and the highest proven state below. ## Proof Boundaries …
Read the whole file at its exact version.
How to install
mdr add fmind/dot/production-readiness@git:20260919.4491844mdr add fmind/dot/production-readiness@sha256:f8bc1289ea77cf6ePin 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.
[](https://markdownregistry.com/a/art_h7j6o2rbwq46m2sq)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260919.4491844 latest | 2026-09-19 | 4491844 | 2,964 B | A | view · diff |
| git:20260916.50d6810 | 2026-09-16 | 50d6810 | 2,964 B | A | view · diff |
| git:20260909.892d859 | 2026-09-09 | 892d859 | 2,928 B | A | view · diff |
| git:20260909.17296ea | 2026-09-09 | 17296ea | 2,776 B | A | view · diff |
| git:20260908.131d2e1 | 2026-09-08 | 131d2e1 | 2,724 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 (2964 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
fmind/dot · 9 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_h7j6o2rbwq46m2sq GET https://markdownregistry.com/api/v1/resolve?ref=fmind/dot/production-readiness GET https://markdownregistry.com/api/v1/blob/f8bc1289ea77cf6ece745319fb3627c84a5283ecd50708a94619385cb0527099
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.