supabase
Core Supabase CLI, migrations, RLS, Edge Functions
43
43%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/supabase/SKILL.mdQuality
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 concrete actions, and no 'Use when...' guidance. While the Supabase-specific terminology provides some distinctiveness, the lack of actionable detail and trigger clauses makes it very difficult for Claude to reliably select this skill at the right time.
Suggestions
Rewrite using action verbs describing concrete capabilities, e.g., 'Manages Supabase projects via CLI, creates and applies database migrations, configures Row Level Security (RLS) policies, and develops/deploys Edge Functions.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about Supabase setup, database migrations, row level security policies, or serverless edge functions.'
Include common natural-language variations of the technical terms, such as 'row level security', 'database policies', 'supabase deploy', 'serverless functions', and 'supabase init'.
| 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 only loosely addresses 'what' (and even that is just a keyword list, not a clear statement of capabilities). There is no 'when' clause or explicit trigger guidance at all, which per the rubric caps completeness at 2 at best—but since the 'what' is also very weak, a score of 1 is appropriate. | 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 | Mentioning 'Supabase' specifically narrows the domain and reduces conflict with generic database or CLI skills. However, the breadth of topics (CLI, migrations, RLS, Edge Functions) without specificity could overlap with more focused Supabase sub-skills if they existed. | 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, comprehensive Supabase skill with excellent actionability—nearly every section provides executable code and real commands. Its main weaknesses are its length (could benefit from splitting detailed sections into referenced files) and some verbosity in areas Claude doesn't need explained. The workflow sections would benefit from explicit validation checkpoints, especially for remote deployment operations.
Suggestions
Split detailed sections (Edge Functions, Storage, RLS patterns, CI/CD) into separate referenced files to improve progressive disclosure and reduce the main file's token footprint.
Add explicit validation/rollback steps after `supabase db push` (e.g., 'Run `supabase migration list` to verify all migrations applied; if errors occur, check `supabase db push --dry-run` first').
Remove the Supabase Stack overview table—Claude already knows what these services are; the table adds ~10 lines without actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill covers a lot of ground efficiently with good use of tables and code blocks, but includes some unnecessary content Claude already knows (e.g., the Supabase Stack table explaining what Auth, Storage, Realtime are; comments like '# macOS' before brew install). The environment variables section and connection pooling explanations add bulk that could be trimmed. | 2 / 3 |
Actionability | Nearly all guidance is concrete and executable: real CLI commands, complete SQL migrations with RLS policies, working Edge Function code with auth context, a full CI/CD GitHub Actions template, and copy-paste ready seed data. The code examples are complete and realistic. | 3 / 3 |
Workflow Clarity | The migration workflow presents three clear options with numbered steps, and the CI/CD pipeline shows a proper test-then-deploy sequence. However, the 'Deploy Migrations' section with `supabase db push` lacks explicit validation/verification steps (e.g., checking migration status after push, rollback guidance on failure). The db reset step serves as implicit validation locally but there's no feedback loop for remote deployment failures. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers and a logical flow from setup to advanced topics. However, it's a monolithic ~300-line file with no references to supporting files for detailed topics like Edge Functions, Storage, or RLS patterns that could be split out. The mention of 'see framework-specific skills' for ORM migrations is good but is the only external reference. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%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
65efb33
- 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.