CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/stripe-subscription-billing-test-author

Builds test suites for Stripe recurring-billing flows: trial-to-paid conversion, proration on plan upgrade and downgrade, dunning on failed renewal, cancel and reactivation, and the full subscription webhook event matrix (invoice.payment_failed, customer.subscription.updated, customer.subscription.deleted, invoice.paid). Uses Stripe Billing test clocks (POST /v1/test_helpers/test_clocks) to time-travel through billing cycles without calendar delay. Distinct from stripe-test-cards-and-webhooks (one-time PaymentIntents) and payment-flow-test-author (idempotency + replay robustness). Does not cover single-event CLI replay or handler idempotency testing (see payment-flow-test-author for those). Use when authoring tests for subscription or recurring-billing integrations.

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill body with executable code, clear sequencing, and validation checkpoints. Minor conciseness gains are available by trimming repeated citation phrases, and progressive disclosure could improve if a large reference table were moved into a bundled file.

Suggestions

Consolidate the repeated 'Per docs.stripe.com/...' citation prefixes and the trailing References section into a single references list to reduce redundancy.

Consider moving the full webhook event matrix (Step 6) into a bundled references file that the overview links to, enabling one-level-deep progressive disclosure.

DimensionReasoningScore

Conciseness

Efficient and mostly assumes Claude's competence, but repeated 'Per docs.stripe.com/...' citation phrases and a References section that re-lists links already embedded inline add minor padding that could be trimmed.

4 / 5

Actionability

Fully executable copy-paste-ready TypeScript with real Stripe SDK calls, real test cards (pm_card_visa, 4000...0341), concrete endpoints, and tabular event/field mappings covering the common cases.

5 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced with explicit validation checkpoints ('Always poll ... until status is ready before asserting', waitForClockReady) and an Anti-patterns feedback section, though a full validate→fix→retry loop is not deeply elaborated.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Overview, Lifecycle, Steps 1–6, Running, CI, Anti-patterns, Limitations, References), but it is a single ~340-line inline file with no bundle files or one-level-deep references to split into.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, complete, and distinctive description that names concrete scenarios, includes an explicit 'Use when' trigger, and draws clear boundaries against sibling skills. Only minor synonym coverage is missing from the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete test scenarios by name — 'trial-to-paid conversion, proration on plan upgrade and downgrade, dunning on failed renewal, cancel and reactivation' — plus a specific webhook event matrix, giving comprehensive coverage of concrete actions.

5 / 5

Completeness

Explicitly answers both 'what' (builds test suites for the named scenarios) and 'when' ('Use when authoring tests for subscription or recurring-billing integrations') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Good coverage of natural terms ('subscription', 'recurring-billing', 'Stripe', 'dunning', 'proration') with an explicit trigger phrase, but a few common synonyms a user might say (e.g. 'renewal testing', 'recurring payments testing') are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche with explicit boundary guidance — 'Distinct from stripe-test-cards-and-webhooks' and 'Does not cover single-event CLI replay or handler idempotency testing (see payment-flow-test-author)' — minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents