managing-database-replication
This skill enables Claude to manage database replication, failover, and high availability configurations using the database-replication-manager plugin. It is designed to assist with tasks such as setting up master-slave replication, configuring automatic failover, monitoring replication lag, and implementing read scaling. Use this skill when the user requests help with "database replication", "failover configuration", "high availability", "replication lag", or "read scaling" for databases like PostgreSQL or MySQL. The plugin facilitates both physical and logical replication strategies.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- managing-database-replication
- description
- This skill enables Claude to manage database replication, failover, and high availability configurations using the database-replication-manager plugin. It is designed to assist with tasks such as setting up master-slave replication, configuring automatic failover, monitoring replication lag, and implementing read scaling. Use this skill when the user requests help with "database replication", "failover configuration", "high availability", "replication lag", or "read scaling" for databases like PostgreSQL or MySQL. The plugin facilitates both physical and logical replication strategies.
02 资源文件 3
- 资产文件assets/README.md259 B
- 参考文档references/README.md434 B
- 脚本scripts/README.md332 B
03 SKILL.md 正文
Overview
This skill empowers Claude to automate and streamline database replication processes, ensuring high availability and data consistency across multiple database instances. It simplifies the configuration and management of complex replication topologies.
How It Works
- Initialization: The skill activates the database-replication-manager plugin upon detecting relevant keywords.
- Configuration: The skill prompts the user for database connection details, replication type (physical/logical), and desired configuration parameters (e.g., failover settings, replication lag thresholds).
- Implementation: The plugin generates and executes the necessary commands to configure database replication based on the user's specifications.
When to Use This Skill
This skill activates when you need to:
- Set up a new database replication environment.
- Configure automatic failover for a database cluster.
- Monitor replication lag and trigger alerts based on defined thresholds.
- Implement read scaling by distributing read queries across multiple replicas.
Examples
Example 1: Setting up Master-Slave Replication
User request: "Set up master-slave replication for my PostgreSQL database with automatic failover."
The skill will:
- Activate the database-replication-manager plugin.
- Guide the user through the configuration process, prompting for connection details and failover settings.
- Generate and execute the necessary PostgreSQL commands to establish master-slave replication and configure automatic failover.
Example 2: Monitoring Replication Lag
User request: "Monitor replication lag on my MySQL replica and alert me if it exceeds 5 seconds."
The skill will:
- Activate the database-replication-manager plugin.
- Configure replication lag monitoring for the specified MySQL replica.
- Set up alerts that trigger when the replication lag exceeds the defined threshold of 5 seconds.
Best Practices
- Security: Always encrypt database credentials and use secure communication channels for replication traffic.
- Monitoring: Implement comprehensive monitoring of replication status, lag, and resource utilization.
- Testing: Regularly test failover procedures to ensure they function correctly in a disaster recovery scenario.
Integration
This skill can be integrated with other monitoring and alerting tools to provide comprehensive database management capabilities. It can also be used in conjunction with infrastructure-as-code tools to automate the deployment and configuration of database replication environments.
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.