business-continuity-and-resilience SKILL.md skillA
business-continuity-and-resilience from cbrock84/headcount is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cbrock84/headcount/business-continuity-and-resilience@git:20260916.0e7cd01Pins git:20260916.0e7cd01 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cbrock84/headcount
- Path
plugins/operations/skills/business-continuity-and-resilience/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260916.0e7cd01, committed Sep 16, 2026
- First version recorded
- Aug 29, 2026
- Size
- 4,196 bytes
- Repository stars
- 2,543
- License
- MIT
Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. Use this to run a business impact analysis, set RTO and RPO, write or test a continuity plan, prepare for a supplier or site failure, or answer a customer's resilience questionnaire.
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
# Business continuity and resilience Continuity is a business question wearing technical clothing. The technical restore is covered by `it-operations:backup-and-recovery`; this is about which processes must keep running, for whom, and how long you can survive without them. ## Start with impact, not systems A business impact analysis asks, per process: what breaks downstream, how fast, and who notices. Work outward from the customer-visible failure, not inward from the asset register — an inventory of systems tells you what you own, never what matters. For each critical process establish: - **Maximum tolerable outage** — the point past which the damage is not recoverable by working harder afterwards. This is a business judgment, made by the process owner, not by IT. - **RTO** — how quickly it must be back. Always shorter than someone wants to pay for. - **RPO** — how much data you can afford to lose, measured in time. An RPO of zero is a claim about spending, not about intent. RTO and RPO that were not signed by the person accountable for the process are aspirations. ## Plans people can follow badly …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/business-continuity-and-resilience@sha256:93025685bf282fc1The line at the top of this page pins the label git:20260916.0e7cd01, 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_jtmumg44k7maqhrc)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 29, 2026 and Sep 16, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.0e7cd01 latest | 2026-09-16 | 0e7cd01 | 4,196 B | A | view · diff |
| git:20260901.49e89d6 | 2026-09-01 | 49e89d6 | 3,857 B | A | view · diff |
| git:20260901.a52f5a7 | 2026-09-01 | a52f5a7 | 3,160 B | A | view · diff |
| git:20260829.2464776 | 2026-08-29 | 2464776 | 3,160 B | A | view · diff |
| git:20260829.42b4a27 | 2026-08-29 | 42b4a27 | 3,161 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 (4196 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
cbrock84/headcount · 2,543 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jtmumg44k7maqhrc GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/business-continuity-and-resilience GET https://markdownregistry.com/api/v1/blob/93025685bf282fc1a2013eec85b1400b31c796033c9f7f14938e1dbc95cd1555
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.