sql-database

Identify and optimize database performance bottlenecks across PostgreSQL and MySQL.

16|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/JCE-Joshhh77/JCE-Opencode-Tools --skill sql-database-jce-joshhh77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sql-database
Source: https://github.com/JCE-Joshhh77/JCE-Opencode-Tools/tree/main/config/skills/sql-database
Command: npx skills add https://github.com/JCE-Joshhh77/JCE-Opencode-Tools --skill sql-database-jce-joshhh77

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SQL and database design, indexing, and migrations are error-prone without structured patterns; this skill provides proven practices to prevent slow queries, schema drift, and risky deployments.

Core Features & Use Cases

  • Schema design best practices for PostgreSQL and MySQL, including data types, constraints, normalization decisions, and future-proofing.
  • Indexing and query optimization guidance with concrete patterns for common workloads.
  • Safe migration strategies (expand/contract, concurrent indexes, zero-downtime upgrades) and rollback planning.
  • Use cases include evolving a production schema with minimal downtime, optimizing read-heavy workloads, and implementing robust data integrity rules.

Quick Start

Execute a full database health check on your PostgreSQL or MySQL instance to identify slow queries, indexing opportunities, and migration risks.

Frequently Asked Questions about sql-database

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

FAQPage Schema
How do I optimize SQL database performance for slow queries in PostgreSQL and MySQL?

To optimize SQL database performance, identify bottlenecks across queries and schemas using indexing strategies and query optimization patterns tailored for PostgreSQL and MySQL workloads to prevent slow queries.

What are the best practices for safe database schema migrations with zero downtime?

Safe database schema migrations require expand/contract patterns, concurrent indexes, and rollback planning to ensure zero-downtime upgrades and backward compatibility during production schema evolution.

How does schema design affect data integrity in relational databases?

Schema design affects data integrity by applying normalization decisions, proper data types, and constraints to future-proof PostgreSQL and MySQL databases and enforce robust data rules.

How do I run a database health check to identify indexing opportunities?

A database health check evaluates your PostgreSQL or MySQL instance to identify slow queries, indexing opportunities, and migration risks by analyzing current schema designs and query workloads.

When should I use concurrent indexes during database migrations?

Use concurrent indexes during database migrations to maintain safe concurrent operations and zero-downtime upgrades, preventing production locks when optimizing read-heavy workloads in PostgreSQL and MySQL.

What are the limitations of expand and contract migration patterns?

Expand and contract migration patterns require strict backward compatibility and multiple deployment phases, adding operational latency when evolving production schemas across PostgreSQL and MySQL databases.