Content
85%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.
The body is an exceptionally actionable, well-sequenced migration runbook: complete scripts, precise mapping tables, decision gates, and validation feedback loops at every fragile stage. Its weaknesses are structural — a fully inlined ~590-line file with no scripts/ or references/ split despite naming script paths in its own code comments — plus inline time-sensitive dates.
Suggestions
Move the two full scripts into actual scripts/ bundle files (matching the paths already named in the code comments) and reference them by path, keeping only usage notes, decision logic, and key excerpts inline.
Move the large mapping tables (Step 1 replace-list, Step 2 catalog mapping, Step 4 webhook event map) into references/ files linked one level deep from their steps, shortening SKILL.md to an overview.
Quarantine time-sensitive details — the March 31, 2027 deadline and the November 2026 API-reference snapshot note — in a clearly labeled section so staleness is easy to detect and update.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with non-obvious domain knowledge (field mappings, event mappings, API quirks) and re-teaches nothing Claude already knows; nearly every table and code block earns its place. Not 5: time-sensitive specifics — "Lemon Squeezy stops processing transactions... on March 31, 2027" and "as of November 2026" — sit inline rather than in a quarantined section, and a few long explanatory passages (e.g. the discounts paragraph) could be tightened. Not 3: there is no padded or generic explanation anywhere. | 4 / 5 |
Actionability | Fully executable throughout: a complete grep command with a key-redacting sed filter, two complete TypeScript scripts (lemon-squeezy-inventory.ts, lemon-squeezy-subscriber-file.ts), SQL DDL for the schema and license tables, an SDK discount-create snippet, the env var block, and the exact run command "node --env-file=.env.local --import tsx scripts/<name>.ts". Copy-paste ready and covering the common cases. | 5 / 5 |
Workflow Clarity | Six explicitly ordered steps, a "Decide with the user first" gate, a cutover sequence with "don't skip ahead", and a "Verify the integration" checklist. Validation feedback loops are present for this batch operation: "open the saved file and compare one subscription... against the field names", "Only clean rows reach the file... then fix the inputs and rerun" via needs-fixing.txt, and post-import reconciliation. Not 4: checkpoints are explicit and recurring, with error-recovery loops at each fragile stage. | 5 / 5 |
Progressive Disclosure | Everything lives in a single ~590-line SKILL.md with no bundle files: the two large scripts are inlined even though the skill itself labels them "// scripts/lemon-squeezy-inventory.ts" and "// scripts/lemon-squeezy-subscriber-file.ts", and the big mapping tables (Step 1 replace-list, Step 2 catalog map, Step 4 webhook map) would fit naturally in references/. Not 2: section structure is strong with clear, well-named headers throughout. Not 4: no references exist at all and the file is far beyond the under-50-line simple-skill exception. | 3 / 5 |
Total | 17 / 20 Passed |