CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

postgres-patterns

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

Quality

80%

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/zh-TW/skills/postgres-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

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.

An exemplary lean quick-reference: dense tables and executable SQL with no filler. The only substantive gap is the lack of validation or rollback guidance around the destructive configuration statements, which caps workflow clarity; structure and disclosure are otherwise strong.

Suggestions

Add validation/rollback notes to the 設定範本 section, e.g. a check query to verify connections/timeouts after pg_reload_conf(), and guidance to revert REVOKE/ALTER SYSTEM changes if issues arise.

Move the anti-pattern detection queries and configuration templates into a references/ file (e.g. references/detection.sql, references/config.sql) to keep SKILL.md as a tighter overview.

Briefly note prerequisites for the monitoring and detection queries (e.g. pg_stat_statements must be enabled) so they fail loudly rather than silently for users on default configurations.

DimensionReasoningScore

Conciseness

The body is lean tables and copy-paste SQL where every token earns its place (e.g. "O(1) vs OFFSET 是 O(n)", "用 SELECT 包裝!"), with zero explanation of concepts Claude already knows. It matches the lean-and-efficient anchor exactly; nothing to trim for a 4.

5 / 5

Actionability

All guidance is fully executable, copy-paste-ready SQL covering the common cases: composite/covering/partial indexes, RLS policy, UPSERT, cursor pagination, FOR UPDATE SKIP LOCKED queue processing, anti-pattern detection queries, and config templates. Specific examples span the whole skill's stated scope.

5 / 5

Workflow Clarity

As a reference skill it is well organized with per-pattern applicability notes, but the 設定範本 section prescribes destructive system-wide statements ("REVOKE ALL ON SCHEMA public FROM public", "ALTER SYSTEM SET max_connections...", "statement_timeout") with no validation or rollback guidance, which the rubric caps at 3. Not 2 because content is clearly organized and each pattern states when it applies.

3 / 5

Progressive Disclosure

Clean section structure with clear headers, tables, and an appropriate pointer to the database-reviewer agent for deeper guidance. Not 5 because at ~140 lines with no bundle files, the config templates and anti-pattern detection queries could live in a references/ file; not 3 because nothing is buried and all content fits the quick-reference purpose.

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.

A concise, specific description with good natural keywords and a clear PostgreSQL/Supabase niche. Its main weakness is the complete absence of a "Use when..." trigger clause, which caps completeness and limits discoverability.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing SQL queries or migrations, designing schemas, troubleshooting slow queries, or implementing Row Level Security in PostgreSQL/Supabase."

Include common user phrasings like "Postgres", "SQL", "slow query", and "migration" to broaden trigger-term coverage.

Mention connection pooling and Row Level Security in the description so the stated capabilities match what the skill body actually covers.

DimensionReasoningScore

Specificity

The description names the domain and lists several specific areas ("query optimization, schema design, indexing, and security") rather than generic actions. It falls short of 5 because it omits areas the skill actually covers (connection pooling, RLS, slow-query troubleshooting), and is well above the 1-2 concrete actions anchor at 3.

4 / 5

Completeness

The "what" is clear and concrete ("PostgreSQL database patterns for query optimization, schema design, indexing, and security") but there is no "Use when..." clause or equivalent explicit trigger guidance, which the rubric caps at 3. Not 2 because the "what" half is specific rather than vague.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say: "PostgreSQL", "query optimization", "schema design", "indexing", "security", "Supabase". Not 5 because common variations like "Postgres", "SQL", "slow query", and "migrations" are missing; clearly better than the partial coverage at 3.

4 / 5

Distinctiveness Conflict Risk

"PostgreSQL" plus "Based on Supabase best practices" carves a mostly distinct niche with only minor overlap risk against generic SQL or backend skills. Not 5 because "database patterns ... security" is broad enough to overlap closely related skills (the body itself lists backend-patterns and clickhouse-io).

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

affaan-m/ECC

Path

docs/zh-TW/skills/postgres-patterns/SKILL.md

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.