postgres-patterns

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

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./docs/zh-TW/skills/postgres-patterns/SKILL.md

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.

The body is an exceptionally lean, actionable SQL reference with excellent conciseness and actionability. Its main weakness is the absence of validation/feedback checkpoints for destructive database operations, which caps workflow clarity.

Suggestions

Add explicit validation/feedback steps for destructive or batch operations, e.g. test ALTER SYSTEM settings on a non-production instance and verify with SHOW before reloading, and re-check pg_stat_statements after applying indexes.

For the queue-processing pattern, add a verification note (e.g. confirm exactly one row returned, handle no-row case) to establish a feedback loop.

Consider splitting the anti-pattern detection and config templates into a separate reference file and signaling it from SKILL.md to strengthen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Lean reference of tables and copy-paste SQL with minimal prose; assumes Claude's competence and every section earns its place; not below 5 because there is no padding or over-explanation of concepts Claude already knows.	5 / 5
Actionability	Fully executable SQL covering common cases (composite/covering/partial indexes, RLS, UPSERT, cursor pagination, SKIP LOCKED queues, anti-pattern queries, config templates); copy-paste ready with concrete examples; not below 5 because the guidance is specific and complete.	5 / 5
Workflow Clarity	This is a pattern catalog rather than a sequenced workflow, and the destructive/batch database operations (ALTER SYSTEM config, SKIP LOCKED queue processing) lack explicit validate-then-fix feedback loops; the rubric caps workflow_clarity at 3 for database operations without validation, so it cannot score above 3 despite being well organized.	3 / 5
Progressive Disclosure	Well-organized into clear sections (index cheat sheet, data types, patterns, anti-patterns, config) with no nested references and a self-contained structure; not a 5 because it is a single monolithic reference rather than an overview that signals one-level-deep detail files, and the skill exceeds the ~50-line simple-skill threshold.	4 / 5
	Total	17 / 20 Passed

Description

66%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 and PostgreSQL-niche with good keyword coverage, but it omits any explicit 'Use when...' trigger guidance, which caps its completeness. Adding a trigger clause would lift both completeness and trigger-term quality.

Suggestions

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

Include natural synonyms/extensions users might say (e.g. 'Postgres', '.sql', 'migrations') to broaden trigger coverage.

Drop the provenance phrase 'Based on Supabase best practices.' from the description to keep it focused on capabilities and triggers.

Dimension	Reasoning	Score
Specificity	Names the domain plus four concrete capability areas ('query optimization, schema design, indexing, and security'), listing several specific actions with only minor coverage gaps; not a 5 because it describes topical areas rather than a comprehensive enumerated set of discrete actions.	4 / 5
Completeness	Has a clear 'what' (PostgreSQL patterns for the listed areas) but no explicit 'when' trigger clause; per the rubric, a missing 'Use when...' clause caps completeness at 3, so it cannot score 4.	3 / 5
Trigger Term Quality	Contains good natural keyword coverage a user would plausibly say ('PostgreSQL', 'query optimization', 'schema design', 'indexing', 'security'); not a 5 because it omits common synonyms and file/extension-style triggers and has no explicit 'Use when' phrasing.	4 / 5
Distinctiveness Conflict Risk	Clearly PostgreSQL-specific with distinct triggers and minimal conflict risk; not a 5 because 'database patterns' broadly could still overlap marginally with general database or sibling skills (e.g. backend-patterns).	4 / 5
	Total	15 / 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
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: docs/zh-TW/skills/postgres-patterns/SKILL.md
Commit: e04ea0b

Reviewed: 2 days 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.