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 3ds-test-flow-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.

73

Quality

92%

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

80%

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

The body is lean and highly actionable with executable examples, but workflow clarity is capped by missing validation/feedback checkpoints and progressive disclosure suffers because several referenced companion files do not exist as bundle files.

Suggestions

Add explicit validation checkpoints to the webhook and CI workflows — e.g. assert the signing secret matches before running tests, and a validate→fix→retry loop around webhook handler failures.

Either add the referenced companion files (`3ds-test-flow-reference`, `payment-flow-states-reference`, `pci-dss-scope-reference`, builders) as bundle files or remove the dangling references so navigation resolves to real files.

Surface a short ordering note in 'Running' / 'CI integration' so the sequence (start `stripe listen` → seed fixtures → run tests → tear down) is unambiguous.

DimensionReasoningScore

Conciseness

Lean and table-driven; it assumes Claude knows what Stripe is and never pads with basic explanations — the test-card table, code blocks, and anti-pattern table each earn their tokens.

3 / 3

Actionability

Provides fully executable TypeScript, bash, and YAML snippets (PaymentIntent create, webhook handler test, `stripe listen --forward-to`, `stripe trigger`, CI config) that are copy-paste ready.

3 / 3

Workflow Clarity

Sections are sequenced (Install → Initialize → cards → tests → webhooks → CI) but lack explicit validation checkpoints and feedback loops; the webhook and CI workflows assert success without a validate→fix→retry path, keeping it below the top anchor.

2 / 3

Progressive Disclosure

Sections are well-organized, but the referenced catalogs/builders (e.g. `3ds-test-flow-reference`, `payment-flow-states-reference`) are not present as bundle files in the repo, so the references do not resolve to actual files and the structure is not clearly one-level-deep.

2 / 3

Total

10

/

12

Passed

Description

100%

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

The description is specific, trigger-rich, and complete, naming concrete capabilities (test cards, webhook flow, signature verification) and an explicit use-when clause. It is concise despite its density and clearly scoped to Stripe testing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "test-mode initialization", "canonical test cards", "Stripe CLI webhook flow", "stripe trigger payment_intent.succeeded", and "webhook signature verification (Stripe-Signature header + HMAC-SHA256)" — rather than vague language.

3 / 3

Completeness

Explicitly answers both what it does (wraps Stripe API testing patterns) and when to use it ("Use when testing Stripe-integrated code"), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Uses natural terms a user would actually say — "Stripe", "test cards", "webhook", "3DS challenge", "testing Stripe-integrated code" — covering common variations.

3 / 3

Distinctiveness Conflict Risk

Has a clear, narrow niche (Stripe test-mode + webhooks) with distinct triggers, unlikely to fire for non-Stripe skills.

3 / 3

Total

12

/

12

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