postgres-patterns

PostgreSQL database patterns for query optimization, schema design, indexing, and security. Quick reference for common patterns, index types, data types, and anti-pattern detection. Based on Supabase best practices.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

A highly actionable, well-organized SQL reference with copy-paste-ready examples, slightly held back by minor redundancy and a lack of validation checkpoints around its destructive/batch operations.

Suggestions

Consolidate the redundant "When to Activate" and "When to Use This Skill" sections into one.

Add a brief validation step for destructive/batch operations (e.g. verify an index is used via EXPLAIN before/after; test RLS policies with sample roles).

Drop the inline explanations of concepts Claude already knows (e.g. the O(1) vs O(n) cursor note) to tighten token use.

Dimension	Reasoning	Score
Conciseness	Largely lean and table-driven, but it recapitulates some basics Claude already knows (e.g. explaining that cursor pagination is "O(1) vs OFFSET which is O(n)") and the "When to Activate" / "When to Use This Skill" sections duplicate each other.	2 / 3
Actionability	Provides fully executable, copy-paste-ready SQL across indexes, RLS policies, UPSERT, cursor pagination, queue processing, anti-pattern queries, and configuration — concrete and complete rather than pseudocode.	3 / 3
Workflow Clarity	It is a reference cheat sheet rather than a sequenced workflow, and the destructive/batch operations it covers (ALTER SYSTEM, REVOKE, queue processing) have no validation or verification checkpoints, capping clarity per the rubric.	2 / 3
Progressive Disclosure	No bundle files exist, but the body is well-organized into clearly labeled sections (cheat sheets, patterns, anti-patterns, configuration) with a "Related" pointer to companion skills/agents — appropriate single-file structure for a quick-reference skill.	3 / 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 niche-scoped to PostgreSQL, but it omits an explicit "Use when..." trigger and leans on technical terms over natural phrasing a user would actually say.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing SQL, designing schemas, fixing slow queries, or setting up RLS in PostgreSQL."

Include natural user phrasing such as "slow queries", "indexes", and "SQL" alongside the technical terms.

Trim the trailing meta sentence ("Quick reference for common patterns... Based on Supabase best practices.") which adds little trigger value.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "query optimization, schema design, indexing, and security" — each naming a specific capability rather than vague language.	3 / 3
Completeness	Clearly answers "what" (optimization, schema design, indexing, security) but "when" is only implied — there is no explicit "Use when..." trigger clause, which caps completeness per the rubric.	2 / 3
Trigger Term Quality	Includes relevant terms ("PostgreSQL", "query optimization", "indexing", "Row Level Security") but lacks common natural variations a user would say like "slow queries", "database", "SQL", or "indexes", leaning somewhat technical.	2 / 3
Distinctiveness Conflict Risk	Scoped tightly to PostgreSQL-specific patterns (index types, data types, RLS), giving it a clear niche distinct from generic backend or migration skills.	3 / 3
	Total	10 / 12 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
Commit: 4130457

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.