postgres-patterns

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

87%

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

The body is a tight, executable PostgreSQL reference with excellent conciseness and actionability and clean single-file organization. Its only weakness is workflow clarity: for database configuration and anti-pattern checks it offers no validation or feedback steps, which caps that dimension.

Suggestions

Add a short validation step after the 設定範本 (ALTER SYSTEM) block, e.g. 'Run SELECT pg_reload_conf(); then verify with SHOW work_mem;' to create a config feedback loop.

For the anti-pattern detection queries, add a follow-up note such as 'After identifying unindexed foreign keys, create a matching index and re-run the check to confirm resolution'.

Optionally sequence the slow-query troubleshooting into a small ordered checklist (detect -> explain -> index -> re-measure) so the workflow is explicit rather than implied.

Dimension	Reasoning	Score
Conciseness	The body is a lean quick-reference of tables and code with no padding or explanation of concepts Claude already knows (e.g. no 'what is an index' prose); every token earns its place like the level-3 anchor.	3 / 3
Actionability	All examples are complete, executable SQL with inline guidance comments (e.g. the SKIP LOCKED queue query, the composite-index order note), copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	This is a quick-reference rather than a multi-step process, but the database-configuration and anti-pattern-detection sections involve operations where no validation/feedback loop is given; per the scoring notes, missing validation for database operations caps workflow_clarity at 2.	2 / 3
Progressive Disclosure	A single self-contained file with well-organized sections and clear headers; no bundle files exist so references are appropriately absent, and the cross-links to the database-reviewer agent and sibling skills are clearly signaled and one level deep.	3 / 3
	Total	11 / 12 Passed

Description

50%

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 conveys a clear domain and several capability areas but lacks an explicit trigger clause and natural keyword variations. It reads as a category listing rather than trigger-rich guidance, landing mid-range on most dimensions.

Suggestions

Add an explicit 'Use when...' clause (e.g. 'Use when writing SQL queries or migrations, designing schemas, troubleshooting slow queries, or implementing RLS') to lift completeness to 3.

Expand trigger terms with natural user phrasings like 'slow queries', 'indexes', 'migrations', 'row-level security', and 'connection pooling' rather than only 'PostgreSQL'.

Replace generic categories with concrete actions (e.g. 'optimize slow queries', 'design composite and partial indexes', 'write RLS policies') to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ('PostgreSQL database patterns') and several actions ('query optimization, schema design, indexing, and security'), but these are broad categories rather than the multiple concrete actions (e.g. 'extract text', 'fill forms') the level-3 anchor requires.	2 / 3
Completeness	Clearly states what the skill covers, but there is no explicit 'when to use' trigger clause — the guideline caps completeness at 2 when 'Use when...' or equivalent trigger guidance is missing.	2 / 3
Trigger Term Quality	Includes the relevant keyword 'PostgreSQL' but omits natural variations users would actually say ('slow queries', 'indexes', 'migrations', 'RLS', 'connection pooling'); coverage is partial like the 'Works with PDF files' anchor.	2 / 3
Distinctiveness Conflict Risk	The PostgreSQL niche is reasonably specific, but the generic phrasing 'database patterns' could overlap with broader database or schema-design skills, so it is not as cleanly distinguishable as a level-3 trigger set.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: ysyecust/everything-claude-code
Commit: a9cbecb

Reviewed: 1 day 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.