CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/stripe-test-cards-and-webhooks

Wraps Stripe API testing patterns: test-mode initialization, the canonical test cards (4242 success; 4000 0000 0000 0002 declined; 4000 0027 6000 3184 3DS challenge per the 3DS flows reference in payment-flow-states-reference), the Stripe CLI webhook flow (`stripe listen --forward-to`), the Stripe CLI fixture commands (`stripe trigger payment_intent.succeeded`), and the webhook signature verification (Stripe-Signature header + HMAC-SHA256). Use when testing Stripe-integrated code.

72

Quality

90%

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.

An actionable, well-structured testing skill whose executable examples and anti-pattern table make it easy to apply directly. The main gaps are a repeated CLI command and the absence of an explicit validation checkpoint in the local webhook-listen workflow.

Suggestions

De-duplicate the `stripe listen --forward-to` command so it appears once (e.g. define it in the CLI section and reference it from Running) to trim tokens.

Add an explicit validate-fix-retry step for the local webhook-forwarding flow (e.g. confirm `stripe listen` printed a secret and the handler returned 200 before running the suite).

Consolidate the test-card table and the inline PaymentIntent card values into named constants referenced once, reducing redundancy between the Authoring and test sections.

DimensionReasoningScore

Conciseness

The body is lean with code blocks, a test-card table, and minimal concept over-explanation, but the `stripe listen --forward-to` command is repeated across the CLI and Running sections and a few lines could be tightened.

4 / 5

Actionability

Copy-paste-ready TypeScript test snippets, concrete CLI commands (`stripe listen --forward-to`, `stripe trigger payment_intent.succeeded`), a full test-card table, and a CI YAML cover the common Stripe test cases end-to-end.

5 / 5

Workflow Clarity

The Install → Initialize → test-cards → test-snippets → Running → CI sequence is clear with the webhook-signature verification embedded in the test, but there is no explicit validate-fix-retry feedback loop for the local webhook-forwarding setup.

4 / 5

Progressive Disclosure

A single self-contained file with well-organized section headers (Overview, Authoring, Running, CI, Anti-patterns, Limitations, References) and one-level companion-skill pointers; no bundle files exist, so structure is good but there is nothing to split out.

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, third-person description that crisply states both what the skill wraps and when to invoke it, anchored by concrete test-card and CLI trigger terms. Minor keyword synonym coverage keeps it just short of perfect on trigger-term breadth.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'test-mode initialization', 'canonical test cards (4242 success... 4000 0000 0000 0002 declined... 3DS challenge)', 'Stripe CLI webhook flow', 'fixture commands', 'webhook signature verification (Stripe-Signature header + HMAC-SHA256)' — giving comprehensive, action-level coverage.

5 / 5

Completeness

Both poles are explicit: the 'what' is enumerated via the wrapped testing patterns, and the 'when' is the concrete trigger phrase 'Use when testing Stripe-integrated code'.

5 / 5

Trigger Term Quality

Natural terms like 'Stripe', 'test cards', 'webhook', '3DS challenge', 'Stripe CLI' and the explicit trigger 'Use when testing Stripe-integrated code' are present, but a few natural variants (e.g. 'Stripe payments', 'payment integration testing', 'webhook signature') are absent.

4 / 5

Distinctiveness Conflict Risk

The Stripe-test-mode niche is sharply scoped (test cards, webhook fixtures, signature verification) with distinct triggers, leaving minimal overlap risk with non-Stripe skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents