postgres-pro
Use when optimizing PostgreSQL queries, configuring replication, or implementing advanced database features. Invoke for EXPLAIN analysis, JSONB operations, extension usage, VACUUM tuning, performance monitoring.
95
92%
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 its PostgreSQL-specific niche with concrete actions and explicit trigger guidance. It uses domain-appropriate terminology that users would naturally employ, and the 'Use when' / 'Invoke for' structure makes selection criteria unambiguous. The description is concise yet comprehensive, covering both high-level tasks and specific PostgreSQL features.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: optimizing PostgreSQL queries, configuring replication, EXPLAIN analysis, JSONB operations, extension usage, VACUUM tuning, and performance monitoring. | 3 / 3 |
Completeness | Clearly answers both 'what' (optimizing queries, configuring replication, EXPLAIN analysis, JSONB operations, VACUUM tuning, etc.) and 'when' with explicit trigger guidance ('Use when optimizing PostgreSQL queries...', 'Invoke for EXPLAIN analysis...'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'PostgreSQL queries', 'replication', 'EXPLAIN', 'JSONB', 'VACUUM', 'performance monitoring', 'extension'. These are terms a developer would naturally use when seeking PostgreSQL help. | 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. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured skill with excellent actionability and workflow clarity. The end-to-end example with verification steps is particularly effective, and the reference table provides clean progressive disclosure. The main weakness is some token waste in the introductory description, the 'When to Use' list, and the 'Knowledge Reference' footer that don't add value beyond what Claude already knows or what the YAML frontmatter provides.
Suggestions
Remove the opening description line ('Senior PostgreSQL expert...') and the 'Knowledge Reference' section at the bottom — these describe Claude's existing knowledge and waste tokens.
Trim or remove the 'When to Use This Skill' section since this information is already captured in the skill description metadata and is largely self-evident from the content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary framing (e.g., 'Senior PostgreSQL expert with deep expertise...' opening, the 'When to Use This Skill' list largely restates what Claude can infer from context, and the 'Knowledge Reference' section at the bottom lists concepts Claude already knows). The code examples themselves are lean and well-targeted. | 2 / 3 |
Actionability | Provides fully executable SQL examples throughout — the end-to-end slow query workflow, JSONB indexing, VACUUM monitoring, and replication lag queries are all copy-paste ready with inline comments explaining what to look for in the output. | 3 / 3 |
Workflow Clarity | The core workflow is clearly sequenced with explicit validation checkpoints: analyze → create index → verify index is used via EXPLAIN → update statistics. The end-to-end example demonstrates a complete feedback loop (identify → fix → verify), and the constraints section reinforces verification requirements. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and common patterns inline, plus a well-organized reference table pointing to five topic-specific files with clear 'Load When' guidance. References are one level deep and clearly signaled. | 3 / 3 |
Total | 11 / 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.
- Repository
- jeffallan/claude-skills
- Commit
3d95bb1
- Reviewed
Table of Contents
Is this your skill?
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.