CtrlK
BlogDocsLog inGet started
Tessl Logo

postgres-optimization

PostgreSQL optimization including indexes, query plans, partitioning, JSONB operations, and connection pooling

63

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/postgres-optimization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and token-efficient with excellent executable examples, but it is a monolithic reference rather than a sequenced workflow, and it keeps all material inline with no progressive disclosure to bundled reference files.

Suggestions

Add an explicit ordered optimization workflow (e.g. profile with pg_stat_statements → EXPLAIN ANALYZE → add/verify index → re-measure) with validation checkpoints.

Move the detailed index/partitioning/JSONB examples or tuning reference into separate reference files and link to them from a concise overview.

DimensionReasoningScore

Conciseness

The body is lean: executable code with brief inline comments, concise prose, and no padding explaining concepts Claude already knows; every section earns its tokens.

3 / 3

Actionability

It provides fully executable SQL, pgbouncer config, and pg_stat_statements queries that are specific and copy-paste ready across each topic.

3 / 3

Workflow Clarity

Content is organized by topic with a verification checklist, but there is no explicit sequenced workflow with validation checkpoints or validate→fix→retry feedback loops for the destructive operations mentioned (e.g. VACUUM FULL, dropping indexes).

2 / 3

Progressive Disclosure

All ~140 lines live inline in SKILL.md with no references to separate files; the detailed examples and tuning reference could be split out for clearer navigation.

2 / 3

Total

10

/

12

Passed

Description

67%

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

The description is specific and clearly scoped to PostgreSQL optimization but is missing an explicit "Use when..." trigger clause and common natural-language variations. Adding usage triggers would raise the completeness and trigger-term dimensions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when optimizing slow PostgreSQL queries, adding indexes, or tuning database performance.'

Include natural trigger terms users would say such as 'slow queries', 'EXPLAIN ANALYZE', and 'pgbouncer'.

DimensionReasoningScore

Specificity

"PostgreSQL optimization including indexes, query plans, partitioning, JSONB operations, and connection pooling" names the domain plus multiple concrete capability areas, matching the anchor that lists several specific concrete items.

3 / 3

Completeness

It clearly states what the skill does but lacks an explicit "Use when..." trigger clause, so per the guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Terms like "indexes", "partitioning", and "connection pooling" are relevant, but common variations a user would naturally say ("slow queries", "EXPLAIN", "pgbouncer", "query performance") are missing.

2 / 3

Distinctiveness Conflict Risk

The PostgreSQL-specific scope with named subtopics forms a clear niche unlikely to trigger for or conflict with other skills.

3 / 3

Total

10

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rohitg00/awesome-claude-code-toolkit
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.