Database Optimizer

Optimize PostgreSQL and MySQL database performance through schema, query, and indexing analysis.

Updated Dec 18, 2025
One-click install
npx skills add https://github.com/JesusFigueroa25/SEABOT --skill database-optimizer-jesusfigueroa25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Database Optimizer
Source: https://github.com/JesusFigueroa25/SEABOT/tree/main/PROYECTO/fronted-seabot/.agents/skills/database-optimizer
Command: npx skills add https://github.com/JesusFigueroa25/SEABOT --skill database-optimizer-jesusfigueroa25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the problem of poor database performance by optimizing schema design, query execution, and indexing strategies for PostgreSQL, MySQL, and modern databases like Supabase and PlanetScale.

Core Features & Use Cases

  • Schema Optimization: Design efficient schemas with indexed foreign keys and appropriate constraints.
  • Query Optimization: Use EXPLAIN ANALYZE to interpret query plans and optimize them for performance.
  • Indexing Strategies: Implement indexing strategies for B-tree, GiST, GIN, and partial indexes.
  • Connection Pooling: Utilize connection pooling for efficient database connections.
  • Use Case: For a developer working on a high-traffic application, this Skill helps ensure that the database performs well under load and scales gracefully.

Quick Start

Analyze the performance of the 'users' table in your PostgreSQL database using the Database Optimizer skill.

Frequently Asked Questions about Database Optimizer

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

FAQPage Schema
How do I optimize PostgreSQL query performance using EXPLAIN ANALYZE?

Query tuning uses EXPLAIN ANALYZE to interpret PostgreSQL query plans and improve execution. By analyzing these plans, you can identify bottlenecks and apply indexing strategies to significantly speed up slow queries.

What is the best way to design an efficient database schema for high-traffic applications?

Efficient schema design requires indexed foreign keys and appropriate constraints to ensure databases scale gracefully under heavy load. Designing schemas this way maintains data integrity while optimizing performance for high-traffic applications.

When do I need partial indexes or GIN indexes in MySQL and PostgreSQL?

Partial indexes and GIN indexes are needed when standard B-tree indexes cannot efficiently handle specific query patterns or data types. Implementing these indexing strategies ensures complex queries return results quickly without full table scans.

Does this database optimization approach work with Supabase and PlanetScale?

Yes, this database optimization approach explicitly supports modern databases including Supabase and PlanetScale. It applies schema optimization and query tuning techniques designed for these platforms to ensure scalable performance.

Why is connection pooling necessary for my database performance?

Connection pooling is necessary to manage and reuse efficient database connections, preventing resource exhaustion under heavy load. By utilizing connection pooling, high-traffic applications maintain responsive query execution without overwhelming the database.