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.
An exceptionally actionable, well-sequenced migration guide whose code, commands, and mapping tables are directly executable and whose batch operations are guarded by real validation loops. Its weaknesses are structural: everything is inlined in one very long SKILL.md with no bundle files, and a few guidance points are stated more than once.
Suggestions
Move the two full TypeScript scripts (lemon-squeezy-inventory.ts, lemon-squeezy-subscriber-file.ts) into a scripts/ directory and keep only run instructions and input/output contracts inline.
Split the webhook event-mapping and catalog-mapping tables into a references/ file, surfacing only the flagged/exception rows inline at the point of use.
De-duplicate guidance repeated across "Read this first", Step 6, "Cut over", and "Common pitfalls" (cancellation timing, card_brand grouping) into a single canonical location.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The prose is dense and migration-specific with virtually no explanation of concepts Claude already knows, but a few points are repeated across sections (cancellation timing in Lemon Squeezy appears in "Read this first", "Cut over", and "Common pitfalls"; the card_brand/payment_processor grouping appears in both Step 6 and the pitfalls), so minor trimming is possible. It is not 5 given these repeats and the overall 59KB size, and not 3 since nearly every sentence carries non-derivable, task-specific facts. | 4 / 5 |
Actionability | The body provides copy-paste-ready material throughout: an exact grep/sed audit command, two complete executable TypeScript scripts, SQL DDL, a full webhook handler with SDK imports, and precise env-var and API-permission lists. The two stubbed handler branches are explicitly justified app-specific fulfillment, not pseudocode gaps. | 5 / 5 |
Workflow Clarity | Steps 1–6 plus "Cut over" and "Verify the integration" give a clear, ordered sequence with explicit validation checkpoints and feedback loops: field-checking the snapshot against the API reference, "Report the three counts and show needs-fixing.txt ... then fix the inputs and rerun", confirming Paddle IDs before writing the map, sandbox testing, and post-import reconciliation — exactly the validation the batch subscriber-file operation requires. | 5 / 5 |
Progressive Disclosure | There are no bundle files (references/, scripts/, assets/ all absent), so all ~590 lines live inline in SKILL.md, including two full scripts already labeled with scripts/ path comments and large webhook/catalog mapping tables that clearly belong in separate files. Section structure is good, but content that should be separate is inline — more than the "minor organization gaps" of score 4. | 3 / 5 |
Total | 17 / 20 Passed |