postgres-patterns

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

Quality

60%

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

87%Scale 1-3

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

This is a high-quality reference skill that is exceptionally concise and actionable, providing executable SQL for every pattern with well-organized tables and sections. Its main weakness is the lack of validation/verification steps—there's no guidance on using EXPLAIN ANALYZE to verify index effectiveness, testing RLS policies, or confirming configuration changes took effect. The content is written in Traditional Chinese, which is fine for its target audience, and appropriately delegates detailed workflows to the database-reviewer agent.

Suggestions

Add a brief validation section showing how to verify index effectiveness with EXPLAIN ANALYZE after creating indexes (e.g., `EXPLAIN ANALYZE SELECT ... ;` to confirm index scan vs seq scan)

Include a quick verification step for RLS policies (e.g., `SET ROLE authenticated; SET request.jwt.claims = '{...}'; SELECT * FROM orders;`) to catch misconfigurations

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. Uses tables for quick reference, provides only actionable SQL examples, and avoids explaining what PostgreSQL or indexes are. Every section earns its place with concrete patterns Claude wouldn't inherently know (e.g., specific Supabase RLS optimization with SELECT wrapper, BRIN for time series).	3 / 3
Actionability	All guidance is concrete and copy-paste ready: executable SQL for every pattern (covering indexes, upserts, cursor pagination, queue processing, anti-pattern detection queries, and configuration templates). No pseudocode or vague descriptions.	3 / 3
Workflow Clarity	This is primarily a reference/cheat-sheet skill rather than a multi-step workflow, so sequencing is less critical. However, for operations like applying configuration changes or creating indexes on production tables, there are no validation checkpoints or feedback loops (e.g., verify index creation, check EXPLAIN output after adding an index, test RLS policies).	2 / 3
Progressive Disclosure	Clean overview structure with well-organized sections (index cheat sheet, data types, common patterns, anti-patterns, config). Appropriately delegates deeper content to the `database-reviewer` agent and references related skills. For a standalone skill with no bundle files, the organization is excellent and navigation is clear.	3 / 3
	Total	11 / 12 Passed

Description

32%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 identifies a clear domain (PostgreSQL/Supabase) and lists relevant capability areas, but remains at a category level rather than specifying concrete actions. The biggest weakness is the complete absence of a 'Use when...' clause, which is critical for Claude to know when to select this skill from a pool of many. The trigger terms are reasonable but could be expanded with common user phrasings.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about PostgreSQL queries, Supabase database setup, SQL performance issues, or database security policies.'

Include more natural trigger term variations such as 'postgres', 'SQL', 'slow queries', 'RLS', 'row-level security', 'migrations', 'database performance'.

Make capabilities more concrete by listing specific actions, e.g., 'Write optimized SQL queries, design normalized schemas, create indexes for performance, configure row-level security (RLS) policies.'

Dimension	Reasoning	Score
Specificity	Names the domain (PostgreSQL) and lists several action areas (query optimization, schema design, indexing, security), but these are categories rather than concrete specific actions like 'create indexes', 'write RLS policies', or 'optimize slow queries'.	2 / 3
Completeness	Describes what the skill covers (PostgreSQL patterns for optimization, schema, indexing, security) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only moderately detailed, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'PostgreSQL', 'query optimization', 'schema design', 'indexing', 'security', and 'Supabase', but misses common user variations like 'SQL', 'database performance', 'slow queries', 'RLS', 'migrations', 'postgres', or '.sql'.	2 / 3
Distinctiveness Conflict Risk	The mention of PostgreSQL and Supabase provides some distinctiveness, but 'database patterns', 'query optimization', and 'schema design' could overlap with general SQL skills or other database-related skills. The Supabase qualifier helps narrow it somewhat.	2 / 3
	Total	7 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

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

Reviewed: 3 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.