CtrlK
CommunityDocumentationLog inGet started
Tessl Logo

postgres-pro

tessl install github:jeffallan/claude-skills --skill postgres-pro
github.com/jeffallan/claude-skills

Use when optimizing PostgreSQL queries, configuring replication, or implementing advanced database features. Invoke for EXPLAIN analysis, JSONB operations, extension usage, VACUUM tuning, performance monitoring.

Review Score

70%

Validation Score

12/16

Implementation Score

42%

Activation Score

100%

SKILL.md
Review
Evals

Generated

Validation

Total

12/16

Score

Passed
CriteriaScore

metadata_version

'metadata' field is not a dictionary

license_field

'license' field is missing

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

body_examples

No examples detected (no code fences and no 'Example' wording)

Implementation

Suggestions 4

Score

42%

Overall Assessment

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
DimensionScoreReasoning

Conciseness

2/3

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.

Actionability

1/3

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.

Workflow Clarity

2/3

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.

Progressive Disclosure

3/3

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.

Activation

Score

100%

Overall Assessment

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.

DimensionScoreReasoning

Specificity

3/3

Lists multiple specific concrete actions: 'optimizing PostgreSQL queries', 'configuring replication', 'implementing advanced database features', 'EXPLAIN analysis', 'JSONB operations', 'extension usage', 'VACUUM tuning', 'performance monitoring'.

Completeness

3/3

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.

Trigger Term Quality

3/3

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.

Distinctiveness Conflict Risk

3/3

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.