OmniRoute Backup and Sync CLI
diegosouzapw/OmniRoute
Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.
Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work.
Install Business Continuity And Resilience
$ npx skills add cbrock84/headcount --skill business-continuity-and-resilience -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount business-continuity-and-resilience --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/operations/skills/business-continuity-and-resilience .claude/skills/business-continuity-and-resilience && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "business-continuity-and-resilience" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/business-continuity-and-resilience into .claude/skills/business-continuity-and-resilience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "business-continuity-and-resilience", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/business-continuity-and-resilienceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cbrock84/headcount --skill business-continuity-and-resilience -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount business-continuity-and-resilience --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/operations/skills/business-continuity-and-resilience .agents/skills/business-continuity-and-resilience && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "business-continuity-and-resilience" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/business-continuity-and-resilience into .agents/skills/business-continuity-and-resilience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "business-continuity-and-resilience", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill business-continuity-and-resilience -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount business-continuity-and-resilience --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/operations/skills/business-continuity-and-resilience .cursor/skills/business-continuity-and-resilience && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "business-continuity-and-resilience" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/business-continuity-and-resilience into .cursor/skills/business-continuity-and-resilience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "business-continuity-and-resilience", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cbrock84/headcount.git --path plugins/operations/skills/business-continuity-and-resilience--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cbrock84/headcount --skill business-continuity-and-resilience -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount business-continuity-and-resilience --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/operations/skills/business-continuity-and-resilience .gemini/skills/business-continuity-and-resilience && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "business-continuity-and-resilience" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/business-continuity-and-resilience into .gemini/skills/business-continuity-and-resilience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "business-continuity-and-resilience", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cbrock84/headcount business-continuity-and-resilienceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cbrock84/headcount --skill business-continuity-and-resilience -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/operations/skills/business-continuity-and-resilience .github/skills/business-continuity-and-resilience && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "business-continuity-and-resilience" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/business-continuity-and-resilience into .github/skills/business-continuity-and-resilience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "business-continuity-and-resilience", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill business-continuity-and-resilience -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cbrock84/headcount business-continuity-and-resilience --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/operations/skills/business-continuity-and-resilience .opencode/skills/business-continuity-and-resilience && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "business-continuity-and-resilience" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/operations/skills/business-continuity-and-resilience into .opencode/skills/business-continuity-and-resilience/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "business-continuity-and-resilience", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
business-continuity-and-resilience- GitHub stars
- 2k
- Token cost
- ~1k tokens
- SKILL.md length
- 605 words
- Files
- 2 (incl. references)
- Skills in repo
- 178
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work.
- Works in 3 steps: Walkthrough — read it aloud together and… → Tabletop — inject a scenario and make… → Live failover — actually run on the…
- Tasks that involve Backup and disaster recovery
- SKILL.md covers Start with impact, not systems, Plans people can follow badly, Exercises and Concentration risk, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Business Continuity And Resilience is an agent skill from cbrock84/headcount. 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.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).
It sits in DevOps & Cloud, covering Backup and disaster recovery. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.
When your agent uses it
- Tasks that involve Backup and disaster recovery
Example prompts
- “Use the business-continuity-and-resilience skill to plan for operating through disruption — impact analysis, recovery objectives, continuity plans…”
- “/business-continuity-and-resilience”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Walkthrough — read it aloud together and find the steps nobody can actually perform.
- Tabletop — inject a scenario and make the decisions under time pressure.
- Live failover — actually run on the alternate path, in production, with the real people.
What it can do on your machine
Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Business Continuity And Resilience loads about 1k tokens when it runs, and up to ~1.5k if it reads all its reference files. Until then it costs about 89 tokens; SKILL.md has 605 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 605 words, ~1,043 tokens.
Download SKILL.mdSave it as
.claude/skills/business-continuity-and-resilience/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- business-continuity-and-resilience
- description
- 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.
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
A continuity plan is read by a stressed person at 03:00 who did not write it. Optimize for that reader: named roles rather than names, decision authority stated explicitly, and the first three actions on the first page.
Include what to do when the plan's assumptions fail — the alternate site is also affected, the key person is unreachable, the supplier is not answering. Plans that only handle the anticipated failure handle almost nothing.
Exercises
Untested plans are documents, not capabilities. Escalate the rigour:
- Walkthrough — read it aloud together and find the steps nobody can actually perform.
- Tabletop — inject a scenario and make the decisions under time pressure.
- Live failover — actually run on the alternate path, in production, with the real people.
The exercise produces findings or it was theater. Track them as work with owners and dates, and re-run the scenario that failed rather than a fresh one, so improvement is demonstrable.
Concentration risk
Resilience fails where dependencies converge invisibly: three suppliers who all sit on one cloud region, redundant network paths in the same physical duct, a manual workaround that requires a system you have just lost. Map dependencies to the point where they stop being yours, and check whether the redundancy is real or just contractual.
Show full SKILL.md (219 more words)Show less
Sources
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
Tooling
Continuity and crisis management platforms: Fusion Framework, Castellan, Riskonnect, and similar. They hold the impact analysis, the plans, and the exercise record in one place, and they are worth buying at the point where the plans are too many for one person to keep current.
Mass notification: Everbridge, AlertMedia, and similar — the capability being bought is reaching people when your own email and chat are the thing that is down, which is the scenario a plan stored only in those systems fails.
Keep an offline copy of the plan and the contact list. Every organization that has run a real incident has a story about the plan being inside the system that was unavailable.
Never
- Set an RTO without the process owner agreeing to what it costs.
- Count a plan as tested because it was reviewed.
- Treat a backup as continuity — an unrestored backup is an untested assumption.
- Write a plan whose first step requires the system that has just failed.
© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in plugins/operations/skills/business-continuity-and-resilience of cbrock84/headcount.
- SKILL.md
- references/sources.md
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Business Continuity And Resilience next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Business Continuity And Resilience this skillcbrock84/headcount | 2k | — | ~1k | Automated safety check: Pass | MIT | |
| OmniRoute Backup and Sync CLIdiegosouzapw/OmniRoute | 75k | — | ~948 | Automated safety check: Pass | MIT | |
| Pymobiledevice3 Device Operatordoronz88/pymobiledevice3 | 2.9k | — | ~1.8k | Automated safety check: Notes | GPL-3.0 | |
| Myclaw BackupLeoYeAI/openclaw-backup | 659 | — | ~1.8k | Automated safety check: Pass | MIT | |
| OmniRoute Database Backupsdiegosouzapw/OmniRoute | 75k | — | ~395 | Automated safety check: Pass | MIT | |
| Tempsgotempsh/temps | 833 | — | ~2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Pymobiledevice3 Device Operator
doronz88/pymobiledevice3
Operate iOS and iPadOS devices with pymobiledevice3, from a local checkout or straight from PyPI via uvx on a fresh workstation.
Myclaw Backup
LeoYeAI/openclaw-backup
Backup and restore all OpenClaw configuration, agent memory, skills, and workspace data.
OmniRoute Database Backups
diegosouzapw/OmniRoute
Trigger system backups, restore from backup files, and manage the SQLite database lifecycle. Supports export, import, and incremental snapshot strategies.
Temps
gotempsh/temps
Manage, deploy, operate, and instrument applications with Temps.
Hermes Offsite Backup
OnlyTerp/hermes-optimization-guide
Set up encrypted off-machine Hermes backups. An agent skill from OnlyTerp/hermes-optimization-guide.
More from cbrock84/headcount
All 178 skills in this repoAgent Hierarchy
cbrock84/headcount
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…
Access And Identity
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
Account Based Marketing
cbrock84/headcount
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…
Activation
cbrock84/headcount
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.
AI ML Governance
cbrock84/headcount
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.
AI Research Analyst
cbrock84/headcount
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.
Related
Categories
Questions about Business Continuity And Resilience
What does Business Continuity And Resilience do?
Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. Business Continuity And Resilience is an agent skill from cbrock84/headcount. Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work.
When should I use Business Continuity And Resilience?
Business Continuity And Resilience fits situations like: tasks that involve Backup and disaster recovery.
How do I install Business Continuity And Resilience in Claude Code?
Run `npx skills add cbrock84/headcount --skill business-continuity-and-resilience -a claude-code`. Or copy the skill folder (plugins/operations/skills/business-continuity-and-resilience in cbrock84/headcount) into .claude/skills/business-continuity-and-resilience in your project. Claude Code loads it when a task matches its description.
How do I install Business Continuity And Resilience in Codex?
Run `npx skills add cbrock84/headcount --skill business-continuity-and-resilience -a codex`. Or copy the skill folder (plugins/operations/skills/business-continuity-and-resilience in cbrock84/headcount) into .agents/skills/business-continuity-and-resilience in your project. Codex loads it when a task matches its description.
Can I use Business Continuity And Resilience in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill business-continuity-and-resilience -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/business-continuity-and-resilience, .gemini/skills/business-continuity-and-resilience, .github/skills/business-continuity-and-resilience and .opencode/skills/business-continuity-and-resilience in your project.
What does Business Continuity And Resilience need to run?
SKILL.md names no scripts, command-line tools or credentials: Business Continuity And Resilience is instructions for the agent only.
Does Business Continuity And Resilience access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Business Continuity And Resilience safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Business Continuity And Resilience use?
Business Continuity And Resilience is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Business Continuity And Resilience use?
About 1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 420 tokens, read only when the agent opens those files.
What are the alternatives to Business Continuity And Resilience?
Skills that share tags, products or a category with Business Continuity And Resilience: OmniRoute Backup and Sync CLI (diegosouzapw/OmniRoute, 75k stars), Pymobiledevice3 Device Operator (doronz88/pymobiledevice3, 2.9k stars), Myclaw Backup (LeoYeAI/openclaw-backup, 659 stars) and OmniRoute Database Backups (diegosouzapw/OmniRoute, 75k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Business Continuity And Resilience?
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.
Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.