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.
68
81%
Does it follow best practices?
Impact
—
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
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid sequential migration workflow with good validation checkpoints and a useful concrete SQL example. Its main weaknesses are that several workflow steps lack specific executable commands (relying on vague references to 'smoke tests' and 'safe-deploy pipeline'), and the skill description promises coverage of auth integration and TypeScript types that the content only briefly touches. The progressive disclosure structure is reasonable but the referenced config file doesn't exist in the bundle.
Suggestions
Replace vague workflow steps ('run smoke tests', 'safe-deploy pipeline') with specific executable commands or script paths, e.g., `supabase db reset && supabase test db` for local validation.
Add concrete guidance for TypeScript type generation as a standalone actionable step rather than a comment in the SQL example, since it's called out in the skill description.
Include a brief auth integration section with a concrete example (e.g., using auth.uid() in a client query or setting up an auth trigger), since the skill description promises auth configuration guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary phrasing like 'Generic Supabase development methodology' and slightly verbose step descriptions (e.g., 'promote migration to production using the project's safe-deploy pipeline' is vague filler). The validation checkpoint paragraph could be tighter. However, it avoids explaining what Supabase or RLS is, which is good. | 2 / 3 |
Actionability | The SQL migration example is concrete and executable, and the verification query is copy-paste ready. However, several workflow steps are vague ('run smoke tests', 'run the full test suite', 'safe-deploy pipeline') without providing actual commands or scripts. The type generation command is commented out rather than being a clear actionable step. | 2 / 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 called out with mitigation guidance (backfill scripts, phased changes). | 3 / 3 |
Progressive Disclosure | There is a reference to a project-specific config file (supabase-config.md) which is good progressive disclosure. However, no bundle files exist to support this reference, and the skill could benefit from splitting out more detailed content (e.g., RLS policy patterns, auth integration details, TypeScript type generation) into separate referenced files rather than keeping everything inline or omitting it entirely. | 2 / 3 |
Total | 9 / 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
cc13aaf
- 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.