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

76%

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 ./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.

This is a strong, token-efficient quick-reference skill: every snippet is executable, the tables are dense with actionable guidance, and navigation to the full database-reviewer workflow is clearly signaled. The only meaningful gap is the Configuration Template, which applies destructive/system-wide changes (ALTER SYSTEM, REVOKE ALL) without any verification or rollback guidance.

Dimension	Reasoning	Score
Conciseness	The body is a lean cheat sheet — tables and copy-paste SQL with terse, load-bearing comments like "Wrap in SELECT!" and "O(1) vs OFFSET which is O(n)" — with no padding and no explanations of concepts Claude already knows. Every section earns its tokens as a quick reference.	5 / 5
Actionability	All examples are executable, copy-paste-ready SQL covering the common cases: index selection by query pattern, type choices, composite/covering/partial indexes, RLS policy, upsert, cursor pagination, queue processing with FOR UPDATE SKIP LOCKED, and diagnostic queries against pg_stat_statements. Minor placeholders ("adjust for RAM") are appropriately flexible rather than pseudocode.	5 / 5
Workflow Clarity	As a lookup reference there is no multi-step workflow to sequence, but the Configuration Template performs risky system-wide operations — "ALTER SYSTEM SET max_connections", "REVOKE ALL ON SCHEMA public FROM public" — with only pg_reload_conf() and no verification, rollback, or check-existing-grants steps. Per the rubric's cap for database operations lacking validation/feedback loops, workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	The body is well-organized with clearly headed sections (cheat sheets, common patterns, anti-pattern detection, configuration) and an explicit pointer to the deeper "database-reviewer" agent for full workflows. It is not a 5 because at ~140 lines all content is inline — the anti-pattern queries and configuration template are candidates for one-level-deep reference files — though as a self-contained quick reference the placement is defensible.	4 / 5
	Total	17 / 20 Passed

Description

58%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 communicates what the skill covers with a well-defined PostgreSQL niche, but it omits any 'when to use' trigger guidance, which caps its completeness. It also leans on the formal term "PostgreSQL" while missing the natural synonyms ("Postgres", "SQL", "migrations") users are more likely to say.

Suggestions

Append an explicit trigger clause, e.g. "Use when writing SQL queries or migrations, designing schemas, troubleshooting slow queries, or setting up Row Level Security in Postgres."

Include natural synonyms and user phrasing such as "Postgres", "SQL", "migrations", "RLS", and "connection pooling" so the skill triggers on the terms users actually say.

Consider dropping "Based on Supabase best practices" from the description (it is already credited in the body) to free tokens for the trigger clause.

Dimension	Reasoning	Score
Specificity	The description lists several specific capability areas — "query optimization, schema design, indexing, and security" — which go beyond naming the domain. It falls short of a 5 because these are topic areas rather than concrete actions, and there is no 'what it produces' framing.	4 / 5
Completeness	The 'what' is clear (PostgreSQL patterns for optimization, schema design, indexing, security), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guidelines. It is not a 2 because the 'what' is concrete and multi-faceted.	3 / 5
Trigger Term Quality	Relevant keywords like "PostgreSQL", "query optimization", "schema design", "indexing", and "Supabase" are present, but common natural variations users would say are missing — notably "Postgres", "SQL", "migrations", and "slow queries". This matches the 'some relevant keywords but missing common variations or synonyms' anchor rather than the 4 anchor's fuller coverage.	3 / 5
Distinctiveness Conflict Risk	"PostgreSQL database patterns" carves out a mostly distinct niche, and the Supabase attribution further signals scope. It is not a 5 because "database patterns ... security" could overlap with general SQL/database or backend skills, a risk the body itself confirms by cross-referencing sibling 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: valeriibeck-star/claude-skills
Path: skills/postgres-patterns/SKILL.md
Revision: 0bda8b8

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