This is a strong, well-structured skill that provides concrete, actionable guidance for debugging slow Postgres queries via EXPLAIN ANALYZE. The phased workflow with explicit thresholds, safety constraints, and a verification step makes it highly reliable. Minor verbosity in some explanatory sections prevents a perfect conciseness score, but overall token efficiency is good.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient and avoids explaining basic concepts Claude already knows (like what SQL is), but some sections could be tightened — e.g., the buffer usage ratio explanation and some of the deferral criteria are somewhat verbose. The JSON example node is useful but borderline on necessity.	2 / 3
Actionability	Provides fully executable SQL examples (EXPLAIN ANALYZE syntax, CREATE INDEX CONCURRENTLY), specific JSON fields to inspect, concrete thresholds (10x ratio, 0.5 read ratio, 1000 rows), and exact naming conventions for indexes. Guidance is copy-paste ready and specific.	3 / 3
Workflow Clarity	Seven clearly sequenced phases with explicit validation in Phase 7 (re-run EXPLAIN ANALYZE, compare before/after). Includes safety guardrails (never run on destructive statements, never CREATE INDEX without CONCURRENTLY), clear deferral points to another skill, and a before/after example demonstrating the feedback loop.	3 / 3
Progressive Disclosure	Appropriately references external skills (supabase-mcp-verification, db-diagnostics-inspection) with clear signaling of when to defer. Content is well-structured with phases as natural sections, and the skill itself stays focused on query plan analysis without inlining unrelated material.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that hits all the marks. It provides specific concrete actions, includes a comprehensive set of natural trigger terms a developer would use, explicitly states both what it does and when to use it, and occupies a clearly distinct niche around Postgres query performance debugging via MCP.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Executes EXPLAIN ANALYZE via MCP', 'debug slow queries', 'identify missing indexes', 'detect sequential scans', 'optimize query plans'. These are all concrete, well-defined actions.	3 / 3
Completeness	Clearly answers both 'what' (executes EXPLAIN ANALYZE, debugs slow queries, identifies missing indexes, detects sequential scans, optimizes query plans) and 'when' with an explicit 'Use when...' clause listing multiple trigger scenarios.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'slow SQL', 'query plans', 'unused indexes', 'Postgres queries', 'index-not-used', 'sequential scans', 'EXPLAIN ANALYZE'. These are terms a developer would naturally use when seeking help with database performance.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: Postgres query performance optimization via EXPLAIN ANALYZE through MCP. The combination of Postgres-specific terminology, MCP execution, and query plan analysis makes it very unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed

2 months ago

Table of Contents

Discovery Implementation Validation