postgres-patterns

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

1.12x

Quality

56%

Does it follow best practices?

Impact

96%

1.12x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs/ja-JP/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

79%

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

This is a well-crafted PostgreSQL quick reference skill that excels in conciseness and actionability, providing lean, executable SQL patterns organized in clear tables and code blocks. Its main weaknesses are the lack of validation/verification steps for destructive operations (ALTER SYSTEM, REVOKE) and the absence of supporting bundle files for deeper reference material despite mentioning a database-reviewer agent.

Suggestions

Add validation steps after destructive operations like ALTER SYSTEM SET and REVOKE (e.g., verify with SHOW commands or check pg_settings)

Consider splitting anti-pattern detection queries and configuration templates into separate reference files to improve progressive disclosure

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, using tables and code examples without explaining basic concepts Claude already knows. Every section serves as a quick reference with no unnecessary padding or explanations of what PostgreSQL is or how databases work.	3 / 3
Actionability	All guidance is concrete with executable SQL examples that are copy-paste ready. The index cheat sheet, anti-pattern detection queries, configuration templates, and common patterns all provide specific, immediately usable code.	3 / 3
Workflow Clarity	This is primarily a reference/cheat-sheet skill rather than a multi-step workflow skill, so sequential processes are less critical. However, the 'When to activate' section lists triggers without clear decision paths, and there are no validation checkpoints for potentially destructive operations like ALTER SYSTEM SET or REVOKE commands.	2 / 3
Progressive Disclosure	The skill references a `database-reviewer` agent for detailed guidance and links to related skills, which is good progressive disclosure. However, there are no bundle files to support deeper dives, and the main file itself is fairly long (~120 lines of content) with sections like anti-pattern detection and configuration templates that could potentially be split into separate reference files.	2 / 3
	Total	10 / 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/everything-claude-code
Commit: 841beea

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