CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stripe-integration

Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/payment-processing/skills/stripe-integration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 solid overview tier: the Checkout-vs-Payment-Intents decision guidance and executable Quick Start / Testing code are its strengths, and it correctly pushes detailed patterns into a real one-level-deep reference. Weaknesses are a redundant restatement of the description, generic filler bullets, and no sequenced workflow with validation checkpoints (notably webhook signature verification).

Suggestions

Delete the opening line that duplicates the frontmatter description verbatim, and cut or compress the generic 'Customer Management' and subscription 'Components' bullet lists, keeping only Stripe-specific decision guidance.

Add an explicit numbered integration workflow with validation checkpoints, e.g., 1) create Checkout Session, 2) redirect to session.url, 3) verify webhook signature before processing events, 4) confirm payment status server-side via retrieve before fulfilling.

Split references/details.md into topic-focused files (webhooks.md, refunds.md, subscriptions.md) and link each from the corresponding body section so navigation targets are specific rather than one catch-all file.

DimensionReasoningScore

Conciseness

The opening line 'Master Stripe payment processing integration for robust, PCI-compliant payment flows...' restates the frontmatter description verbatim, and the 'Customer Management' and subscription 'Components' bullets (e.g., 'Product: What you're selling', 'Create and manage customer records') are generic filler Claude already knows. The rest is efficient decision guidance and code, so it sits at 'mostly efficient but includes some unnecessary explanation' rather than the padded anchor 2 or the lean anchor 4/5.

3 / 5

Actionability

The Quick Start and Testing sections provide copy-paste-ready executable code with real parameter values ('ui_mode', test card numbers, asserts), and concrete API guidance like 'ui_mode='custom''. It is not a 5 because webhook handling, refunds, and customer management have no inline code or commands — those common cases are only deferred to references/details.md.

4 / 5

Workflow Clarity

There is an implied sequence (create session -> redirect to session.url -> success URL) and a Testing section with an assert, but no explicitly ordered integration workflow or validation checkpoints (e.g., verify webhook signatures before trusting events, confirm payment status server-side). That matches 'sequence present but checkpoints missing or implicit' rather than anchor 4's 'most checkpoints present'.

3 / 5

Progressive Disclosure

The body is a well-organized overview with one clearly signaled, one-level-deep reference ('Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient'), and that file exists with substantial executable patterns. It falls short of anchor 5 because all advanced topics (webhooks, refunds, customer management, five implementation patterns) are funneled into a single catch-all details.md rather than an appropriately split, easy-to-navigate reference set.

4 / 5

Total

14

/

20

Passed

Description

87%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 in third-person imperative voice: it states concrete capabilities and follows with an explicit, naturally worded 'Use when' trigger clause, so both completeness and distinctiveness are at the top anchors. The only gaps are modest — a few capabilities (refunds, disputes, Connect) and a few natural trigger synonyms (billing, webhooks) are omitted.

DimensionReasoningScore

Specificity

'Implement Stripe payment processing... including checkout, subscriptions, and webhooks' names the domain plus several concrete capability areas (PCI-compliant flows, checkout, subscriptions, webhooks). It stops short of anchor 5 because capabilities the skill itself covers — refunds, disputes, payment-method management, Stripe Connect — are absent.

4 / 5

Completeness

It explicitly answers both parts: a clear 'what' ('Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks') followed by an explicit 'when' with concrete trigger phrases ('Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows'). This matches the anchor-5 good_overall_example pattern exactly; anchor 4 would require the 'when' to be less explicit.

5 / 5

Trigger Term Quality

'Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows' contains natural phrases users would actually say (stripe payments, subscription systems, checkout flows). It misses common variations like 'billing', 'payment processing', or 'webhooks' as triggers, so it fits anchor 4's 'good keyword coverage; a few natural terms missing' rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The vendor-named niche ('Stripe payment processing') plus vendor-specific triggers ('integrating Stripe payments', 'building subscription systems') gives a clear niche with minimal overlap risk against non-Stripe or non-payment skills. It mirrors the anchor-5 example's structure; anchor 4's 'minor overlap risk with closely related skills' does not fit since no sibling skill in this space shares these triggers.

5 / 5

Total

18

/

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.

Repository

wshobson/agents

Path

plugins/payment-processing/skills/stripe-integration/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.