postgres-patterns

PostgreSQL 数据库模式，涵盖查询优化、架构设计、索引和安全。基于 Supabase 最佳实践。

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/ja-JP/skills/postgres-patterns/SKILL.md

Quality

Content

80%

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 lean, highly actionable SQL quick-reference with excellent conciseness and copy-paste-ready examples, but it lacks validation feedback loops for its batch/destructive config operations and keeps all content inline rather than progressively disclosing detail into separate files.

Suggestions

Add validation/verification checkpoints to the config template's destructive operations (ALTER SYSTEM, REVOKE ALL) to lift workflow clarity above 2.

Move the anti-pattern detection queries and full configuration template into a one-level-deep reference file linked from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is a lean cheat sheet using dense tables and terse, useful SQL comments with no padding or explanation of concepts Claude already knows, matching anchor 3; not 2 because nothing reads as unnecessary or tighten-able.	3 / 3
Actionability	All examples are fully executable, copy-paste-ready SQL (CREATE INDEX, covering/partial indexes, RLS policy, UPSERT, cursor pagination, SKIP LOCKED queue, anti-pattern detection, config), matching anchor 3; not 2 because there is no pseudocode or missing key details.	3 / 3
Workflow Clarity	It is a well-organized reference card rather than a sequenced multi-step workflow, and the config template performs batch/destructive operations (ALTER SYSTEM, REVOKE ALL) without validation checkpoints beyond a final pg_reload_conf(), so workflow clarity is capped at 2 per the database-operations guideline; not 3 because explicit validate/verify feedback loops are absent.	2 / 3
Progressive Disclosure	Sections are well organized and it appropriately points outward to the database-reviewer agent, but all content is inline in a single ~140-line file with no separate reference files, matching anchor 2; not 3 because there is no one-level-deep file split, and not 1 because references are signaled and not deeply nested.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 clearly identifies a PostgreSQL-specific niche and its main domains, but it omits an explicit 'Use when…' trigger clause, which limits its completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when…' trigger clause naming user-phrased situations (e.g., 'Use when writing SQL queries, designing schemas, troubleshooting slow queries, or setting up RLS and connection pooling').

Reframe the area list as concrete actions (e.g., 'Optimize queries, design schemas, create indexes, and configure Row Level Security') to lift specificity from domains to operations.

Include common natural variations users might say ('Postgres', 'slow query', 'database indexes', 'RLS policies') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('PostgreSQL 数据库模式') and several action areas ('查询优化、架构设计、索引和安全性') but lists topic domains rather than multiple concrete actions, matching anchor 2; not anchor 3 because the items are abstract nouns rather than concrete operations like 'extract text, fill forms'.	2 / 3
Completeness	Clearly states what the skill does but has no 'Use when…' clause or equivalent explicit trigger guidance, which the guidelines cap at 2; not 3 because the 'when' is missing rather than explicit.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('PostgreSQL', '查询优化', '索引', '安全性', 'Supabase') but lacks common variations a user might actually say, matching anchor 2; above anchor 1 (terms are not jargon-only) but below anchor 3 (incomplete coverage).	2 / 3
Distinctiveness Conflict Risk	'PostgreSQL 数据库模式' anchored on Supabase best practices is a clear, specific niche unlikely to trigger for the wrong skill, matching anchor 3; not 2 because it is more specific than 'Works with document files'.	3 / 3
	Total	9 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: xu-xiang/everything-claude-code-zh
Path: docs/ja-JP/skills/postgres-patterns/SKILL.md
Commit: dfbf946

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