postgres-patterns

用于查询优化、模式设计、索引和安全性的PostgreSQL数据库模式。基于Supabase最佳实践。

1.26x

Quality

60%

Does it follow best practices?

Impact

91%

1.26x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/zh-CN/skills/postgres-patterns/SKILL.md

Quality

Content

87%Scale 1-3

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-structured PostgreSQL reference skill that provides highly actionable, copy-paste-ready SQL examples across indexing, data types, common patterns, anti-pattern detection, and configuration. Its main weakness is the lack of validation/verification steps for potentially impactful operations like system configuration changes and security revocations. The progressive disclosure is effective, delegating detailed review workflows to the `database-reviewer` agent.

Suggestions

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

Add a brief caution or rollback note for the `REVOKE ALL ON SCHEMA public FROM public` command, since it can break existing applications.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient throughout. It uses tables for quick reference, provides only executable SQL examples without explaining what PostgreSQL or indexes are, and trusts Claude's existing knowledge. Every section earns its place.	3 / 3
Actionability	All guidance is concrete and copy-paste ready: executable SQL for every pattern (composite indexes, partial indexes, RLS policies, upserts, cursor pagination, queue processing), diagnostic queries for anti-pattern detection, and configuration templates with specific values.	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 potentially destructive operations like ALTER SYSTEM SET and REVOKE ALL, there are no validation checkpoints or rollback guidance. The configuration template lacks a verify step after pg_reload_conf().	2 / 3
Progressive Disclosure	The skill serves as a concise overview with clear pointers to the `database-reviewer` agent for full workflow guidance, and references related skills (`clickhouse-io`, `backend-patterns`). Content is well-organized into logical sections with tables and code blocks. No bundle files are needed for this reference-style skill.	3 / 3
	Total	11 / 12 Passed

Description

32%Scale 1-3

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 the domain (PostgreSQL/Supabase) and lists high-level capability areas but lacks concrete actions and explicit trigger guidance. It reads more like a topic label than a skill description that would help Claude disambiguate among many available skills. The Chinese language is fine but the content needs more specificity and a clear 'Use when' clause.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about PostgreSQL queries, Supabase database setup, RLS policies, or database performance optimization.'

List more specific concrete actions instead of broad categories, e.g., 'Write and optimize SQL queries, design database schemas with proper normalization, create indexes for performance, configure Row Level Security (RLS) policies.'

Include common user-facing trigger terms and file/technology variations like 'SQL', 'database', 'RLS', 'migrations', 'slow queries', '.sql files' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (PostgreSQL/Supabase) and lists some actions (query optimization, schema design, indexing, security), but these are broad categories rather than concrete specific actions like 'create indexes on foreign keys' or 'write RLS policies'.	2 / 3
Completeness	Describes what the skill covers (PostgreSQL patterns for query optimization, schema design, etc.) but completely lacks any 'Use when...' clause or 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 score of 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'PostgreSQL', 'Supabase', 'query optimization', 'schema design', 'indexing', and 'security', but misses common user variations like 'SQL', 'database queries', 'RLS', 'row level security', 'migrations', 'slow queries', or 'database performance'.	2 / 3
Distinctiveness Conflict Risk	The mention of PostgreSQL and Supabase provides some distinctiveness, but 'schema design', 'query optimization', and 'security' are broad enough to overlap with general database skills or other SQL-related skills.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: affaan-m/everything-claude-code
Path: docs/zh-CN/skills/postgres-patterns/SKILL.md
Commit: 0c1d7be

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