postgres-patterns

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

1.26x

Quality

75%

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

83%Weight 40%Scale 1-5

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

The content is an exceptionally lean and actionable SQL cheatsheet with executable examples throughout. Its main gap is the lack of validation/verification steps around the destructive configuration operations, which caps workflow clarity.

Suggestions

Add a verification checkpoint after the configuration template, e.g. re-query pg_settings or run a smoke test before relying on ALTER SYSTEM changes.

Flag the destructive commands (REVOKE ALL, ALTER SYSTEM) with an explicit 'review before applying in production' note.

Consider splitting the anti-pattern detection and configuration templates into a separate reference file to keep the overview lighter.

Dimension	Reasoning	Score
Conciseness	The body is a lean quick-reference of tables and terse SQL snippets with minimal prose; it assumes Claude's competence and never explains what PostgreSQL is, so every token earns its place.	5 / 5
Actionability	It provides copy-paste-ready, executable SQL across the common cases — index DDL, data-type choices, UPSERT, cursor pagination, SKIP LOCKED queues, and anti-pattern detection queries.	5 / 5
Workflow Clarity	Although it is a reference rather than a sequenced workflow, it contains destructive/system-changing operations (ALTER SYSTEM SET, REVOKE ALL ON SCHEMA public) with no validation or verification checkpoint, capping workflow clarity at 3 per the destructive-ops rule.	3 / 5
Progressive Disclosure	The single self-contained file is well-organized under clear section headers with no nested references, but at ~155 lines it exceeds the under-50-line simple-skill exception and could split the larger query/config catalogs into reference files.	4 / 5
	Total	17 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 conveys a PostgreSQL-specific capability set but lacks an explicit 'Use when' trigger clause, which limits completeness. It is concise and reasonably distinct from generic database skills.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when writing SQL queries, designing schemas, or troubleshooting slow PostgreSQL queries.'

Include natural trigger synonyms users say, such as 'slow queries', 'migrations', and 'RLS'.

Convert capability areas into concrete verbs ('Optimize queries', 'Design schemas', 'Add indexes') to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the PostgreSQL domain plus four specific capability areas ("查询优化、模式设计、索引和安全性") but these are domain categories rather than the most concrete verb-actions, leaving minor coverage gaps.	4 / 5
Completeness	The 'what' is clear (PostgreSQL patterns for query optimization, schema design, indexing, security) but there is no explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural terms like "PostgreSQL", "查询优化", "索引", and "安全性" that users would say, but omits common synonyms such as "slow queries", "SQL", or "数据库".	4 / 5
Distinctiveness Conflict Risk	The PostgreSQL-specific framing plus the Supabase reference carves a clear niche, though it could still overlap with general SQL/database skills, leaving minor conflict risk.	4 / 5
	Total	15 / 20 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: affaan-m/ECC
Path: docs/zh-CN/skills/postgres-patterns/SKILL.md
Commit: e04ea0b

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.