Content
72%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A comprehensive, highly actionable Supabase reference with broad executable code examples, but it is a monolithic ~750-line document that inlines material better split into reference files and lacks explicit validation checkpoints in its destructive database workflows.
Suggestions
Add explicit validation/verification steps to destructive workflows — e.g., after generating a migration, apply it to the local environment and verify the resulting schema matches the declared state before proceeding, with a fix-and-retry loop on failure.
Split reference-grade material (SQL style guide, RLS helper functions, the multiple code-example catalogs) into clearly signaled one-level-deep files under references/ (e.g. references/sql-style-guide.md, references/rls-policies.md) and keep SKILL.md as a concise overview.
Trim the redundant Summary recap and basic SQL-convention prose to tighten token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and rule-dense with minimal padding of concepts Claude already knows, but the redundant Summary recap and some standard SQL-convention prose ('Use white space and indentation to enhance readability') are tokens that could be trimmed. | 4 / 5 |
Actionability | Extensive copy-paste-ready, executable examples throughout — Deno.serve Hello World, npm:express, Supabase.ai embeddings, SQL schema/function examples (5 variants), and RLS policies with correct/incorrect pairs and performance rewrites covering common cases. | 5 / 5 |
Workflow Clarity | The schema-management and migration flows are clearly sequenced (stop env -> supabase db diff -> review), but for destructive/batch database operations there is no explicit validation/verification feedback loop (apply-then-verify, validate-fix-retry); the destructive-operations cap therefore applies. | 3 / 5 |
Progressive Disclosure | Good internal section structure across 6 numbered parts, but at ~750 lines with no references/ scripts/ or assets/ files, reference-grade material (SQL style guide, RLS helper-function reference) is fully inlined rather than split into clearly signaled one-level-deep files. | 3 / 5 |
Total | 15 / 20 Passed |