Skip to content
TrustedSkillsbeta
Back to all skills

Database Backup Restore

Checked
aj-geddes·vlatest·database·MIT

Automates full or incremental database backups and restores to ensure data safety and disaster recovery.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add aj-geddes/useful-ai-prompts --skill database-backup-restore -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

aj-geddes

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned aj-geddes/useful-ai-prompts at 3f5182cfd7.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
3f5182cfd7
Manifest
skills/database-backup-restore/SKILL.md
Scanned
9 files, 363 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The database-backup-restore skill enables AI agents to execute automated backup and restore operations for relational databases. It handles the creation of snapshots, verification of data integrity, and recovery procedures to ensure business continuity.

When to use it

  • Automating daily or weekly snapshot schedules for production PostgreSQL or MySQL instances.
  • Recovering corrupted tables or lost transactions after a system crash.
  • Cloning database states for development environments without manual export/import steps.
  • Testing disaster recovery plans by simulating restoration from off-site backups.

Key capabilities

  • Initiates full and incremental backup jobs based on user-defined schedules.
  • Validates backup file integrity before confirming successful completion.
  • Executes point-in-time recovery to restore data to a specific timestamp.
  • Manages storage rotation policies for retaining historical backups.

Example prompts

  • "Create a new automated backup job for the 'sales_db' database running every night at 2 AM."
  • "Restore the 'inventory_system' database from the backup taken on January 15th at 09:00 UTC."
  • "Verify the integrity of the last completed backup file and report any corruption errors found."

Tips & gotchas

Ensure your AI agent has read/write permissions to both the source database and the designated backup storage location. Always test restore procedures in a non-production environment first to confirm data consistency before relying on them for critical recovery scenarios.