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

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 topic areas, but it reads more like a category label than an actionable skill description. It lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill, and the capabilities are described as abstract categories rather than concrete actions.

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.'

Replace abstract category names with concrete actions, e.g., 'Writes optimized PostgreSQL queries, designs normalized schemas, recommends indexes for slow queries, and configures Row Level Security (RLS) policies.'

Include common trigger term variations such as 'postgres', 'SQL', 'slow queries', 'RLS', 'row level security', 'database performance', and 'db schema'.

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 actions. It doesn't specify what it actually does with these areas (e.g., 'creates indexes', 'writes optimized queries', 'designs schemas').	2 / 3
Completeness	Describes what it 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 the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also somewhat weak (patterns rather than actions), warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'PostgreSQL', 'query optimization', 'schema design', 'indexing', 'security', and 'Supabase', which users might naturally mention. However, it misses common variations like 'SQL', 'database performance', 'slow queries', 'RLS', 'row level security', 'postgres', or 'db'.	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 or database 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 high-quality reference skill that is exceptionally concise and actionable, providing executable SQL for every pattern it covers. Its table-based quick references and well-commented code examples make it immediately useful. The main weakness is the lack of validation/safety guidance around the configuration and security commands, which involve potentially destructive operations.

Suggestions

Add a brief validation step after the configuration template (e.g., 'Verify with SHOW work_mem; before and after reload') to address safety for destructive ALTER SYSTEM operations.

Consider adding a note about testing RLS policies (e.g., 'SET ROLE to test; verify policy blocks unauthorized access') since RLS misconfigurations are a common security risk.

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., Supabase-specific RLS wrapping with SELECT, specific anti-pattern detection queries).	3 / 3
Actionability	Nearly every section contains copy-paste ready SQL. Index cheat sheet maps query patterns directly to CREATE INDEX statements, common patterns include executable examples with comments explaining the 'why', and anti-pattern detection queries are fully functional against pg_catalog views.	3 / 3
Workflow Clarity	This is primarily a reference/cheat-sheet skill rather than a multi-step workflow skill, so the bar is lower. However, the configuration template section includes destructive operations (ALTER SYSTEM SET, REVOKE ALL) without validation checkpoints or rollback guidance, and there's no explicit sequence for applying these changes safely.	2 / 3
Progressive Disclosure	Well-structured with clear sections (index cheat sheet, data types, common patterns, anti-patterns, configuration). Appropriately delegates deeper content to the `database-reviewer` agent and references related skills. For a standalone skill with no bundle files, the organization is clean and navigable.	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: about 1 month 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.