implementing-backup-strategies
This skill implements backup strategies for databases and applications. It generates configuration files and setup code to ensure data protection and disaster recovery. Use this skill when the user requests to "implement backup strategy", "configure backups", "setup data recovery", or needs help with "backup automation". The skill provides production-ready configurations, best practices, and multi-platform support for database and application backups. It focuses on security and scalability.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- implementing-backup-strategies
- description
- This skill implements backup strategies for databases and applications. It generates configuration files and setup code to ensure data protection and disaster recovery. Use this skill when the user requests to "implement backup strategy", "configure backups", "setup data recovery", or needs help with "backup automation". The skill provides production-ready configurations, best practices, and multi-platform support for database and application backups. It focuses on security and scalability.
02 资源文件 3
- 资产文件assets/README.md401 B
- 参考文档references/README.md581 B
- 脚本scripts/README.md443 B
03 SKILL.md 正文
Overview
This skill empowers Claude to generate and implement robust backup strategies for databases and applications. It provides ready-to-use configurations and setup scripts, streamlining the process of data protection and disaster recovery.
How It Works
- Analyzing Requirements: The skill analyzes the user's specific requirements, including database type, application architecture, and desired backup frequency.
- Generating Configuration: Based on the requirements, the skill generates optimized configuration files for the chosen backup solution.
- Creating Setup Code: The skill creates setup code (e.g., scripts, commands) to automate the backup process and ensure its consistency.
When to Use This Skill
This skill activates when you need to:
- Implement a new backup strategy for a database or application.
- Automate existing backup processes.
- Configure backups for disaster recovery purposes.
Examples
Example 1: Setting up daily backups for a PostgreSQL database.
User request: "Implement daily backups for my PostgreSQL database named 'users_db' to an AWS S3 bucket."
The skill will:
- Generate a
pg_dumpscript configured to backup the 'users_db' database and upload it to the specified S3 bucket. - Provide instructions for scheduling the script to run daily using
cron.
Example 2: Configuring application-level backups for a Dockerized application.
User request: "Configure application-level backups for my Dockerized application. I want to backup the application's data directory every hour."
The skill will:
- Generate a Docker Compose configuration that includes a volume for the application's data directory.
- Create a backup script to copy the volume's contents to a backup location.
- Provide instructions for scheduling the backup script using a Docker container and
cron.
Best Practices
- Security: Always encrypt backup data, both in transit and at rest.
- Retention: Implement a well-defined backup retention policy to manage storage costs and meet compliance requirements.
- Testing: Regularly test backup and restore procedures to ensure their effectiveness.
Integration
This skill can be integrated with other tools and plugins, such as infrastructure-as-code tools (e.g., Terraform, CloudFormation) to automate the deployment and configuration of backup infrastructure. It can also work with monitoring tools to provide alerts on backup failures.
04 同仓库更多 Skills
Docs Research
Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).
wrappee-drift
Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API/docs, not training-data memory) and against comparable/competing wrappers. Trigger when the user says "wrappee drift" followed by a repo name, "capability audit" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth/archive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's/competitors' actual current capabilities.
modules
暂无简介
mcp-standards
Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI/CD workflows.
webapp-cua-test
Run the pre-Tauri CUA click-through test (real browser, dev stack, OCR "Connected" wait, sidebar nav walk) for a fleet MCP server repo under D:\Dev\repos. Trigger when the user says "cua webapp test" or "webapp clickthrough" followed by a repo name, asks for an e2e click-through of a webapp, or asks whether a webapp boots and connects in a real browser. Not for the installed NSIS app (that is the nsis-build skill / cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).
ship
Final release gate for a fleet MCP server repo under D:\Dev\repos -- run all quality gates, build the release artifact, verify it, commit, push, and cut a GitHub release. Trigger this whenever the user says "ship it", "ship" followed by a repo name, "release" followed by a repo name, or asks to finalize and publish work that's already been done in a repo. This is the terminal step after assfix/nsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.