Tessl • The management layer for AI agent skills

SkillPublic

postgres-patterns

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

Quality

79%

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

Quality

Content

90%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 body is an exemplary lean reference: executable, copy-paste-ready SQL patterns organized into scannable tables and short labeled sections with zero padding. Its only gaps are the absence of an explicit validation/verify loop around the risky ALTER SYSTEM and REVOKE configuration changes, and no deeper reference files for the bulk patterns.

Suggestions

Add a brief validation step around the 設定範本 section (e.g. check current values with SHOW before ALTER SYSTEM, and verify with pg_reload_conf()) to close the feedback loop for risky config changes.

Consider moving the expanded pattern catalog or the full RLS/config guidance into a references/ file with a clearly signaled link, keeping SKILL.md as the quick-reference overview.

Dimension	Reasoning	Score
Conciseness	The body is a lean quick reference: terse tables (索引速查表, 資料類型快速參考), one-line pattern labels with SQL, and no padding or explanation of concepts Claude already knows. Every token earns its place, matching anchor 5.	5 / 5
Actionability	All snippets are fully executable, copy-paste-ready SQL covering the common cases: composite/covering/partial indexes, RLS policy wrapping, UPSERT with ON CONFLICT, cursor pagination, FOR UPDATE SKIP LOCKED queue processing, diagnostic queries, and config templates. This matches the anchor-5 example of executable commands covering common cases.	5 / 5
Workflow Clarity	As a single-purpose reference the "action" (look up the pattern) is unambiguous, and the 反模式偵測 section provides diagnostic queries that act as verification steps. It is not 5 because there is no explicit sequence or validation checkpoint before risky operations (ALTER SYSTEM SET, REVOKE ALL) — no verify-then-apply loop — which the rubric flags for database operations.	4 / 5
Progressive Disclosure	Clear single-file overview with well-signaled sections (何時啟用, 快速參考, 相關) and an explicit pointer to the `database-reviewer` agent for the full workflow — a one-level-deep handoff. Not 5 because everything (~140 lines) is inline with no external bundle; still appropriately organized for a quick reference, so above the midpoint.	4 / 5
	Total	18 / 20 Passed

Description

61%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 names a specific domain and lists relevant sub-areas with good natural keywords, but it describes topics rather than concrete actions and entirely lacks a "when to use" trigger clause, capping completeness and specificity. Adding an explicit "Use when..." clause with natural trigger phrases would lift it substantially.

Suggestions

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

Replace the topic list with concrete actions — e.g. "Optimizes slow PostgreSQL queries, designs schemas and indexes, implements Row Level Security, and configures connection pooling" — to convert areas into capabilities.

Include natural synonyms users actually say ("Postgres", "slow query", "migrations", "RLS") to improve trigger term coverage toward the top anchor.

Dimension	Reasoning	Score
Specificity	"PostgreSQL database patterns for query optimization, schema design, indexing, and security" names the domain plus four sub-areas, but these are topics rather than concrete actions — no verbs describing what the skill actually does. It matches anchor 3 (domain plus some specifics, not comprehensive); it falls short of 4 because 4 requires several specific concrete actions, which are absent.	3 / 5
Completeness	The "what" is clearly stated (patterns for query optimization, schema design, indexing, security), but there is no "Use when..." or equivalent trigger clause anywhere, so per the rubric guideline completeness is capped at 3. It is not 2 because the "what" is specific and multi-area, not vague.	3 / 5
Trigger Term Quality	Good keyword coverage with natural terms: "PostgreSQL", "query optimization", "schema design", "indexing", "security", "Supabase". A few natural terms users would say are missing — "Postgres" synonym, "slow query", "migrations", "row level security", "connection pooling" — keeping it at anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The PostgreSQL/Supabase framing carves out a clear niche with distinct triggers, with only minor overlap risk against generic database or ORM skills. Not 5 because the broad areas (security, schema design) could co-trigger with general backend/database skills.	4 / 5
	Total	14 / 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
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: docs/zh-TW/skills/postgres-patterns/SKILL.md
Revision: 25278e7

Reviewed: 29 days ago

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.

postgres-patterns

Table of Contents

Is this your skill?