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.08x

Quality

78%

Does it follow best practices?

Impact

90%

1.08x

Average score across 2 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/build-web-apps/skills/supabase-best-practices/SKILL.md

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

Quality

Content

68%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 a well-organized, token-efficient index that leverages progressive disclosure across a large reference bundle. Its weaknesses are the absence of executable content or validation guidance in the body itself and a broken example reference path.

Suggestions

Fix the broken reference in the 'How to Use' example block: references/schema-partial-indexes.md does not exist — the actual file is references/query-partial-indexes.md.

Add a brief validation checkpoint to the workflow (e.g., 'After applying a rule, re-run EXPLAIN ANALYZE or the relevant diagnostic to confirm the improvement') since the skill guides schema and configuration changes that can be destructive.

Either inline one concrete executable example (e.g., a representative index-creation snippet) or make the navigation more actionable by listing the per-category rule files so Claude can locate guidance without guessing filenames.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — a short overview, a 'When to Apply' bullet list, a priority table, and a 'How to Use' section — with no padding and no explanation of concepts Claude already knows; every token earns its place.	5 / 5
Actionability	Guidance is mostly high-level ('Read individual rule files for detailed explanations and SQL examples') with concrete file paths and a description of each file's structure, but no executable SQL or commands in the body, and one example path (references/schema-partial-indexes.md) does not exist, leaving key details incomplete.	3 / 5
Workflow Clarity	A rough navigation sequence is present (identify category by prefix → read the matching rule file → apply its incorrect/correct examples), but there are no validation or verification checkpoints, which is a gap for a skill that guides potentially destructive schema and configuration changes.	3 / 5
Progressive Disclosure	Good structure: a concise overview, a prefix/category table for discovery, and clearly signaled one-level-deep references to 33 rule files. Minor gaps — the 'How to Use' example block shows only 3 of 33 files and includes a non-existent path (schema-partial-indexes.md).	4 / 5
	Total	15 / 20 Passed

Description

87%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 strong description that clearly states what the skill does and when to invoke it, with concrete trigger phrases and a distinct Postgres/Supabase niche. It could be marginally improved by adding more specific trigger synonyms (SQL, indexes, RLS) for broader natural-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Postgres performance optimization and best practices from Supabase') and several concrete action areas ('writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations'), but coverage is not fully comprehensive (indexing, RLS, and connection pooling are not surfaced as distinct actions here).	4 / 5
Completeness	Explicitly answers both 'what' ('Postgres performance optimization and best practices from Supabase') and 'when' ('Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms a user would say ('Postgres queries', 'schema designs', 'database configurations', 'writing/reviewing/optimizing') are present, but common synonyms and specifics like 'SQL', 'indexes', 'RLS', or 'Supabase database' are missing.	4 / 5
Distinctiveness Conflict Risk	The Postgres + Supabase + performance-optimization niche is clearly delineated with distinct triggers, giving minimal overlap risk with other skills.	5 / 5
	Total	18 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/build-web-apps/skills/supabase-best-practices/SKILL.md
Commit: 1e28582

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