databases

Configure, tune, and manage production database engines with compliance auditing.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/iuliandita/skills --skill databases-iuliandita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: databases
Source: https://github.com/iuliandita/skills/tree/main/skills/databases
Command: npx skills add https://github.com/iuliandita/skills --skill databases-iuliandita

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the high risk of misconfiguration, performance bottlenecks, and data loss in production database environments by providing a standardized, checklist-driven approach to operations.

Core Features & Use Cases

  • Production Hardening: Enforces security baselines like SCRAM-SHA-256, TLS, and strict mode for PostgreSQL, MongoDB, MySQL, and MSSQL.
  • Performance Optimization: Provides structured workflows for query plan analysis, index tuning, and connection pool sizing.
  • Migration Safety: Offers battle-tested patterns for zero-downtime schema changes and cross-engine migrations.

Quick Start

Use the databases skill to analyze the provided query plan and suggest an indexing strategy for the slow-running orders table.

Frequently Asked Questions about databases

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

FAQPage Schema
How do I optimize PostgreSQL query performance and tune indexes for slow tables?

To optimize PostgreSQL query performance, analyze the query execution plan and apply structured workflows for index tuning and connection pool sizing. This approach targets slow-running tables by evaluating execution plans to suggest effective indexing strategies.

What is the best way to plan a zero-downtime database migration across different engines?

Zero-downtime database migration uses battle-tested patterns for schema changes and cross-engine transfers between PostgreSQL, MongoDB, MySQL, and MSSQL. This ensures continuous availability and data integrity during complex operational migrations.

How do I harden MongoDB and MySQL production databases for PCI-DSS 4.0 compliance?

Hardening MongoDB and MySQL for PCI-DSS 4.0 compliance involves enforcing security baselines including SCRAM-SHA-256, TLS, and strict mode configurations. This enforces strict security and durability standards across all generated database configuration changes.

Does this database configuration approach support idempotent schema design operations?

Yes, this database configuration approach requires strict adherence to idempotency standards for all generated SQL and configuration changes. This ensures repeated schema design operations yield consistent results without risking data loss or unexpected side effects.

Can I use this skill for MSSQL connection pool sizing and performance bottlenecks?

Yes, you can use this for MSSQL connection pool sizing and performance bottlenecks. It provides structured workflows for query plan analysis and performance optimization across PostgreSQL, MongoDB, MySQL, and MSSQL production database environments.

Why does production database hardening require strict security and durability standards?

Production database hardening requires strict security and durability standards to mitigate the high risk of misconfiguration, performance bottlenecks, and data loss. A standardized checklist-driven approach ensures safe operations across complex database engines.