database-administrator

Configure high availability, backups, and performance for PostgreSQL, MySQL, MongoDB, and Redis.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mikebronner/development-settings --skill database-administrator-mikebronner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-administrator
Source: https://github.com/mikebronner/development-settings/tree/main/.ai/skills/database-administrator
Command: npx skills add https://github.com/mikebronner/development-settings --skill database-administrator-mikebronner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Database environments often suffer from outages, slow queries, and fragile recovery processes due to inconsistent configurations and manual maintenance. This skill provides end-to-end guidance to design, implement, and operate robust database systems.

Core Features & Use Cases

  • High availability configuration and automated failover across PostgreSQL, MySQL, MongoDB, and Redis.
  • Automated backups, point-in-time recovery, and disaster recovery testing with runbooks.
  • Performance tuning, index optimization, and resource planning to achieve low latency and scalable workloads.
  • Monitoring, alerting, and capacity planning to maintain 99.9%+ uptime in production.
  • Cross-database administration with standardized procedures for production enablement and incident response.

Quick Start

Analyze the current database landscape and implement high-availability, backup, and performance optimization strategies.

Frequently Asked Questions about database-administrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure high availability and automated failover for PostgreSQL?

High availability for PostgreSQL requires designing automated failover mechanisms and consistent configurations to prevent outages. This involves setting up replication, monitoring cluster health, and documenting runbooks for production-grade incident response and recovery.

What is the best way to implement automated backups and point-in-time recovery for MongoDB?

Automated backups and point-in-time recovery for MongoDB ensure robust data protection against fragile manual processes. Implementing disaster recovery testing with documented runbooks verifies that restoration procedures work reliably during actual failure scenarios in production.

How do I optimize slow queries and tune performance in MySQL databases?

Performance tuning in MySQL involves index optimization and resource planning to resolve slow queries and achieve low latency. Analyzing workload patterns allows for scalable configurations that maintain high throughput as data volume grows.

Can I use a single standardized procedure for production enablement across Redis and relational databases?

Cross-database administration provides standardized procedures for production enablement across Redis, PostgreSQL, MySQL, and MongoDB. This ensures consistent security hardening, monitoring, and alerting configurations regardless of the underlying database technology.

Why does my database environment suffer from outages and fragile recovery processes?

Database outages and fragile recovery processes stem from inconsistent configurations and manual maintenance practices. Implementing automated backups, high availability configurations, and documented disaster recovery runbooks resolves these reliability issues.

How do I plan capacity and maintain 99.9% uptime in production database environments?

Maintaining 99.9%+ uptime requires capacity planning, continuous monitoring, and alerting to anticipate resource bottlenecks. Proactive performance tuning and high availability configurations ensure the database infrastructure meets production demands.