supabase-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.14x

Quality

71%

Does it follow best practices?

Impact

96%

1.14x

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/supabase/skills/supabase-postgres-best-practices/SKILL.md

The canonical home for this skill is supabase-postgres-best-practices in supabase/agent-skills

Quality

Content

57%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 skill body is an effective, well-organized index that exemplifies progressive disclosure by deferring detail to 32 real reference files. Its weaknesses are mild redundancy with the frontmatter, absence of executable examples in the body itself, and a lack of any sequenced validation workflow.

Suggestions

Remove the duplicate opening sentence and the redundant 'When to Apply' trigger list, since both restate the frontmatter abstract and description.

Add one short, concrete SQL example (incorrect vs. correct) directly in the body so the skill is actionable without opening a reference file.

For optimization workflows that change schemas or indexes, include a brief validation checkpoint sequence (e.g. EXPLAIN ANALYZE before/after) to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining Postgres basics, but the opening sentence ("Comprehensive performance optimization guide... Contains rules across 8 categories") echoes the frontmatter abstract, and the "When to Apply" bullets restate the description's triggers, so it could be tightened.	2 / 3
Actionability	It gives concrete navigation — real file paths in "How to Use" and a category/prefix table — but the body itself contains no executable SQL or commands; the actionable content lives one level down in the reference files, so guidance is concrete yet incomplete.	2 / 3
Workflow Clarity	Usage is organized (When to Apply → category table → How to Use), but there is no sequenced multi-step workflow with validation checkpoints; it reads as a lookup pattern rather than a process, capping it below 3.	2 / 3
Progressive Disclosure	The body is a concise overview pointing to well-signaled, one-level-deep reference files (e.g. references/query-missing-indexes.md, references/query-partial-indexes.md, references/_sections.md, all verified present), organized by prefix across 8 categories — matching the anchor for clear overview with easy navigation.	3 / 3
	Total	9 / 12 Passed

Description

85%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.

A strong, well-structured description that clearly states both capability and explicit usage triggers in third person. The only gap is trigger-term breadth, omitting common phrasings like SQL and indexes that users frequently say.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations" — matching the anchor for several specific concrete actions, and uses third-person voice throughout.	3 / 3
Completeness	It explicitly answers both what ("Postgres performance optimization and best practices from Supabase") and when ("Use this skill when writing, reviewing, or optimizing Postgres queries..."), satisfying the anchor for clearly answering both with explicit triggers.	3 / 3
Trigger Term Quality	It includes natural terms like "Postgres," "queries," "schema designs," and "database configurations," but misses common variations a user might say such as "SQL," "indexes," or "slow queries," so it lands at the 'some relevant keywords but missing common variations' level rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	The Postgres performance-optimization niche with Supabase-specific framing and explicit query/schema/config triggers is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/supabase/skills/supabase-postgres-best-practices/SKILL.md
Commit: 11c74d6

Reviewed: 9 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.