CtrlK
BlogDocsLog inGet started
Tessl Logo

postgres-patterns

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

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

The body is an excellent lean, executable PostgreSQL quick-reference with copy-paste SQL and well-organized sections that assume Claude's competence. Its only gap is the absence of validation/feedback loops, which the rubric specifically expects for database operations and which caps workflow clarity.

Suggestions

Add a brief validate-then-retry loop for the destructive/batch patterns (e.g. after the queue-processing and ALTER SYSTEM config template, note how to verify the change took effect and roll back if needed).

For the anti-pattern detection section, add a short follow-up step indicating what to do once a missing-FK-index or slow query is found (create the index / EXPLAIN ANALYZE) to close the loop.

DimensionReasoningScore

Conciseness

The body is lean — dense tables, executable snippets, and brief inline comments (e.g. "等值列在前,范围列在后") — with no padding explaining what PostgreSQL is or basic concepts, so every token earns its place.

3 / 3

Actionability

It provides fully executable, copy-paste-ready SQL throughout (CREATE INDEX variants, INSERT...ON CONFLICT, FOR UPDATE SKIP LOCKED, ALTER SYSTEM, anti-pattern detection queries), matching the "fully executable code/commands" anchor.

3 / 3

Workflow Clarity

Content is well-organized by category with a clear 触发时机 section, but as a reference catalog it has no multi-step sequencing or validation/feedback loops; the rubric explicitly flags database operations as needing such loops, capping this at 2.

2 / 3

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent) and none are needed; the single self-contained file is well-organized into clear sections (索引速查表, 数据类型, 常用模式, 反模式检测, 配置模板) with a 相关 navigation block and no nested references, fitting a well-organized quick-reference.

3 / 3

Total

11

/

12

Passed

Description

50%Weight 40%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 clearly scopes the skill to PostgreSQL patterns across query optimization, schema design, indexing, and security, but it is a noun-phrase catalog rather than a list of concrete actions and lacks any explicit "Use when..." trigger guidance. Adding concrete verbs and a trigger clause would raise specificity and completeness.

Suggestions

Add concrete actions instead of noun-phrase scope, e.g. "Optimize slow queries, design schemas, create indexes, and configure row-level security for PostgreSQL."

Append an explicit trigger clause: "Use when creating SQL queries or migrations, designing schemas, troubleshooting slow queries, or configuring RLS and connection pooling in PostgreSQL/Supabase."

Disambiguate from the `database-reviewer` agent — clarify this skill is a quick reference for lookups while the agent handles full review workflows.

DimensionReasoningScore

Specificity

It names the domain and sub-areas — "查询优化、架构设计、索引和安全" (query optimization, schema design, indexing, security) — but as noun-phrase scope rather than concrete actions like "optimize queries" or "create indexes", matching the "names domain and some actions" anchor and falling short of multiple specific concrete actions.

2 / 3

Completeness

It clearly states what the skill covers ("PostgreSQL 数据库模式,涵盖...") but provides no explicit "when should Claude use it" trigger clause; per the guidelines a missing "Use when..." clause caps completeness at 2.

2 / 3

Trigger Term Quality

Relevant keywords are present ("PostgreSQL", "索引", "Supabase", "安全") but common variations users would say are missing ("Postgres", "RLS", "slow query", "migration"), fitting the "some relevant keywords but missing common variations" anchor.

2 / 3

Distinctiveness Conflict Risk

The PostgreSQL/Supabase niche is fairly specific, but the description does not disambiguate from the referenced `database-reviewer` agent or other database skills, leaving overlap risk — matching the "somewhat specific but could still overlap" anchor.

2 / 3

Total

8

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
xu-xiang/everything-claude-code-zh
Reviewed

Table of Contents

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.