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 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 Supabase mention adds some distinctiveness but the description would benefit significantly from explicit trigger guidance and more specific action verbs.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about PostgreSQL queries, Supabase database setup, slow query performance, or database schema design.'

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

Replace category-level descriptions with concrete actions, e.g., 'Writes optimized SQL queries, designs normalized schemas, creates indexes for performance, and implements Row Level Security 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 'slow queries', 'database performance', 'RLS', 'migrations', 'SQL', '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 skills or other database-related 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 quick reference skill that excels in conciseness and actionability, providing executable SQL for every pattern with efficient table-based summaries. Its main weaknesses are the lack of validation/verification steps for configuration changes and anti-pattern remediation, and the absence of bundle files to support the progressive disclosure structure it hints at with agent/skill references.

Suggestions

Add validation steps after configuration changes (e.g., 'Verify with SHOW work_mem;' after ALTER SYSTEM) and after anti-pattern fixes to create feedback loops.

Consider splitting anti-pattern detection queries and configuration templates into separate referenced files to improve progressive disclosure and keep the main skill leaner.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, using tables and code snippets to convey maximum information with minimal prose. It assumes Claude's competence with PostgreSQL concepts and doesn't explain what indexes or RLS are—just shows how to use them.	3 / 3
Actionability	Every pattern includes fully executable SQL code that is copy-paste ready. The index cheat sheet, anti-pattern detection queries, configuration templates, and common patterns like UPSERT and cursor pagination are all concrete and immediately usable.	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) and anti-pattern detection, there are no explicit validation checkpoints or feedback loops for verifying that changes took effect or that fixes resolved issues.	2 / 3
Progressive Disclosure	The skill references a `database-reviewer` agent for detailed guidance and related skills, which is good progressive disclosure. However, there are no bundle files to support deeper dives, and the content itself is fairly dense—some sections like anti-pattern detection queries or configuration templates could be split into referenced files for better organization.	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: 7113b5b

Reviewed: about 23 hours 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.