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 highly actionable, code-first reference: commands and complete Deno examples cover nearly every common Supabase Edge Functions task. Weaknesses are the absence of a sequenced workflow with validation/debugging checkpoints (notably no log inspection after deploy), a broken reference link (references/deno-imports.md), and pattern examples inlined that belong in the existing function-patterns.md reference.
Suggestions
Add a validation/debugging step to the deploy workflow, e.g., 'supabase functions logs <name> --tail' after deploy and a curl smoke test against the production URL, so failures are caught early.
Fix or create references/deno-imports.md (referenced at the bottom of SKILL.md but missing from the bundle), or remove the dead link.
Move the full Stripe webhook, database webhook, and shared-code pattern examples into references/function-patterns.md, keeping only a one-line pointer plus a minimal example in SKILL.md to reduce duplication with the inline CORS section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dominated by executable code with minimal conceptual padding, but has notable duplication: the CORS pattern appears in full inline and again via the _shared/cors.ts example, and supabase client creation is shown nearly identically in three sections. This fits 'efficient; minor instances that could be trimmed' rather than the fully lean top anchor. | 4 / 5 |
Actionability | Every section provides copy-paste-ready CLI commands ('supabase functions new hello-world', 'supabase secrets set --env-file .env') or complete executable Deno code covering the common cases: serving locally, curl testing, CORS, JWT auth, secrets, deploy, Stripe webhooks, pg_cron scheduling, and shared code. This matches the fully executable top anchor. | 5 / 5 |
Workflow Clarity | The create -> serve -> test -> deploy sequence is implicitly present across sections, but there are no validation checkpoints or error-recovery steps (e.g., 'supabase functions logs' after deploy, verifying a deployed endpoint). Since deploy, secrets set, and delete are batch/outward operations lacking verification steps, workflow clarity is capped at 3 per the rubric's feedback-loop rule. | 3 / 5 |
Progressive Disclosure | Headers are clear and a References section signals reference files, but the link to references/deno-imports.md points to a file that does not exist in the bundle, and long pattern content (the full Stripe webhook example, database webhook, and shared-code section) is inlined in SKILL.md when references/function-patterns.md exists for exactly that purpose. This matches 'content that should be separate is inline' rather than the well-split level 4. | 3 / 5 |
Total | 15 / 20 Passed |