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 with validation and feedback loops at every stage, held back only by progressive disclosure: everything lives inline in one large SKILL.md rather than being split across bundle files. Moving the two full scripts and the detailed mapping tables into scripts/ and references/ files would complete the picture.
Suggestions
Move the complete lemon-squeezy-inventory.ts and lemon-squeezy-subscriber-file.ts scripts into a scripts/ bundle directory, keeping only their purpose, inputs, outputs, and the rerun/fix loop described inline.
Consider relocating the large variant-mapping and webhook-event mapping tables to a references/ file (e.g. references/mappings.md), leaving a short summary plus pointers in SKILL.md.
Tighten verbose table-cell prose and consolidate the deadline cautions into the single "Read this first" section to reduce token load.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with task-specific knowledge (field-level mapping tables, API quirks, rate limits, pitfalls) and never explains concepts Claude already knows, assuming competence throughout. A few passages could be trimmed — repeated deadline cautions and verbose explanatory prose inside table cells — and inline time-sensitive dates ("March 31, 2027", "as of November 2026") are not isolated in a dedicated section, so it falls short of the lean anchor 5. | 4 / 5 |
Actionability | The skill provides two complete copy-paste-ready scripts (inventory and subscriber-file generation), a full processEvent webhook handler, SQL DDL, an SDK discount-creation call, an importable ID-map utility, and a runnable grep audit command with a redaction filter. The few app-specific stubs (fulfillment, license key issuance) are explicitly justified placeholders backed by precise event-to-action tables, so the guidance is fully executable for the common cases. | 5 / 5 |
Workflow Clarity | Steps 1–6 are explicitly sequenced with validation checkpoints everywhere: snapshot fields are verified against the API reference before proceeding, the catalog proposal waits for user decisions on flagged rows, unplaceable rows go to needs-fixing.txt with a fix-the-inputs-and-rerun loop, sandbox testing gates the cutover, the cutover itself is strictly ordered ("Only then cancel"), and a post-import reconciliation checklist closes the loop. For a batch migration operation this matches the explicit-validation anchor exactly. | 5 / 5 |
Progressive Disclosure | Sections are well-organized and external references are clearly signaled (Related docs, paired skills, the migration guide URL), but there is no bundle at all: roughly 180 lines of complete scripts are inlined in a ~590-line monolithic SKILL.md — the skill even names their intended scripts/ paths — which matches the anchor of content that should be separate being inline. It is not a 4 because the split into scripts/ files is a substantial, not minor, organization gap. | 3 / 5 |
Total | 17 / 20 Passed |