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.
Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work.
Install Backup And Recovery
$ npx skills add cbrock84/headcount --skill backup-and-recovery -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount backup-and-recovery --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/it-operations/skills/backup-and-recovery .claude/skills/backup-and-recovery && 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 "backup-and-recovery" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/it-operations/skills/backup-and-recovery into .claude/skills/backup-and-recovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backup-and-recovery", 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/it-operations/skills/backup-and-recoveryType 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 backup-and-recovery -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount backup-and-recovery --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/it-operations/skills/backup-and-recovery .agents/skills/backup-and-recovery && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "backup-and-recovery" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/it-operations/skills/backup-and-recovery into .agents/skills/backup-and-recovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backup-and-recovery", 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 backup-and-recovery -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount backup-and-recovery --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/it-operations/skills/backup-and-recovery .cursor/skills/backup-and-recovery && 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 "backup-and-recovery" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/it-operations/skills/backup-and-recovery into .cursor/skills/backup-and-recovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backup-and-recovery", 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/it-operations/skills/backup-and-recovery--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 backup-and-recovery -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount backup-and-recovery --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/it-operations/skills/backup-and-recovery .gemini/skills/backup-and-recovery && 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 "backup-and-recovery" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/it-operations/skills/backup-and-recovery into .gemini/skills/backup-and-recovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backup-and-recovery", 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 backup-and-recoveryInstalls 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 backup-and-recovery -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/it-operations/skills/backup-and-recovery .github/skills/backup-and-recovery && 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 "backup-and-recovery" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/it-operations/skills/backup-and-recovery into .github/skills/backup-and-recovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backup-and-recovery", 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 backup-and-recovery -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 backup-and-recovery --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/it-operations/skills/backup-and-recovery .opencode/skills/backup-and-recovery && 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 "backup-and-recovery" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/it-operations/skills/backup-and-recovery into .opencode/skills/backup-and-recovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "backup-and-recovery", 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
backup-and-recovery- GitHub stars
- 2k
- Token cost
- ~985 tokens
- SKILL.md length
- 542 words
- Files
- 2 (incl. references)
- Skills in repo
- 178
- Repo updated
- First seen
- Licence
- MIT
At a glance
Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work.
- Tasks that involve Backup and disaster recovery
- SKILL.md covers Coverage is where it fails first, The 3-2-1 shape, and why the…, Retention is a policy… and Test restores, or you have…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Backup And Recovery is an agent skill from cbrock84/headcount. Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Use this to design a backup regime, verify restores, plan retention, protect backups from ransomware, or recover from data loss.
Its SKILL.md is about 990 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 backup-and-recovery skill to protect and restores data — backup coverage and scope, retention, immutability against ransomware, and proving…”
- “/backup-and-recovery”
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
Backup And Recovery loads about 985 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 71 tokens; SKILL.md has 542 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). 542 words, ~985 tokens.
Download SKILL.mdSave it as
.claude/skills/backup-and-recovery/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- backup-and-recovery
- description
- Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Use this to design a backup regime, verify restores, plan retention, protect backups from ransomware, or recover from data loss.
Backup and recovery
Nobody wants backups; they want restores. The distinction is not pedantic — organizations discover the difference during the only event that matters.
Recovery objectives and which processes must survive are set by
operations:business-continuity-and-resilience. This skill delivers against them.
Coverage is where it fails first
Most backup gaps are things nobody thought to include: a database somebody stood up outside the standard process, configuration that only exists in a running system, data in a SaaS platform assumed to be the vendor's responsibility, or a developer's machine holding the only copy of something.
Reconcile backup coverage against the asset register from
it-operations:it-asset-management on a cadence and treat the difference as a finding. An untested
assumption of coverage is the normal state of affairs.
Note that SaaS providers protect against their failures, not against your deletion or a malicious insider. Read what the contract actually commits to, rather than what the marketing implies.
The 3-2-1 shape, and why the offline copy matters
Three copies, two media or platforms, one off-site — and, since ransomware, one immutable or offline.
Modern ransomware deliberately targets backups first, using the credentials it found on the way in. A backup system reachable with production credentials will be encrypted alongside production. Immutable storage or genuinely offline copies are what survive this, and it is the difference between an outage and an extinction event.
Retention is a policy decision, not a storage one
Retention has to satisfy operational recovery, legal and regulatory obligations, and data protection
requirements — which pull in opposite directions. Data protection law obliges deletion of personal
data you no longer have a basis to keep, and indefinite backup retention conflicts with that
directly. Settle it with legal-risk:privacy-and-data-protection.
Know how you would satisfy a deletion request that touches backups, before one arrives.
Show full SKILL.md (247 more words)Show less
Test restores, or you have nothing
A backup job reporting success proves a file was written. It says nothing about whether the data is complete, uncorrupted, or restorable in a usable time.
Test on a schedule, restore to a separate environment, and verify the application actually works on the restored data rather than that the bytes arrived. Record how long it took — that measurement is the only honest input to an RTO, and it is invariably longer than assumed.
Test the full-scale case at least annually. Restoring one file proves the mechanism; restoring the system proves the plan.
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
Backup platforms: Veeam, Rubrik, Cohesity, Commvault, Acronis, and similar.
SaaS data is the gap people miss. Microsoft 365, Google Workspace, and Salesforce retain for a short window and no longer; Veeam, Druva, AvePoint, Keepit, and similar cover it.
The tool is not the control. An untested restore is not a backup, whatever the console reports.
Never
- Report backup health from job success rather than tested restores.
- Leave backups reachable with production credentials.
- Set retention without reconciling legal obligation against deletion duty.
- Quote an RTO you have not measured by actually restoring.
© 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/it-operations/skills/backup-and-recovery of cbrock84/headcount.
- SKILL.md
- references/sources.md
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Backup And Recovery 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 |
|---|---|---|---|---|---|---|
| Backup And Recovery this skillcbrock84/headcount | 2k | — | ~985 | 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 Backup And Recovery
What does Backup And Recovery do?
Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Backup And Recovery is an agent skill from cbrock84/headcount. Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work.
When should I use Backup And Recovery?
Backup And Recovery fits situations like: tasks that involve Backup and disaster recovery.
How do I install Backup And Recovery in Claude Code?
Run `npx skills add cbrock84/headcount --skill backup-and-recovery -a claude-code`. Or copy the skill folder (plugins/it-operations/skills/backup-and-recovery in cbrock84/headcount) into .claude/skills/backup-and-recovery in your project. Claude Code loads it when a task matches its description.
How do I install Backup And Recovery in Codex?
Run `npx skills add cbrock84/headcount --skill backup-and-recovery -a codex`. Or copy the skill folder (plugins/it-operations/skills/backup-and-recovery in cbrock84/headcount) into .agents/skills/backup-and-recovery in your project. Codex loads it when a task matches its description.
Can I use Backup And Recovery 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 backup-and-recovery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/backup-and-recovery, .gemini/skills/backup-and-recovery, .github/skills/backup-and-recovery and .opencode/skills/backup-and-recovery in your project.
What does Backup And Recovery need to run?
SKILL.md names no scripts, command-line tools or credentials: Backup And Recovery is instructions for the agent only.
Does Backup And Recovery 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 Backup And Recovery 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 Backup And Recovery use?
Backup And Recovery 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 Backup And Recovery use?
About 985 tokens (SKILL.md is roughly 3.9k 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 229 tokens, read only when the agent opens those files.
What are the alternatives to Backup And Recovery?
Skills that share tags, products or a category with Backup And Recovery: 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 Backup And Recovery?
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.