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

Pending

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

Discovery

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 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', 'database performance', 'migrations'.

Make capabilities more concrete by listing specific 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 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', '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

Implementation

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, well-crafted reference skill that efficiently packs actionable PostgreSQL patterns into a scannable format. The tables, executable SQL examples, and anti-pattern detection queries are all high-value additions that respect Claude's intelligence. The main weakness is the lack of validation/verification guidance for configuration changes and the absence of a clear workflow for acting on diagnostic query results.

Suggestions

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

Consider adding a brief note after anti-pattern detection queries on recommended next steps (e.g., 'Create missing indexes for unindexed foreign keys' or 'Run VACUUM on bloated tables').

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient—pure reference tables, executable SQL examples, and no unnecessary explanations of what PostgreSQL is or how databases work. Every section earns its place as a quick-reference cheat sheet.	3 / 3
Actionability	All examples are concrete, executable SQL statements with clear comments explaining their purpose. The index cheat sheet, anti-pattern detection queries, and configuration templates are all copy-paste ready.	3 / 3
Workflow Clarity	This is primarily a reference/cheat-sheet skill rather than a multi-step workflow, so explicit sequencing is less critical. However, for operations like configuration changes (ALTER SYSTEM + pg_reload_conf), there's no validation step to confirm settings took effect, and the anti-pattern detection queries lack guidance on what to do with results.	2 / 3
Progressive Disclosure	The skill is well-structured as a quick reference with clear sections, and appropriately delegates detailed workflows to the `database-reviewer` agent. References to related skills and agents are clearly signaled at the end, with no nested reference chains.	3 / 3
	Total	11 / 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: 8 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.