Content
65%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 a rich, executable Stripe integration reference with strong actionability and reasonable conciseness. Its weaknesses are the lack of an explicit end-to-end workflow with validation checkpoints and the monolithic single-file structure with no progressive disclosure.
Suggestions
Add an ordered end-to-end integration checklist with explicit validation checkpoints (e.g., 1. set up client, 2. create products/prices, 3. build checkout, 4. configure & verify webhooks locally with Stripe CLI, 5. test upgrade/downgrade proration), framed as a validate→fix→retry loop.
Split large reference material (full webhook handler, plan/price configuration, CLI testing) into separate files under references/ and link to them from SKILL.md so the top-level file stays a lean overview.
Remove the redundant Overview/Core Capabilities sections that repeat the frontmatter description, and fix the missing comma in the checkout customer creation snippet so the code is copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean executable code, but the Overview duplicates the frontmatter description verbatim and the Core Capabilities bullets overlap the detailed sections below — minor trimming possible. Not 5 because of that redundant preamble. | 4 / 5 |
Actionability | Extensive concrete, mostly copy-paste-ready code plus CLI commands and test cards, but the checkout snippet has a real syntax error (missing comma between `name: "username-undefined"` and `metadata:`), a minor copy-paste gap. Not 5 because of that defect; not 3 because the bulk is genuinely executable. | 4 / 5 |
Workflow Clarity | A clear subscription lifecycle state machine and idempotent webhook retry logic are present, but there is no end-to-end sequenced integration workflow with explicit validate→fix→retry checkpoints. Not 4 because checkpoints are implicit and scattered; not 2 because per-feature structure and the webhook retry loop are coherent. | 3 / 5 |
Progressive Disclosure | Well-organized with clear section headers, but all content (~477 lines, including full webhook handlers) is inlined in one file with no external references. Not 4 because content that belongs in separate reference files is inlined; not 2 because sectioning is solid. | 3 / 5 |
Total | 14 / 20 Passed |