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.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill postgres-pro70
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 concrete actions and explicit trigger guidance. The technical terms used are appropriate for the target audience and provide excellent differentiation from other database-related skills. The 'Use when' and 'Invoke for' structure makes selection criteria unambiguous.
| 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', 'VACUUM', 'performance monitoring' - these are terms database developers naturally use when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with PostgreSQL-specific terminology (JSONB, VACUUM, EXPLAIN) that clearly differentiates it from generic database skills or other SQL database skills like MySQL or SQLite. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has excellent organization and progressive disclosure with clear references to detailed topic files, but critically lacks actionable content. It reads more like a role description than executable guidance - there are no SQL examples, no EXPLAIN output interpretation, and no concrete commands that Claude could copy and use. The constraints lists are helpful but abstract.
Suggestions
Add executable SQL examples for key operations: an EXPLAIN ANALYZE query with sample output interpretation, an index creation statement with rationale, a JSONB query with GIN index
Include a concrete validation workflow for index creation: check current query plan -> create index -> verify plan improvement -> monitor pg_stat_user_indexes
Remove the role-play framing ('You are a senior PostgreSQL DBA...') - Claude doesn't need persona instructions, just actionable guidance
Add at least one complete worked example showing the full optimization cycle: slow query -> EXPLAIN analysis -> solution -> verification
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary framing ('You are a senior PostgreSQL DBA with 10+ years of production experience') and role-play setup that Claude doesn't need. The MUST DO/MUST NOT DO lists are useful but could be more compact. | 2 / 3 |
Actionability | The skill lacks any executable code examples. It describes what to do ('Use EXPLAIN ANALYZE', 'Create appropriate indexes') but provides no concrete SQL, no example queries, no actual EXPLAIN output interpretation, and no copy-paste ready commands. | 1 / 3 |
Workflow Clarity | The 5-step core workflow provides a sequence but lacks validation checkpoints. For database operations that can be destructive (index creation, VACUUM tuning), there are no explicit verification steps or feedback loops for error recovery. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear reference table pointing to topic-specific files (performance.md, jsonb.md, etc.) with explicit 'Load When' guidance. References are one level deep and well-signaled. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
- 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.