CtrlK
BlogDocsLog inGet started
Tessl Logo

postgres-patterns

PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.

61

Quality

72%

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-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

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

The body is a lean, highly actionable quick reference with dense tables and executable SQL, well-organized and appropriately delegating deeper guidance to the database-reviewer agent. Its only notable gap is the absence of validation checkpoints after destructive configuration changes.

Suggestions

Add a verification step after the configuration template (e.g. "Verify with `\dp` and `SHOW statement_timeout;` before reloading") to close the workflow-clarity gap on destructive changes.

Optionally add a one-line note flagging which configuration values (max_connections, work_mem) must be tuned to RAM before applying, so the template is safer to apply verbatim.

DimensionReasoningScore

Conciseness

The body is lean — dense tables and brief code snippets with minimal, value-adding comments ("Equality columns first", "Wrap in SELECT!", "O(1) vs OFFSET which is O(n)") — assuming Claude's competence with no padded explanations, matching the score-3 anchor.

3 / 3

Actionability

It provides fully executable SQL throughout (CREATE INDEX, UPSERT with ON CONFLICT, FOR UPDATE SKIP LOCKED, pg_stat_statements queries), copy-paste ready, matching the score-3 anchor.

3 / 3

Workflow Clarity

Content is well-organized into clear sections, but the configuration template includes destructive/security-sensitive changes ("REVOKE ALL ON SCHEMA public FROM public", "ALTER SYSTEM SET...") with no validation or verification step, capping workflow clarity at 2 per the judging guidelines.

2 / 3

Progressive Disclosure

A clear overview line delegates detail to the `database-reviewer` agent, sections are well-organized, and the Related section signals one-level-deep cross-references with no nested references; for a self-contained quick reference this matches the score-3 anchor.

3 / 3

Total

11

/

12

Passed

Description

57%Weight 40%Scale 1-3

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 names a clear domain and several relevant capability areas in third person, but it lacks an explicit "Use when..." trigger clause and omits common user phrasings, leaving it competent yet incomplete.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing SQL queries or migrations, designing schemas, troubleshooting slow queries, or implementing RLS."

Include natural user variations such as "Postgres", "slow queries", and "database migrations" to improve trigger-term coverage.

Reframe capability areas as concrete actions (e.g. "optimize queries, design schemas, add indexes") rather than abstract "patterns for" topics.

DimensionReasoningScore

Specificity

Quotes "query optimization, schema design, indexing, and security" name the domain and several areas, but these are topics/capabilities rather than concrete actions like "extract", "fill", or "merge", matching the score-2 anchor.

2 / 3

Completeness

It clearly states what the skill covers ("PostgreSQL database patterns for...") but provides no "Use when..." clause or equivalent trigger, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Natural terms like "PostgreSQL", "query optimization", "indexing", and "schema design" are present, but common user variations such as "Postgres", "slow queries", and "migrations" are missing, fitting the score-2 anchor.

2 / 3

Distinctiveness Conflict Risk

The explicit PostgreSQL scoping carves a clear niche unlikely to trigger for non-Postgres skills, matching the score-3 anchor; it is not above 3 because trigger guidance is absent, but not below 3 because the niche is distinct.

3 / 3

Total

9

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
ysyecust/everything-claude-code
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.