db-query-plan-analyzer SKILL.md skillA
db-query-plan-analyzer from testland/qa is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testland/qa/db-query-plan-analyzer@git:20260728.1bce424Pins git:20260728.1bce424 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testland/qa
- Path
plugins/qa-load-testing/skills/db-query-plan-analyzer/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260728.1bce424, committed Jul 28, 2026
- First version recorded
- Jul 20, 2026
- Size
- 7,207 bytes
- Repository stars
- 11
- License
- MIT
Reads `EXPLAIN` / `EXPLAIN ANALYZE` output from PostgreSQL, MySQL, or SQLite - identifies the dominant cost (sequential scan, nested loop, sort spill, missing index, type-cast preventing index use), proposes the specific index or query rewrite to fix it, and emits the candidate `CREATE INDEX` statement. Use when load testing or production telemetry shows the database as the bottleneck and the team needs targeted query-level remediation.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# db-query-plan-analyzer ## Overview Most API perf regressions resolve to one of: 1. A new query running unindexed (sequential scan over a growing table). 2. A query joining on the wrong column type (implicit cast prevents index use). 3. A sort that doesn't fit in `work_mem` and spills to disk. 4. A query plan that started using a nested loop where a hash join would be faster (or vice versa) due to stale stats. 5. A query touching N+1 rows because of an ORM N+1 access pattern. `EXPLAIN ANALYZE` (PostgreSQL), `EXPLAIN ANALYZE` (MySQL 8.0+), or `EXPLAIN QUERY PLAN` (SQLite) reveals which case you're in. This skill reads that output and proposes the fix. The query-plan vocabulary (Sequential Scan, Index Scan, Nested Loop) comes from PostgreSQL's [Using EXPLAIN][pg-explain]. [pg-explain]: https://www.postgresql.org/docs/current/using-explain.html ## When to use - A load test showed DB-bound latency growth. - An APM tool (Datadog / New Relic / Grafana) flagged a slow query. - A production incident traced to a specific query. - An `EXPLAIN ANALYZE` was captured but the team can't tell which cost is dominant. …
Read the whole file at its exact version.
How to install
mdr add testland/qa/db-query-plan-analyzer@sha256:65c02415faee9031The line at the top of this page pins the label git:20260728.1bce424, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_u2dw4qzznhezbw4q)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jul 20, 2026 and Jul 28, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260728.1bce424 latest | 2026-07-28 | 1bce424 | 7,207 B | A | view · diff |
| git:20260725.bc7a24d | 2026-07-25 | bc7a24d | 11,251 B | A | view · diff |
| git:20260724.d4db756 | 2026-07-24 | d4db756 | 11,249 B | A | view · diff |
| git:20260720.22d020c | 2026-07-20 | 22d020c | 11,316 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7207 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
testland/qa · 11 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_u2dw4qzznhezbw4q GET https://markdownregistry.com/api/v1/resolve?ref=testland/qa/db-query-plan-analyzer GET https://markdownregistry.com/api/v1/blob/65c02415faee9031d1c78626f6f5226d76f66adb9dab3b8c783acf1ecb3258e2
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.