supabase-database
Generates Supabase database migrations, writes RLS policies with auth.uid(), configures auth integration, and generates TypeScript types. Use when creating tables, writing migrations, configuring RLS, or implementing Supabase auth.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is a strong skill description that clearly communicates specific Supabase-related capabilities with concrete actions, includes an explicit 'Use when' clause with natural trigger terms, and is highly distinctive due to Supabase-specific terminology. It follows the third-person voice convention and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: generates migrations, writes RLS policies with auth.uid(), configures auth integration, and generates TypeScript types. These are precise, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (generates migrations, writes RLS policies, configures auth, generates TypeScript types) and 'when' with an explicit 'Use when...' clause listing trigger scenarios (creating tables, writing migrations, configuring RLS, implementing Supabase auth). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Supabase', 'migrations', 'RLS policies', 'auth.uid()', 'TypeScript types', 'tables', 'auth'. These cover the main terms a developer working with Supabase would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Supabase-specific terminology (RLS policies, auth.uid(), Supabase auth) that clearly differentiates it from generic database or migration skills. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently covers Supabase migration workflows with concrete, executable examples and clear validation checkpoints. It respects Claude's intelligence by avoiding explanations of basic concepts while providing specific, actionable guidance for the multi-step migration process. The progressive disclosure to project-specific configuration is cleanly handled.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what Supabase, migrations, or RLS are—concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable SQL for table creation, RLS policies, and verification queries. The migration example is copy-paste ready with realistic naming conventions, and the type generation command is concrete. | 3 / 3 |
Workflow Clarity | The 7-step sequential workflow is clearly numbered with explicit validation checkpoints after steps 3 and 5, including specific assertions (migration completes, RLS passes, tests pass) and a failure recovery loop (revert, adjust, re-run). Destructive operations are explicitly called out with mitigation steps. | 3 / 3 |
Progressive Disclosure | The skill serves as a concise overview and immediately references the project-specific config file for customization. Content is well-structured into logical sections (rules, example, verification) without being monolithic or requiring multi-level navigation. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- monkilabs/opencastle
- Commit
f5c8508
- 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.