CtrlK
BlogDocsLog inGet started
Tessl Logo

supabase

Core Supabase CLI, migrations, RLS, Edge Functions

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/supabase/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with copy-paste-ready examples and a clear core principle, but it is a long monolithic document that would benefit from splitting into reference files and from adding explicit validation checkpoints around destructive migration operations.

Suggestions

Add explicit validation checkpoints to destructive workflows (e.g., 'Review generated SQL before running db reset'; 'Run supabase migration list and confirm only intended migrations before db push').

Split the larger inline sections (RLS policies, Edge Functions, Storage, CI/CD) into clearly signaled reference files (e.g., references/RLS.md, references/edge-functions.md) to reduce the monolithic SKILL.md body.

Trim the Supabase Stack table and redundant inline comments to tighten token efficiency toward a fully lean state.

DimensionReasoningScore

Conciseness

Mostly efficient with direct commands and code blocks that avoid explaining basics Claude knows, but the redundant Stack table and a few padded comments could be trimmed to reach a fully lean state.

2 / 3

Actionability

Packed with executable, copy-paste-ready bash, SQL, TypeScript, and YAML CI/CD examples with specific commands — fully actionable rather than abstract.

3 / 3

Workflow Clarity

Migration options are explicitly sequenced, but destructive/batch operations like 'db reset' and 'db push' lack explicit validate-then-proceed checkpoints, which caps workflow clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

Content is well-organized into sections, but it is a ~420-line monolith with RLS, edge functions, storage, and CI/CD all inline rather than split into clearly signaled one-level-deep reference files.

2 / 3

Total

9

/

12

Passed

Description

67%

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 is specific and clearly distinctive, naming four concrete Supabase capabilities, but lacks an explicit 'Use when' trigger clause and relies partly on technical jargon over natural user phrasing.

Suggestions

Add an explicit 'Use when...' trigger clause to the description (e.g., 'Use when working with Supabase database, auth, storage, or edge functions') so completeness and trigger quality are both met within the description field.

Expand natural keywords beyond jargon — include 'database', 'auth', and 'storage' alongside 'RLS' and 'Edge Functions' to match how users phrase requests.

DimensionReasoningScore

Specificity

Names multiple concrete capabilities — 'CLI, migrations, RLS, Edge Functions' — beyond just the domain, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

The description answers 'what' but has no 'Use when...' trigger clause; per the rubric a missing explicit trigger caps completeness at 2, even though a separate when-to-use field exists.

2 / 3

Trigger Term Quality

'Supabase' is a natural term, but the rest ('migrations, RLS, Edge Functions') leans technical and omits common variations like database, auth, or storage that users would actually say.

2 / 3

Distinctiveness Conflict Risk

'Supabase' is a clear, specific niche with distinct triggers unlikely to conflict with other skills.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
alinaqi/claude-bootstrap
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.