postgres-patterns

PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices. Use when designing PostgreSQL schemas, indexes, or RLS policies, or when a query is too slow.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

83%Weight 40%Scale 1-5

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

A lean, highly actionable SQL cheat sheet that excels at conciseness and actionability. Its main weakness is workflow clarity: as a reference catalog it lacks explicit validation checkpoints or feedback loops for the database operations it describes.

Suggestions

Add a short "Verify before shipping" step (e.g. EXPLAIN the query, confirm the index is used, test the RLS policy with a sample role) to turn isolated patterns into a validate→fix→retry workflow.

Consider moving the anti-pattern detection and configuration template blocks into separate reference files referenced one level deep, keeping SKILL.md as a tighter overview.

Add a brief pointer on when to run VACUUM/ANALYZE after schema/index changes so the catalog covers post-change validation.

Dimension	Reasoning	Score
Conciseness	Dense tables and copy-paste SQL with terse inline comments assume Claude's competence; no padded explanations of what PostgreSQL or an index is, so every token earns its place.	5 / 5
Actionability	All examples are executable SQL covering the common cases — composite/covering/partial indexes, RLS, upsert, cursor pagination, SKIP LOCKED queues, and diagnostic anti-pattern queries — with no pseudocode.	5 / 5
Workflow Clarity	It is a pattern catalog rather than a sequenced process, so there is no explicit multi-step workflow with validation checkpoints; the "When to Activate" list and diagnostic queries provide loose guidance but no validate→fix→retry feedback loop.	3 / 5
Progressive Disclosure	Well-organized sections (When to Activate, Quick Reference, Related) with one-level pointers to the database-reviewer agent and no nested references, but the anti-pattern and configuration blocks are substantial enough that splitting them into reference files would improve navigation.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

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, complete, and well-differentiated, cleanly stating both capabilities and natural-use triggers in third person. Minor additional synonyms would push trigger_term_quality to full marks.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas — "query optimization, schema design, indexing, and security" — giving comprehensive coverage of the PostgreSQL skill domain.	5 / 5
Completeness	Explicitly answers both what ("PostgreSQL database patterns for query optimization, schema design, indexing, and security") and when ("Use when designing PostgreSQL schemas, indexes, or RLS policies, or when a query is too slow") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural triggers like "designing PostgreSQL schemas, indexes, or RLS policies" and "when a query is too slow" are present, but synonyms (e.g. "slow query", "database", "migrations") and explicit file/extension terms are only partially covered.	4 / 5
Distinctiveness Conflict Risk	A clearly scoped PostgreSQL niche with distinct triggers (RLS policies, indexing, slow queries) and minimal overlap risk with non-database skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/postgres-patterns/SKILL.md
Commit: d8409a4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.