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.

Quality

70%

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

65%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 body is a concise, well-organized index that progressively discloses detail into 30 prefix-named rule files, but it offers no executable guidance or validation workflow in-body and ships a broken reference path. Fixing the path and adding a verification step would lift the weaker dimensions.

Suggestions

Correct the broken reference: 'schema-partial-indexes.md' does not exist; point to 'query-partial-indexes.md' or the matching schema rule file.

Add a short 'How to apply a rule' workflow with a validation checkpoint (e.g. run EXPLAIN ANALYZE before/after, confirm the plan improves, then apply) to satisfy the database feedback-loop expectation.

Include a complete file listing or a per-category index of all 30 rule files so navigation does not rely solely on the prefix convention and a directory scan.

Dimension	Reasoning	Score
Conciseness	The body is a lean overview/index (priority table, when-to-apply list, how-to-use, references) that does not re-explain concepts Claude already knows; every section earns its place.	3 / 3
Actionability	The body indexes rule files and describes their contents but contains no executable SQL itself, and one cited path ('schema-partial-indexes.md') does not exist, fitting 'some concrete guidance but incomplete'.	2 / 3
Workflow Clarity	No multi-step sequence or validation checkpoints are given; per the rubric notes, database operations without validate/fix/retry feedback loops are capped at 2.	2 / 3
Progressive Disclosure	A clear category/prefix table and one-level-deep references provide good structure, but the in-body file index is incomplete (only three examples) and includes a broken path, so navigation is not fully clean.	2 / 3
	Total	9 / 12 Passed

Description

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

The description cleanly answers both what the skill does and when to use it, with a distinct Postgres-performance niche. It is held back only by generic action verbs and limited trigger-term variation rather than concrete operations and fuller keyword coverage.

Suggestions

Replace generic verbs with concrete operations, e.g. 'Add missing indexes, rewrite slow queries, design partitioned schemas, and tune connection pooling'.

Broaden trigger terms to include natural phrases users say: 'SQL', 'slow queries', 'indexes', 'connection pooling', and 'row-level security (RLS)'.

Keep the explicit 'Use this skill when...' clause but tie it to the most common real-world asks (e.g. 'when diagnosing slow Postgres queries or reviewing schema migrations').

Dimension	Reasoning	Score
Specificity	Names the domain and several actions ('writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations') but the verbs are generic rather than a list of concrete operations, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	Both 'what' (Postgres performance optimization and best practices) and 'when' ('Use this skill when writing, reviewing, or optimizing...') are explicit, with an explicit trigger clause.	3 / 3
Trigger Term Quality	'Postgres queries, schema designs, database configurations' are natural user terms, but common variations users would say (SQL, indexes, slow queries, RLS, connection pooling) are absent, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	A focused Postgres performance niche with distinct, domain-specific triggers makes it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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: 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.