Omni Db Backups
List and export database backups. Also covers the system version, metrics and environment-repair routes.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Omni Db Backups when an AI agent needs a reusable SKILL.md workflow for this job: List and export database backups. Also covers the system version, metrics and environment-repair routes.
When not to use it
Skip Omni Db Backups when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/omni-db-backups # Save SKILL.md to ~/.claude/skills/omni-db-backups/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/omni-db-backups/SKILL.md. For a shared project, commit the folder at .claude/skills/omni-db-backups/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Omni Db Backups skill for this task: Use Omni Db Backups when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
68/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 70/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->
## Overview
List and export database backups. Also covers the system version, metrics and environment-repair routes.
## Authentication
All requests require a valid Bearer token or session cookie. Obtain a token via `POST /api/auth/login` or configure `REQUIRE_API_KEY=false` for local development.
## Endpoints
### GET /api/db-backups
List database backups
```bash curl http://localhost:20128/api/db-backups \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### PATCH /api/db-backups
Save database backup retention settings
Persists `keepLatest` / `retentionDays`. Operator-only: dashboard session, local CLI, or login disabled — the persisted values drive the automatic pruning after every backup.
```bash curl -X PATCH http://localhost:20128/api/db-backups \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/db-backups/export
GET db backups › export
```bash curl http://localhost:20128/api/db-backups/export \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/db-backups/exportAll
GET db backups › exportAll
```bash curl http://localhost:20128/api/db-backups/exportAll \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/system/env/repair
GET system › env › repair
```bash curl http://localhost:20128/api/system/env/repair \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/system/env/repair
POST system › env › repair
```bash curl -X POST http://localhost:20128/api/system/env/repair \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
### GET /api/system/metrics
Host and OmniRoute process CPU and memory
Management-tier (dashboard session or management API key) snapshot behind the home-page system metrics cards. CPU percentages are deltas since the previous call that was at least 400 ms earlier, so the first call after process start (and any call inside the 400 ms window) returns the last computed value, which is `0` before the first delta. Host values come from `os.cpus()` / `os.totalmem()` / `os.freemem()` and describe the host, not a container limit; the process CPU percentage is normalised by the host core count. Sent with `Cache-Control: no-store, no-cache, must-revalidate`.
```bash curl http://localhost:20128/api/system/metrics \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### GET /api/system/version
GET system › version
Running version, latest published version, auto-update status and npm release channel. `releaseChannel` and `channels` are additive (rail 3.8.54); `channel` keeps meaning the deployment mode used by the dashboard updater.
```bash curl http://localhost:20128/api/system/version \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" ```
### POST /api/system/version
POST system › version
```bash curl -X POST http://localhost:20128/api/system/version \ -H "Authorization: Bearer $OMNIROUTE_TOKEN" \ -H "Content-Type: application/json" \ -d '{}' ```
## Payloads
See the full OpenAPI specification at `GET /api/openapi/spec` or `docs/openapi.yaml` for detailed request/response schemas.
Intended uses
- Use Omni Db Backups when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.