index-optimization
/index-optimization
Reviews and improves indexing for changed data paths. Use when a request adds filters, sorts, joins, uniqueness rules or query-heavy flows that depend on index coverage.
- Author
- eliyce ↗
- Repository
- paqad-ai ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 8
- Scripts
- 2
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 2 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/lint-output.sh, scripts/scan-query-shapes.sh
What it does and when to use it
Reviews and improves indexing for changed data paths. Use when a request adds filters, sorts, joins, uniqueness rules or query-heavy flows that depend on index coverage.
Original author description
Reviews and improves indexing for changed data paths. Use when a request adds filters, sorts, joins, uniqueness rules or query-heavy flows that depend on index coverage.
How it works
- What It Does
- Use This When
- Inputs
- Procedure
- Output Contract
- Escalate / Stop Conditions
- Resources
SKILL.md preview
--- name: index-optimization description: 'Reviews and improves indexing for changed data paths. Use when a request adds filters, sorts, joins, uniqueness rules or query-heavy flows that depend on index coverage.' metadata: model_tier: reasoning cacheable: 'true' output_format: markdown paqad-meta: skill.meta.yaml --- ## What It Does Evaluates whether changed query paths have the right supporting indexes and explains tradeoffs without drifting into speculative indexing unrelated to the current request. ## Use This When When a request introduces new filters, sorts, joins, uniqueness rules, or query-heavy flows that depend on index coverage. ## Inputs - Read the changed query paths, migrations, and existing index docs first. - Read `runtime/capabilities/coding/checklists/database-review-20pt.md` and `references/index-review-guide.md` before evaluating changes. - Read any query inventory or performance notes tied to the affected module. ## Procedure 1. Run `scripts/scan-query-shapes.sh <files...>` to surface query patterns implying index requirements. 2. Cross-reference each shape with `assets/index-rules.txt` to know which index shape actually serves it. 3. Audit existing index docs for redundancy and ordering against those shapes. 4. Bucket findings into Correctness / Migration Safety / Performance per `assets/output.template.md`. 5. Validate with `scripts/lint-output.sh`. Recommend only indexes that serve the changed behavior or a directly adjacent hot path, no speculative. ## Output Contract - Return sections named `Correctness Risks`, `Migration Safety Risks`, and `Performance Risks`. - For each item, name the query path or index and the reason it is risky or recommended. - If no changes are needed, state `Performance Risks: none` and keep the other buckets explicit. ## Escalate / Stop Conditions - Ask when workload shape, row volume, or hot-path expectations are missing and materially change the recommendation. - Warn when an index recommendation would meaningfully increase write cost or migration risk. - Do not suggest speculative indexes without a concrete changed access pattern. ## Resources - `references/index-review-guide.md` - `scripts/scan-query-shapes.sh` - `scripts/lint-output.sh` - `assets/output.template.md` - `assets/index-rules.txt` - `runtime/capabilities/coding/checklists/database-review-20pt.md` - `agents/openai.yaml`
Files in this package (8)
- SKILL.md 2 KB
- skill.meta.yaml 1 KB
- agents/openai.yaml 1 KB
- assets/index-rules.txt 1 KB
- assets/output.template.md 1 KB
- references/index-review-guide.md 1 KB
- scripts/lint-output.sh 1 KB
- scripts/scan-query-shapes.sh 1 KB
Versions
The database has no other skills named index-optimization.
Database snapshot: 13.11.2026 · package version c7f7a39382a9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100mongodb-query-optimizer
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do… - 100mongodb-query-optimizer
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: \"How do I optimize this query?\", \"How do I index this?\", \"Why is this query slow?\", \"Can you fix my slow queries?\", \"What are the slow queries on my… - 95documentdb-query-optimizer
Help with DocumentDB/MongoDB query optimization and indexing for Azure DocumentDB. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", etc. Do not invoke… - 100ef-index-advisor
Recommend database indexes for EF Core entities based on how they're actually queried — filters, joins, ordering, and uniqueness — and generate the HasIndex configuration. Use this skill whenever the user wants index recommendations, asks why a query is slow due to a missing… - 100orchardcore-query-indexing
Works with OrchardCore queries and indexing — SQL/Lucene/Elasticsearch queries, full-text index profiles, content part/field index handlers, and search. Use when the user needs to define a query, index content for search, write an index handler, register an indexing source, or… - 100query-optimization
Diagnose and optimize existing slow SQL queries using execution plans, indexing strategies, query rewriting, and ORM tuning. Use when the user provides a query, performance symptom, or EXPLAIN plan; use sql-query-generation when creating a new query from requirements.