CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/stripe-test-cards-and-webhooks

Use for any question or task about testing Stripe payments, including one webhook handler and checkout that fails for 3D Secure cards: test-mode keys, test cards for success, declines and 3D Secure, stripe listen to forward webhooks locally, stripe trigger fixtures, and Stripe-Signature verification.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

71%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, information-dense testing reference with real code and genuinely non-obvious Stripe gotchas (test-clock limits, unpaid bank-debit sessions, concurrent fulfillment). Its main weaknesses are structural: a monolithic 280-line body with no progressive-disclosure file split, plus small placeholder gaps in two code examples.

Suggestions

Move the advanced deep-dives — the test-clocks section and the checkout-fulfillment rules — into reference files (e.g., references/test-clocks.md, references/fulfillment.md) and keep a short summary plus a clearly signaled one-level-deep pointer in SKILL.md.

Replace the `{...}` placeholders in the idempotency test and the `data: {...}` in the webhook payload example with complete, executable code so every example is copy-paste ready.

Cite docs.stripe.com/testing once (in the References section) rather than linking it four times throughout the body.

DimensionReasoningScore

Conciseness

Dense tables, code, and non-obvious Stripe-specific rules with no padding; it assumes competence (never explains what Stripe or webhooks are). Not 5: docs.stripe.com/testing is cited four separate times and a few transitions ("Rules from the same page that break naive tests") could be trimmed.

4 / 5

Actionability

Concrete, runnable TypeScript tests, bash commands, SQL, and CI YAML cover the common cases. Not 5: the idempotency example uses a `{...}` placeholder, the webhook payload has `data: {...}`, and the handler test depends on an external `./stripe-webhook` module — minor gaps that keep it from fully copy-paste ready.

4 / 5

Workflow Clarity

A clear topical sequence (Install → Initialize → test cards → tests → webhooks/CLI → Running → CI) with real checkpoints: test assertions, the test-clock `ready` polling loop, the fulfillment expected-outcome matrix, and an anti-patterns-to-fix table. Not 5: there is no single explicitly ordered end-to-end procedure with validate-and-retry steps for a newcomer.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so all ~280 lines live in SKILL.md, including advanced deep-dives (test-clock rules, checkout fulfillment) that belong in separate reference files. Not 4: substantial content that should be separate is inlined; not 2: clear headers, tables, and a References section keep it navigable.

3 / 5

Total

15

/

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 strong description: explicit trigger guidance followed by a comprehensive, concrete list of capabilities. The only blemishes are a slightly confusing mid-sentence clause ("including one webhook handler and checkout that fails for 3D Secure cards") and a few missing natural synonyms such as "Stripe test mode" or "3DS".

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "test-mode keys", "test cards for success, declines and 3D Secure", "stripe listen to forward webhooks locally", "stripe trigger fixtures", "Stripe-Signature verification" — covering the domain comprehensively. Not 4: the coverage spans keys, cards, local webhook forwarding, event fixtures, and signature verification with no real gaps.

5 / 5

Completeness

"Use for any question or task about testing Stripe payments" explicitly and specifically answers *when*, and the colon-enumeration concretely answers *what* (keys, cards, webhook forwarding, trigger fixtures, signature verification). Not 4: the when-clause is explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Good natural-term coverage: "testing Stripe payments", "test cards", "3D Secure", "webhook", "stripe listen" are phrases users would actually say. Not 5: common synonyms and variations like "Stripe test mode", "3DS", or "sandbox" are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped tightly to Stripe payment testing with Stripe-only triggers ("stripe listen", "stripe trigger", "Stripe-Signature"), giving it a clear niche with minimal conflict risk. Not 4: the Stripe qualifier cleanly separates it from generic payment-testing 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page