Content
67%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 strong, genuinely Supabase-specific body: the security checklist and CLI gotchas are concrete and executable, with real validation checkpoints in the commit workflow. The main costs are token-efficiency — the approval-gate language is repeated many times and repo-specific overrides are inlined — and a few vague hand-waves where commands are expected.
Suggestions
State the disposable-local-database/approval policy once (e.g., in a short 'Safety boundaries' section) and reference it elsewhere instead of repeating it ~5 times.
Extract the BigSimmo/PsychSift repository override into a reference file (or trim it), so the generic skill body stays lean.
Replace vague steps with commands: specify what 'the smallest repository-provided offline or local-emulator proof' and 'the approved local workflow' actually run.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly dense, high-value Supabase-specific traps, but the disposable-local-database/approval-gate policy is restated ~5 times across the override section, CLI gotchas, and schema-changes section, and the repository-specific 'BigSimmo/PsychSift' override is padding for general users. More than the 'minor instances' of anchor 4, well short of the padded-concept-explanations of anchor 2. | 3 / 5 |
Actionability | Concrete throughout: executable curl connectivity check, `supabase --help` discovery pattern, copy-paste SQL policy examples with TO/USING/WITH CHECK, specific CLI version floors, and the .md-suffix doc-fetching trick. Minor gaps like 'create the migration file through the approved local workflow' and 'run the smallest repository-provided offline proof' keep it below fully-executable anchor 5. | 4 / 5 |
Workflow Clarity | Ordered MCP troubleshooting steps, a numbered commit workflow with validation checkpoints (advisors → security checklist → migration → `supabase migration list --local`), and an explicit error-recovery loop ('If an approach fails after 2-3 attempts, stop and reconsider'). The 'Verify your work' principle is underspecified for a skill gating destructive database operations, so not anchor 5. | 4 / 5 |
Progressive Disclosure | Well-sectioned body; the single reference (references/skill-feedback.md) exists, is one level deep, clearly signaled with a 'MUST read when' condition, and correctly links to the real assets/feedback-issue-template.md. Minor gap: the repeated repo-override/approval policy is a natural candidate for extraction into a reference file. | 4 / 5 |
Total | 15 / 20 Passed |