CtrlK
BlogDocsLog inGet started
Tessl Logo

supabase-cli

Supabase CLI commands for local development, migrations, project management, and deployment. Use when working with Supabase CLI, starting local dev, managing migrations, or deploying changes.

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is supabase-cli in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

76%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 highly actionable, well-organized CLI command reference with excellent executable examples and a sensible one-level-deep bundle structure. Its main weaknesses are the absence of validation checkpoints around destructive operations (capping workflow clarity) and mild duplication between the Quick Reference table and detailed sections.

Suggestions

Add validation/verification steps around destructive and batch operations — e.g. run `supabase migration list` or `db push --dry-run` before `db push`, and confirm state after `db reset` or `migration down` — so workflows include explicit checkpoints.

Link the reference files contextually from their related sections (e.g. "See [migrations.md](references/migrations.md) for the full migration workflow") instead of only listing them in the trailing References section.

Trim duplication: drop the near-identical second `migration down`/`squash` examples and consider removing commands from the Quick Reference table that are repeated verbatim in later sections.

DimensionReasoningScore

Conciseness

The body is a lean, command-first reference that assumes Claude's competence with no conceptual padding, but the Quick Reference table duplicates later sections and some example pairs are near-identical (two `migration down` and two `squash` variants), leaving minor trimming opportunities that keep it out of the 5 anchor.

4 / 5

Actionability

Every section provides fully executable, copy-paste-ready commands with real flags, ports, URLs, and expected outputs (e.g. the curl test for edge functions and the psql restore sequence), matching the comprehensive 5 anchor.

5 / 5

Workflow Clarity

Content is well-organized by task and rough sequences exist (init → link → start; migration new → diff → push), but workflows involving destructive and batch operations (`db reset`, `migration down`, `stop --no-backup`, `projects delete`) include no validation or verification checkpoints, which caps this dimension at 3 per the rubric guideline.

3 / 5

Progressive Disclosure

Three real, one-level-deep reference files are clearly signaled with short descriptions in a References section, and the main body is appropriately overview-level for a CLI reference; the minor gap is that references are only listed at the end rather than linked contextually from the relevant workflow sections (e.g. migrations.md from the migration sections).

4 / 5

Total

16

/

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 explicitly states both the skill's capabilities and concrete usage triggers in third person, with a clearly distinct niche. The only improvement space is enumerating a few more concrete actions and natural trigger synonyms.

DimensionReasoningScore

Specificity

The description lists several specific capability areas ("local development, migrations, project management, and deployment"), but these read as categories rather than concrete actions like "start the local stack" or "push migrations", so it falls short of the comprehensive 5 anchor while clearly exceeding the 1-2 actions of a 3.

4 / 5

Completeness

It explicitly answers both what ("Supabase CLI commands for local development, migrations, project management, and deployment") and when ("Use when working with Supabase CLI, starting local dev, managing migrations, or deploying changes") with concrete trigger phrases, closely paralleling the 5 anchor example; the 4 anchor's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

Trigger terms are natural phrases users would say ("working with Supabase CLI, starting local dev, managing migrations, or deploying changes"), but coverage misses common variations such as "edge functions", "generate types", or bare "Supabase", matching the good-but-incomplete 4 anchor.

4 / 5

Distinctiveness Conflict Risk

"Supabase CLI" is a clear niche trigger with distinct, unambiguous terms; there is minimal risk of this description firing for an unrelated skill.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fernandezbaptiste/Skrillz
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.