supabase

Core Supabase CLI, migrations, RLS, Edge Functions

Quality

43%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/supabase/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is essentially a comma-separated list of Supabase-related topics with no verbs, no actions, and no usage guidance. It fails to tell Claude what the skill does or when to select it, making it poorly suited for skill selection among many options. It needs substantial expansion to be functional.

Suggestions

Add concrete action verbs describing what the skill does, e.g., 'Generates and manages Supabase database migrations, configures Row Level Security policies, scaffolds and deploys Edge Functions.'

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about Supabase setup, database migrations, RLS policies, row level security, or deploying serverless Edge Functions.'

Include natural-language variations of key terms such as 'row level security', 'database policies', 'supabase project', and 'serverless functions' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description lists domain keywords ('Supabase CLI, migrations, RLS, Edge Functions') but does not describe any concrete actions. There are no verbs indicating what the skill actually does—it reads as a topic list, not a capability description.	1 / 3
Completeness	The description answers neither 'what does this do' (no actions described) nor 'when should Claude use it' (no 'Use when...' clause or equivalent trigger guidance). Both are missing or very weak.	1 / 3
Trigger Term Quality	It includes relevant technical keywords a user might mention ('Supabase', 'CLI', 'migrations', 'RLS', 'Edge Functions'), but misses common natural-language variations like 'row level security', 'database policies', 'supabase deploy', or 'serverless functions'.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Supabase' provides some niche specificity, but the broad terms like 'CLI' and 'migrations' could overlap with other database or deployment skills. Without explicit scoping, there is moderate conflict risk.	2 / 3
	Total	6 / 12 Passed

Implementation

64%

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

This is a solid, highly actionable Supabase skill with excellent concrete examples covering CLI workflow, migrations, RLS, Edge Functions, and CI/CD. Its main weaknesses are length (could benefit from splitting detailed sections into referenced files) and missing explicit validation/verification checkpoints in multi-step workflows like migration deployment. The anti-patterns section is a nice touch but the overall document could be tightened.

Suggestions

Add explicit validation checkpoints to the migration and deployment workflows (e.g., 'Verify migration applied: supabase migration list' after db push, or 'Test RLS policies: run a query as anon to confirm deny')

Move the Edge Functions, Storage, and CI/CD sections into separate referenced files to reduce the main skill's token footprint and improve progressive disclosure

Remove the Supabase Stack overview table — Claude already knows what these services are; the table adds tokens without actionable value

Dimension	Reasoning	Score
Conciseness	The skill is fairly comprehensive but includes some unnecessary content Claude already knows (e.g., the Supabase Stack table explaining what Auth, Storage, Realtime are). The environment variables section with local vs production examples is somewhat verbose. However, most sections are reasonably tight with useful code examples.	2 / 3
Actionability	Excellent actionability throughout — nearly every section includes executable CLI commands, complete SQL examples, and copy-paste-ready TypeScript code. The migration workflow, RLS policies, Edge Functions, and CI/CD template are all concrete and immediately usable.	3 / 3
Workflow Clarity	The migration workflow presents three clear options with numbered steps, and the CI/CD template shows a proper deploy pipeline. However, there are no explicit validation checkpoints or feedback loops — e.g., after `supabase db push` there's no verification step, and the migration workflow's 'review generated SQL' step lacks guidance on what to check for. The db reset step serves as implicit validation but isn't framed as a checkpoint.	2 / 3
Progressive Disclosure	The skill mentions framework-specific skills at the top ('Load with: base.md + [supabase-nextjs.md \| ...]') and references ORM-specific skills, which is good. However, the file itself is quite long (~250 lines of content) with sections like Storage, Edge Functions, and CI/CD that could be split into separate reference files. The CLI Quick Reference duplicates commands already shown in earlier sections.	2 / 3
	Total	9 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: alinaqi/claude-bootstrap
Commit: d4ddb03

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.