CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

84

1.14x
Quality

77%

Does it follow best practices?

Impact

96%

1.14x

Average score across 3 eval scenarios

SecuritybySnyk

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured overview that exemplifies progressive disclosure, keeping the body lean and delegating detailed SQL examples to one-level-deep reference files. The main weakness is that the body itself carries no executable code, relying entirely on referenced files for actionable guidance.

Suggestions

Inline 1-2 short, high-impact SQL examples (e.g. adding an index on a WHERE column) so the body is immediately actionable without requiring a file read for the most common case.

Add a brief 'Quick check' workflow step (e.g. run EXPLAIN ANALYZE before/after) so the usage sequence has an explicit verification checkpoint for optimization tasks.

Reduce the minor redundancy between the opening paragraph and the 'When to Apply' section by merging or trimming one of them.

DimensionReasoningScore

Conciseness

The body is a lean overview/index with no over-explanation of concepts Claude already knows; only minor redundancy between the intro and the 'When to Apply' list could be trimmed.

4 / 5

Actionability

Provides a concrete priority table with category prefixes and impact levels, but the body itself contains no executable SQL or code — all actionable examples live in the referenced files.

3 / 5

Workflow Clarity

The lookup workflow (identify category by prefix/impact, read the corresponding rule file, apply its incorrect-vs-correct structure) is clear; this is a reference guide rather than a destructive operation, so the validation cap does not apply.

4 / 5

Progressive Disclosure

Clear overview in SKILL.md pointing to well-signaled, one-level-deep reference files (verified present, e.g. references/query-missing-indexes.md, references/_sections.md) with an organized category table for easy navigation.

5 / 5

Total

16

/

20

Passed

Description

83%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 well-constructed description that clearly answers both what the skill does and when to apply it, using third-person imperative trigger guidance. It is specific and distinct, with only minor gaps in keyword synonym coverage.

DimensionReasoningScore

Specificity

Names the Postgres domain and three concrete actions ('writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations'), but coverage is not fully comprehensive (no mention of indexes, RLS, or pooling).

4 / 5

Completeness

Explicitly states both what the skill does ('Postgres performance optimization and best practices from Supabase') and when to use it with concrete trigger phrases ('Use this skill when writing, reviewing, or optimizing...').

5 / 5

Trigger Term Quality

Good natural keywords ('Postgres queries, schema designs, database configurations') but missing common synonyms a user might say such as 'SQL', 'indexes', or 'slow queries'.

4 / 5

Distinctiveness Conflict Risk

Has a clear Supabase/Postgres niche with distinct triggers, but 'queries, schema designs' could overlap with generic SQL or database skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
Reviewed

Table of Contents

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.