- Home
- Skills
- Data & Databases
- Add Database Backups Automatically
More screenshots
Works with the AI Agents you already use
Add Database Backups Automatically
Automatically add safe database backups to existing projects.
$1
Add Database Backups Automatically
Example session with this skill installed
Add nightly PostgreSQL backups to my Express SaaS app.
- Read your context and instructions
- Compiled the add database backups
Project Detected
Node.js Express SaaS application with PostgreSQL and Docker Compose
Backup Setup Added
- PostgreSQL backup script using pg_dump
- Disabled cron example for nightly execution at 02:00
- Timestamped compressed backups stored in the configurable BACKUP_DIR path
Retention and Recovery
- Added a configurable 14-day retention example with dry-run support
- Added a separate PostgreSQL restore verification script
- Restore verification uses an isolated test database
Security Controls
- Database credentials are loaded from DATABASE_URL without being printed
- Backup path validation prevents cleanup outside BACKUP_DIR
- Generated backup files use restricted local permissions
Files Modified
- scripts/backup-postgres.sh
- scripts/verify-postgres-backup.sh
- ops/cron/postgres-backup.cron.example
- docs/database-backups.md
- .env.example
Commands Executed
- bash -n scripts/backup-postgres.sh
- bash -n scripts/verify-postgres-backup.sh
- docker compose config
- bash scripts/backup-postgres.sh --dry-run
Validation Result
Script syntax, Docker configuration, environment checks, and backup dry run completed successfully. No production database was accessed and recovery was not claimed as fully verified.
How to Run
Run bash scripts/backup-postgres.sh after configuring DATABASE_URL and BACKUP_DIR. Use bash scripts/verify-postgres-backup.sh <backup-file> against an isolated local PostgreSQL instance.
Important Notes
Review the backup destination, retention period, time zone, storage permissions, and off-site storage policy before enabling the nightly schedule.
Connects securely to your tools. The creator never sees your data.
About this skill
Add Database Backups Automatically is a bounded ToolForge Labs workflow. Automatically add safe database backups to existing projects. This skill detects your database, creates backup and restore scripts, adds retention rules, protects credentials, and validates recovery using controlled local checks. ✔ PostgreSQL, MySQL, and SQLite ✔ Scheduled backup scripts ✔ Retention and cleanup rules ✔ Restore verification ✔ Secure environment configuration Perfect for SaaS apps, APIs, stores, dashboards, and production services. The skill works from supplied repository files or partial evidence, separates verified facts from assumptions, avoids invented execution claims, and provides concrete next steps plus deterministic validation where possible.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Data & Databases.
Requires local database access for restore verification. Does not support cloud-native backup services (like AWS RDS snapshots) directly. Production restoration must be done manually.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago
Permissions
Use a clean branch or controlled review workspace. Supply the relevant files, logs, configuration, traces, or evidence. Review recommendations before merge or operational action and keep secrets or destructive production actions out of the workflow.