system-design-resilience-ops skillA
system-design-resilience-ops is agent-read markdown (skill) from hoangnguyen0403/agent-skills-standard: Make a design survivable and operable: eliminate single points of failure, pick failover topology, set RPO/RTO, define readiness signals and observability, choose a deployment and rollback strategy. Use when reviewing availability, planning DR, or deciding rollout mechanics..
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
# Resilience and Operations ## **Priority: P1 (HIGH)** A design is not done until its failure and its rollout are designed. ## SPOF Elimination - Walk every component and ask what happens when exactly one instance dies, then when the whole zone dies. - Any component with one instance, one writer, or one shared config plane is a single point of failure. Name it or remove it. - Redundancy only helps when failure modes are independent: shared credentials, shared config, and a shared control plane cancel the benefit. - Blast radius: state which users or flows are affected per component failure, and cap it with cells, bulkheads, or per-tenant quotas. ## Failover and Recovery | Topology | Recovery time | Cost | Fits | | --- | --- | --- | --- | | Single region, multi-AZ | Minutes, automatic | Low | Most products | | Active-passive across regions | Minutes to hours, drill-dependent | Medium | Regulated or high-value flows | | Active-active across regions | Seconds | High | Global low-latency, conflict-tolerant data | - Set **RPO** (tolerable data loss) and **RTO** (tolerable downtime) as numbers before choosing a topology; the numbers pick the topology, not the reverse. …
Read the whole file at its exact version.
How to install
mdr add hoangnguyen0403/agent-skills-standard/system-design-resilience-ops@git:20260830.00e03f4mdr add hoangnguyen0403/agent-skills-standard/system-design-resilience-ops@sha256:0d9f714d908bad27Pin 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_jgcshms6wzfdt5rj)
1 badge views in 30 days
Versions
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 (3608 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
hoangnguyen0403/agent-skills-standard · 571 stars · license MIT · pushed 2026-09-24 · branch develop
API
GET https://markdownregistry.com/api/v1/artifacts/art_jgcshms6wzfdt5rj GET https://markdownregistry.com/api/v1/resolve?ref=hoangnguyen0403/agent-skills-standard/system-design-resilience-ops GET https://markdownregistry.com/api/v1/blob/0d9f714d908bad27b6807e19d389b9dfe606e49c57477bd721a9e28fecd4b36e
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.
More from hoangnguyen0403/agent-skills-standard
Every file in hoangnguyen0403/agent-skills-standard