Content
67%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 dense with genuinely useful, domain-specific material — event matrices, test cards, anti-patterns, and limitations — organized into a clear stepwise workflow. Its main costs are redundant citation boilerplate and a conceptual opening, plus undefined helper functions and an unexplained webhook-capture mechanism that leave the guidance just short of fully executable.
Suggestions
Trim the conceptual Overview paragraph and collapse the repeated 'Per docs.stripe.com/...' prefixes (the References section already lists them once) to reduce token cost without losing information.
Define or inline the helper functions used across snippets (toEpoch, waitForClockReady, getLatestInvoice) so the code examples are copy-paste ready.
Add a short step or snippet showing how webhook events are actually captured and asserted in a test-clock-driven test (e.g., a webhook test utility or event-receipt helper), since the skill requires these assertions throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains subscription-billing concepts Claude already knows ("Subscription billing is distinct from one-time payments. A customer's card is charged on a schedule..."), the "Per docs.stripe.com/..." citation prefix repeats roughly a dozen times, and the References section re-lists the same links already cited inline — mostly efficient but with unnecessary explanation and clear tightening opportunities. | 3 / 5 |
Actionability | Concrete TypeScript snippets, specific test cards (pm_card_chargeDeclinedInsufficientFunds, 4000 0000 0000 0341), and runnable commands (stripe listen, npm test, CI yaml) are mostly executable, but helper functions (toEpoch, waitForClockReady, getLatestInvoice) are used without definitions and webhook assertions appear only as comments — minor gaps that keep it below copy-paste-ready. | 4 / 5 |
Workflow Clarity | Steps 1–6 are clearly sequenced with explicit checkpoints ("Poll until clock.status === 'ready' before asserting", preview-before-apply proration) and the anti-patterns table acts as a checklist, but the skill repeatedly instructs asserting webhook events without ever showing how to capture webhooks in a test — a minor validation gap in the required flow. | 4 / 5 |
Progressive Disclosure | No bundle files exist, and the ~330-line body is well-sectioned (Steps, Anti-patterns, Limitations, References) with clearly signaled external doc links and no nested references; minor gaps only, as the webhook event matrix and CI config could arguably live in separate reference files given the length. | 4 / 5 |
Total | 15 / 20 Passed |