Skip to main content
skill CX Codex

cli-backup-sync — Claude Code skill: Anthropic backups

A skill for driving Anthropic backups from the terminal: incremental snapshots, cloud sync, schedules and restore from archive files.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add cheaper-inference/OmniRoute --skill cli-backup-sync -a claude-code
Open on GitHub

What cli-backup-sync does

The skill hands your agent a map of the Anthropic CLI commands that deal with backups. Through it you can fire a one-off snapshot, check the status of recent copies, turn a schedule on or off, and restore from an archive by id.

Under the hood it covers the omniroute backup and omniroute sync subcommands. backup create takes --name, --cloud, --encrypt, --key-file, --exclude and --retention; backup enable takes --cron, --cloud, --encrypt and --retention. Restores go through omniroute backup restore [backupId], and --list shows what is available. For sync there is sync push, sync pull [outPath], sync bundle <outPath>, sync import <bundlePath> with --dry-run, plus token handling via sync tokens, sync create and sync revoke <id>.

The CLI itself is a separate install: npm install -g omniroute, or run it with npx omniroute. Without that package the skill has nothing to call, since every command shells out to omniroute. A restore overwrites data, so run omniroute backup restore --list first and confirm you picked the right snapshot.

What it helps with

  • take an incremental backup of Anthropic data with one command
  • set up automatic snapshots on a cron schedule
  • push an archive to cloud storage and encrypt it with a key file
  • restore state from a specific archive by id
  • issue a sync token with a limited lifetime for another machine

Example prompts for the agent

  • Back up Anthropic with encryption and upload it to the cloud
  • Show the status of recent backups and list the available archives
  • Restore from an archive, but list the copies first

How to install cli-backup-sync

1Skills CLI (Vercel)

npx skills add cheaper-inference/OmniRoute --skill cli-backup-sync -a claude-code

2Manually: put the files in place

~/.claude/skills/cli-backup-sync/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/cli-backup-sync/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about cli-backup-sync

How do I install cli-backup-sync in Claude Code?

Run npx skills add cheaper-inference/OmniRoute --skill cli-backup-sync -a claude-code, then check that the file landed at ~/.claude/skills/cli-backup-sync/SKILL.md.

What does cli-backup-sync do?

It tells the agent how to use Anthropic's backup commands: creating snapshots, syncing to cloud storage, managing schedules and restoring from archives.

What do I need for the skill to work?

The Anthropic CLI installed: npm install -g omniroute, or run it through npx omniroute. Encryption needs a key file passed with --key-file.

Source text

SKILL.md · MIT
---
name: cli-backup-sync
description: Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.
---
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->

## Overview

Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.

## Quick install

```bash
npm install -g omniroute   # or: npx omniroute
omniroute --version
```

## Subcommands

### `backup`

**Example:**

```bash
omniroute backup
```

### `backup create`

**Flags:**

- `--name <name>`
- `--cloud`
- `--encrypt`
- `--key-file <path>`
- `--exclude <pattern>`
- `--retention <n>`

**Example:**

```bash
omniroute backup create
```

### `backup auto`

**Example:**

```bash
omniroute backup auto
```

### `backup enable`

**Flags:**

- `--cron <expr>`
- `--cloud`
- `--encrypt`
- `--retention <n>`

**Example:**

```bash
omniroute backup enable
```

### `backup disable`

**Example:**

```bash
omniroute backup disable
```

### `backup status`

**Example:**

```bash
omniroute backup status
```

### `backup restore [backupId]`

**Flags:**

- `--list`
- `--yes`

**Example:**

```bash
omniroute backup restore [backupId]
```

### `task`

**Example:**

```bash
omniroute task
```

### `cloud create`

**Flags:**

- `--title <t>`
- `--prompt <p>`
- `--prompt-file <path>`
- `--repo <url>`
- `--branch <b>`
- `--metadata <json>`

**Example:**

```bash
omniroute cloud create
```

### `cloud list`

**Flags:**

- `--status <s>`
- `--limit <n>`

**Example:**

```bash
omniroute cloud list
```

### `cloud get <taskId>`

**Example:**

```bash
omniroute cloud get <taskId>
```

### `cloud status <taskId>`

**Example:**

```bash
omniroute cloud status <taskId>
```

### `cloud cancel <taskId>`

**Flags:**

- `--yes`

**Example:**

```bash
omniroute cloud cancel <taskId>
```

### `cloud approve <taskId>`

**Example:**

```bash
omniroute cloud approve <taskId>
```

### `cloud message <taskId> <message>`

**Example:**

```bash
omniroute cloud message <taskId> <message>
```

### `cloud sources <taskId>`

**Example:**

```bash
omniroute cloud sources <taskId>
```

### `cloud cloud`

**Example:**

```bash
omniroute cloud cloud
```

### `cloud agents`

**Example:**

```bash
omniroute cloud agents
```

### `cloud auth`

**Flags:**

- `--no-browser`
- `--timeout <ms>`

**Example:**

```bash
omniroute cloud auth
```

### `sync`

**Example:**

```bash
omniroute sync
```

### `sync push`

**Example:**

```bash
omniroute sync push
```

### `sync pull [outPath]`

**Example:**

```bash
omniroute sync pull omniroute-export.tar.gz
```

### `sync bundle <outPath>`

**Flags:**

- `--token <syncToken>`

**Example:**

```bash
omniroute sync bundle <outPath>
```

### `sync import <bundlePath>`

**Flags:**

- `--dry-run`

**Example:**

```bash
omniroute sync import <bundlePath>
```

### `sync initialize`

**Example:**

```bash
omniroute sync initialize
```

### `sync tokens`

**Example:**

```bash
omniroute sync tokens
```

### `sync list`

**Example:**

```bash
omniroute sync list
```

### `sync create`

**Flags:**

- `--name <n>`
- `--scope <s>`
- `--ttl <duration>`

**Example:**

```bash
omniroute sync create
```

### `sync revoke <id>`

**Flags:**

- `--yes`

**Example:**

```bash
omniroute sync revoke <id>
```

### `sync status`

**Example:**

```bash
omniroute sync status
```

© cheaper-inference · MIT · cheaper-inference/OmniRoute

Similar skills

All skills for DevOps and infrastructure →

From the same set45

cli-chat Sends completions to OmniRoute chat models from the terminal, streams responses, and starts an interactive REPL session. CX Codex +1 970installs omni-cli-tools Manages CLI tool integrations via the OmniRoute API. It helps configure tool profiles, inspect runtime statuses, and automate CLI plugin settings. CX Codex +1 982installs omni-api-keys This skill creates, lists, rotates and revokes Anthropic API keys, and sets per-key scopes and limits. Useful when keys are handed out from inside an agent. CX Codex +1 966installs omni-agents-a2a Skill for agent-to-agent interaction via JSON-RPC 2.0 protocol. Agents discover each other, pick optimal models by cost and capabilities, check quotas, and monitor system health. CX Codex +1 977installs cli-compression Configures and tests prompt compression from the CLI. Useful for adjusting RTK filters and previewing prompt outputs before inference. CX Codex +1 976installs cli-resilience A skill that hands the agent the OmniRoute CLI commands for breaker state, cooldowns and quota checks, so a stuck provider can be reset from the terminal. CX Codex +1 976installs cli-plugins-skills Hands the agent the omniroute command set for skills, plugins and persistent memory. Useful when you want to install and test skills without leaving the session. CX Codex +1 963installs omni-version-manager Installs, starts, restarts, and monitors embedded OmniRoute services like 9Router and CLIProxyAPI via dedicated API endpoints. CX Codex +1 975installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor