Content
82%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, well-sequenced skill: executable code end-to-end, a genuine ordering-correctness mechanism, explicit verification steps, and a pitfalls section full of real failure modes. The main improvements are trimming known-boilerplate and rationale sections, and splitting reference material (Supabase setup, backfill detail) into bundle files.
Suggestions
Move the Supabase createServerClient boilerplate and the backfill/MCP details into a reference file (e.g. references/backfill.md), keeping SKILL.md a lean overview with one-level-deep pointers.
Consolidate the out-of-order/last_event_at explanation (currently given in the schema section, the handler notes, and the pitfalls) into one authoritative spot, and trim the 'Why mirror state at all?' section to a sentence.
Add a short failure-recovery note to the verification section (what to inspect if rows don't land or status doesn't flip, e.g. check the destination's Usage type and event subscription list).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bulk is dense, non-obvious domain knowledge (the last_event_at ordering guard, status semantics table, scheduled-change lifecycle, pitfalls) that earns its tokens. However, the ~50-line Supabase createServerClient boilerplate, the 'Why mirror state at all?' rationale section, and the out-of-order guard being explained three times (schema notes, process-event notes, pitfalls) are minor over-explanation that could be trimmed. Fits 'Efficient; minor instances of over-explanation' (4) rather than 5, where every token earns its place, and clearly above 3, which requires more pervasive padding. | 4 / 5 |
Actionability | Fully executable throughout: complete SQL DDL and upsert functions with the ordering guard, typed TypeScript webhook handlers, customer-mapping and query helpers, a runnable MCP backfill snippet, and a cron reconciliation route — copy-paste ready and covering the common cases (Supabase and non-Supabase, MCP and SDK backfill). Matches 'Fully executable; copy-paste ready code or commands'. | 5 / 5 |
Workflow Clarity | The sequence is clear (schema → clients → user mapping → event handlers → status semantics → scheduled changes → querying → backfill) with an explicit 6-step verification checklist, and the batch backfill is validated (ordering guard, 'run it once before flipping access gating', 50-call-cap handling with an SDK fallback), so the destructive/batch cap does not apply. It falls short of 5 only because the verification steps say what to confirm but give no failure-recovery path (e.g. what to check if the row never lands), a minor validation gap. | 4 / 5 |
Progressive Disclosure | No bundle files exist (no references/, scripts/, or assets/), so this scores the body structure itself: clear section headers, easy linear navigation, and clearly signaled cross-references to sibling skills ('webhooks', 'checkout-web', 'subscription-cancel', 'sandbox-testing') and external docs. Not 5 because some inlined content — the Supabase client boilerplate and the backfill/MCP details — is a natural candidate for one-level-deep reference files in a ~450-line body; not 3 because what is inline is mostly the core deliverable rather than content that clearly belongs elsewhere. | 4 / 5 |
Total | 17 / 20 Passed |