Name: postgres-best-practices
Rating: 61.8 (1 reviews)
Author: administrakt0r

postgres-best-practices

Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.

1.25x

Quality

44%

Does it follow best practices?

Impact

89%

1.25x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-bundle-data-analytics/skills/postgres-best-practices/SKILL.md

The canonical home for this skill is postgres-best-practices in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

36%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 skill is essentially a table of contents/index file that points to external rule files, but provides no actionable content itself. It lacks any concrete SQL examples, optimization techniques, or workflow guidance. The duplicated 'When to Use' section and meta-descriptive content waste tokens without adding value for Claude.

Suggestions

Add at least 3-5 concrete, high-impact optimization examples inline (e.g., common missing index patterns, RLS performance pitfalls) so the skill provides standalone value without requiring bundle files.

Define a clear workflow for query optimization: identify issue → analyze with EXPLAIN → apply fix → validate improvement, with specific commands at each step.

Remove the duplicated 'When to Use' section at the bottom and trim the introductory paragraph to be more direct.

Include at least one executable SQL example for the most critical category (Query Performance) so Claude has immediately actionable guidance.

Dimension	Reasoning	Score
Conciseness	The content has some unnecessary padding — the 'When to Use' section appears twice (duplicated at top and bottom), the introductory paragraph explains what the guide is rather than providing actionable content, and the table of categories with priority/impact/prefix is meta-information that doesn't directly help Claude act. However, it's not egregiously verbose.	3 / 5
Actionability	The skill provides no concrete SQL examples, no executable code, and no specific optimization techniques. It is entirely a meta-document pointing to other files (rules/*.md, AGENTS.md) without giving any actionable guidance itself. Claude would need to read those referenced files to actually do anything.	2 / 5
Workflow Clarity	There is no workflow defined — no steps, no sequence, no validation checkpoints. The skill only describes a categorization system and file structure. For a performance optimization skill, there should be at least a basic workflow like: identify slow query → check EXPLAIN output → apply relevant rule → validate improvement.	2 / 5
Progressive Disclosure	The skill references external files (rules/*.md, _sections.md, AGENTS.md) which suggests an attempt at progressive disclosure, but no bundle files are provided to verify these exist. The references are reasonably clear but the skill itself provides almost no standalone value — it's essentially just a table of contents with no useful content at the top level.	3 / 5
	Total	10 / 20 Passed

Description

53%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 establishes a clear domain (Postgres optimization via Supabase best practices) and includes an explicit 'Use when' clause, which is good. However, it lacks concrete actions and specific trigger terms that would help Claude distinguish this skill from general database or SQL skills. The capabilities listed are too high-level to give a clear picture of what specific optimizations or techniques the skill covers.

Suggestions

Add specific concrete actions such as 'analyze query plans with EXPLAIN', 'recommend indexes', 'optimize joins', 'configure connection pooling', or 'partition large tables' to improve specificity.

Include natural trigger terms and synonyms users would say, such as 'slow query', 'PostgreSQL', 'SQL performance', 'index', 'query plan', 'EXPLAIN ANALYZE', 'database tuning', or 'RLS policies'.

Clarify what makes this skill distinct from general Postgres knowledge — e.g., specify Supabase-specific features like Row Level Security, Edge Functions, or Supabase-specific configuration recommendations.

Dimension	Reasoning	Score
Specificity	Names the domain (Postgres performance optimization) but the actions are generic — 'writing, reviewing, or optimizing' are broad verbs applied to broad categories (queries, schema designs, configurations). No concrete actions like 'adding indexes', 'analyzing query plans', or 'partitioning tables' are mentioned.	2 / 5
Completeness	Has both 'what' (Postgres performance optimization and best practices from Supabase) and 'when' (writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations). The 'when' clause is present and explicit but could be more specific with concrete trigger scenarios.	4 / 5
Trigger Term Quality	Includes relevant keywords like 'Postgres', 'queries', 'schema designs', 'database configurations', and 'Supabase', but misses natural user phrases and synonyms such as 'slow query', 'index', 'query plan', 'EXPLAIN', 'PostgreSQL', 'SQL performance', or 'database tuning'.	3 / 5
Distinctiveness Conflict Risk	The mention of 'Supabase' adds some distinctiveness, but 'Postgres queries, schema designs, or database configurations' is broad enough to overlap with general SQL skills, database administration skills, or other Postgres-related skills. The scope of 'best practices' is also quite wide.	3 / 5
	Total	12 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/antigravity-bundle-data-analytics/skills/postgres-best-practices/SKILL.md
Commit: db96168

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.