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?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs/zh-TW/skills/postgres-patterns/SKILL.md

Quality

Content

87%

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

This is a strong reference-style skill that efficiently packs PostgreSQL best practices into a scannable, actionable format. The use of tables for index and data type selection, combined with executable SQL examples for common patterns and anti-pattern detection, makes it highly practical. The only notable gap is the lack of validation/verification steps for configuration changes and potentially destructive operations.

Suggestions

Add a brief validation step after the configuration template (e.g., `SHOW work_mem;` to verify settings took effect after `pg_reload_conf()`).

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, using tables for quick reference, minimal prose, and no unnecessary explanations of concepts Claude already knows. Every section earns its place with actionable SQL examples and patterns.	3 / 3
Actionability	Nearly every pattern includes copy-paste ready SQL with comments explaining the purpose. The index cheat sheet, common patterns, anti-pattern detection queries, and configuration templates are all fully executable.	3 / 3
Workflow Clarity	The skill is primarily a reference/cheat sheet rather than a multi-step workflow, so sequencing is less critical. However, for operations like configuration changes (ALTER SYSTEM + pg_reload_conf), there are no explicit validation steps or feedback loops to confirm changes took effect.	2 / 3
Progressive Disclosure	The skill serves as a concise overview with clear pointers to the `database-reviewer` agent for full workflows, and references to related skills. Content is well-organized into logical sections with tables and code blocks, appropriate for a reference skill with no bundle files needed.	3 / 3
	Total	11 / 12 Passed

Description

32%

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 topic areas, but remains at a high level without 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 options. Adding explicit trigger conditions and more specific capability descriptions would significantly improve selection accuracy.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about PostgreSQL query performance, database schema design, Supabase configuration, or SQL optimization.'

Include more natural trigger terms users would say, such as 'postgres', 'SQL', 'slow queries', 'RLS', 'row level security', 'database performance', 'migrations', '.sql files'.

Replace high-level category names with specific concrete actions, e.g., 'Writes optimized SQL queries, designs normalized schemas, creates indexes for performance, implements 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 high-level categories rather than specific concrete actions like 'create indexes', 'write RLS policies', or 'analyze query plans'.	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', 'row level security', 'migrations', or 'postgres'.	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: ysyecust/everything-claude-code
Commit: 79cc4e3

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