indexes

Analyze executed queries to identify missing database indexes and estimate performance impact.

5|2|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/thoreinstein/opencode-config --skill indexes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: indexes
Source: https://github.com/thoreinstein/opencode-config/tree/main/skill/indexes
Command: npx skills add https://github.com/thoreinstein/opencode-config --skill indexes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Database query performance is often limited by missing or poorly targeted indexes. This Skill analyzes queries across the codebase and identifies where indexes would improve read performance, providing actionable recommendations.

Core Features & Use Cases

  • Scan queries and workload patterns to detect missing indexes.
  • Estimate performance impact and propose concrete index definitions.
  • Use cases include accelerating slow reads, multi-table joins, and analytics workloads.

Quick Start

Run the indexes skill against your target database or codebase to generate an index recommendations report.

Frequently Asked Questions about indexes

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

FAQPage Schema
How do I find missing database indexes to improve query performance?

To find missing database indexes and improve query performance, you analyze executed query workloads and schema metadata to detect suboptimal indexes and generate concrete index recommendations with associated impact metrics.

Can I analyze SQL query performance for specific slow reads instead of a full database scan?

Yes, you can analyze SQL query performance by running a targeted scan against specific query sets rather than a full-database scan, allowing you to optimize slow reads, multi-table joins, and analytics workloads directly.

What database metadata is required to generate SQL index recommendations?

Generating SQL index recommendations requires access to query workloads and schema metadata, which the analysis uses to evaluate performance characteristics and propose actionable index definitions.

Does index analysis work across different relational databases in my codebase?

Yes, index analysis applies to relational databases across both codebases and production environments, detecting missing or suboptimal indexes by evaluating query patterns universally.

What is the best way to optimize multi-table joins and analytics workloads experiencing slow read performance?

The best way to optimize multi-table joins and analytics workloads with slow read performance is to scan query patterns to identify missing indexes and apply the proposed concrete index definitions to accelerate data retrieval.

Are there limitations to consider when relying on automated index recommendations for query optimization?

A limitation of automated index recommendations is that the analysis requires direct access to representative query workloads and schema metadata, meaning incomplete workload data will result in inaccurate or suboptimal index guidance.