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.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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 Supabase migration skill with strong actionability through executable SQL examples and a well-structured sequential workflow with explicit validation checkpoints and error recovery. The content could be slightly more concise in the workflow description, and the progressive disclosure is adequate but limited to a single external reference that cannot be verified against bundle files.

Suggestions

Tighten the migration rules text—steps 5-6 reference 'CI test replica' and 'safe-deploy pipeline' without concrete commands; either add specific CLI commands or remove the vague references to save tokens.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes some unnecessary verbosity in the migration rules (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	Provides fully executable SQL for creating tables, enabling RLS, and writing policies with auth.uid(). The verification query is copy-paste ready. The type generation command is concrete. The migration naming convention is specific.	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 clear failure recovery path (revert, adjust, re-run). Step 4 explicitly flags destructive actions with mitigation guidance.	3 / 3
Progressive Disclosure	References project-specific config in supabase-config.md which is good, but no bundle files are provided to verify the reference. The skill is reasonably sized but the migration rules section could potentially be split out for complex projects. The single reference is well-signaled but there's only one level of navigation.	2 / 3
	Total	10 / 12 Passed

Description

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

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Commit: 7a69a05

Reviewed: about 1 month 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.