← ClaudeAtlas

comet-backuplisted

Fleet-wide backup health, failure triage and usage reports for every tenant on your Comet Server, plus the admin API calls an MSP uses day to day. Trigger phrases: `which comet backups failed last night`, `comet backup health across all tenants`, `comet storage usage per customer`, `find offline comet devices`, `re-run failed comet backups`, `use comet-backup`, `run comet-backup`.
Servosity/msp-skills · ★ 82 · AI & Automation · score 80
Install: claude install-skill Servosity/msp-skills
# Comet Backup - Claude Code Skill ## Prerequisites: Install the CLI This skill drives the `comet-backup-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first: 1. macOS / Linux: ```bash bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/comet-backup/install.sh) ``` 2. Windows (PowerShell): ```powershell iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/comet-backup/install.ps1 | iex ``` 3. Verify: `comet-backup-cli --version` 4. Ensure `~/.local/bin` (macOS / Linux) or `%LOCALAPPDATA%\Programs\msp-skills` (Windows) is on `$PATH`. The installer downloads the `comet-backup-cli` and `comet-backup-mcp` binaries into `~/.local/bin` (macOS / Linux) or `%LOCALAPPDATA%\Programs\msp-skills` (Windows). It does not register the skill with your agent and writes no MCP client config - see [mcp-install.md](./mcp-install.md) for that wire-up. If `--version` reports "command not found" after install, the runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds. Comet's console and emailed reports answer one customer at a time. Here a tenant is a Comet user account. `health` lists every protected item that failed, is overdue or never ran across all tenants; `triage` adds the error lines; `usage` breaks out storage, devices, boosters and Microsoft 365 seats per tenant; `snap