Use when optimizing PostgreSQL queries, configuring replication, or implementing advanced database features. Invoke for EXPLAIN analysis, JSONB operations, extension usage, VACUUM tuning, performance monitoring.
98
100%
Does it follow best practices?
Impact
97%
1.02xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
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 a strong skill description that clearly identifies PostgreSQL-specific capabilities with explicit trigger guidance. It uses appropriate technical terms that users would naturally employ when seeking PostgreSQL help, and the 'Use when' and 'Invoke for' clauses provide clear selection criteria. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'optimizing PostgreSQL queries', 'configuring replication', 'implementing advanced database features', 'EXPLAIN analysis', 'JSONB operations', 'extension usage', 'VACUUM tuning', 'performance monitoring'. | 3 / 3 |
Completeness | Explicitly answers both what (optimizing queries, configuring replication, EXPLAIN analysis, etc.) and when ('Use when...', 'Invoke for...') with clear trigger guidance at the start of the description. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'PostgreSQL', 'queries', 'replication', 'EXPLAIN', 'JSONB', 'extension', 'VACUUM', 'performance monitoring' - these are terms database developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with PostgreSQL-specific terminology (EXPLAIN, JSONB, VACUUM, replication) that clearly distinguishes it from generic database or SQL skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that exemplifies best practices: it's concise yet comprehensive, provides executable code with verification steps, and structures content with clear progressive disclosure. The end-to-end example with explicit before/after verification is particularly strong, and the constraints section provides clear guardrails without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's PostgreSQL competence. No unnecessary explanations of basic concepts—jumps straight to actionable patterns and commands. | 3 / 3 |
Actionability | Provides fully executable SQL examples throughout, including complete EXPLAIN queries, index creation with CONCURRENTLY, JSONB patterns, and monitoring queries. All code is copy-paste ready. | 3 / 3 |
Workflow Clarity | The end-to-end example demonstrates a clear 5-step workflow with explicit verification checkpoints (verify index is used, confirm Index Scan, update statistics). The core workflow section also sequences steps logically with validation emphasis. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, common patterns inline, and a clear reference table pointing to one-level-deep topic files (performance.md, jsonb.md, etc.) with explicit 'Load When' guidance. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%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.
5b76101
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.