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

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/payment-processing/skills/stripe-integration/SKILL.md

The canonical home for this skill is stripe-integration in wshobson/agents

SKILL.md
Quality
Evals
Security

Quality

Content

53%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.

The body delivers concrete, mostly copy-paste-ready Stripe patterns with good topical coverage, but it functions as a monolithic reference rather than a lean overview. Its two structural failures are inline duplication of material that the Resources section claims is in separate files, and eight referenced bundle files that do not exist in the bundle at all.

Suggestions

Create the referenced bundle files (references/webhook-handling.md, references/customer-management.md, assets/stripe-client.py, etc.) or remove them from the Resources section — currently every listed reference is a dead path.

Move the detailed webhook best-practices, customer-management, refund, and testing code out of SKILL.md into the corresponding reference files, keeping only a quick-start example and one-line pointers in the body to cut its ~450 lines substantially.

Add a short sequenced integration workflow with explicit validation checkpoints (e.g., 1. choose payment pattern, 2. implement, 3. register and verify webhook endpoint locally, 4. run test-card flows before production) instead of presenting topics as an unsequenced catalog.

DimensionReasoningScore

Conciseness

The body is ~450 lines that largely assume Claude's competence (no basic-concept tutorials), but it inlines full webhook handling, customer management, refund, and testing sections that duplicate content the Resources section says lives in references/webhook-handling.md, references/customer-management.md, etc. Mostly efficient but could be tightened significantly by pushing duplicated detail into the referenced files; not a 4 given the volume of inlined material and placeholder comments like "# Handle error".

3 / 5

Actionability

Mostly executable, concrete code: checkout session creation, PaymentIntent flow, subscription creation with expand, a complete Flask webhook endpoint with signature verification, refunds, and test card numbers. Minor gaps keep it from a 5: undefined helpers (is_event_processed, mark_event_processed, log_error), the frontend JavaScript embedded inside a Python docstring rather than usable code, and handler bodies that are comment placeholders ("# Update your database").

4 / 5

Workflow Clarity

The document is organized as a catalog of per-topic patterns rather than a sequenced integration workflow; an implicit order exists (pick a payment pattern → set up webhooks → test with test cards), and the Testing section provides some validation, but no explicit checkpoints or feedback loops are wired into the flow (e.g., no 'verify webhook endpoint receives events before go-live' step). Steps present with implicit sequence and sparse checkpoints fits the 3 anchor better than 4's 'most checkpoints present'.

3 / 5

Progressive Disclosure

The Resources section clearly signals references and assets, but none of the eight listed files (references/*.md, assets/*.py, assets/*.json) actually exist in the bundle, so navigation is broken. Meanwhile large blocks of content that clearly belong in those files (webhook best practices, customer management) are inlined in SKILL.md. Broken references plus inlined separable content matches the 2 anchor ('content that clearly belongs in separate files is inlined'); it avoids a 1 only because section headers and a dedicated Resources section provide real structure.

2 / 5

Total

12

/

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 that clearly states both capabilities and explicit trigger conditions, anchored by the distinctive 'Stripe' keyword. The only weaknesses are mild buzzword padding ('robust, PCI-compliant') and trigger coverage that omits a few natural variations like 'billing' or 'webhooks'.

DimensionReasoningScore

Specificity

Names the domain and several concrete capability areas — "payment processing ... including checkout, subscriptions, and webhooks" — but omits others the skill actually covers (refunds, disputes, customer/payment-method management), and "robust, PCI-compliant" is mild buzzword padding. Not a 5 because coverage has minor gaps; not a 3 because more than 1-2 concrete actions are explicitly listed.

4 / 5

Completeness

Explicitly answers both questions: what ("Implement Stripe payment processing for ... checkout, subscriptions, and webhooks") and when ("Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows") with three concrete trigger phrases. A clear 'what' plus an explicit 'Use when' clause with concrete triggers matches the top anchor; a 4 would require the 'when' to be less specific than it is.

5 / 5

Trigger Term Quality

The when-clause uses natural phrases users would say: "integrating Stripe payments", "building subscription systems", "implementing secure checkout flows". Missing common variations like "billing", "payment processing", "webhooks", or "Stripe API" in the trigger list, so not comprehensive enough for a 5; well above the generic-keyword level of a 3.

4 / 5

Distinctiveness Conflict Risk

"Stripe" is a clear niche identifier with distinct triggers (Stripe payments, subscription systems, checkout flows); minimal risk of triggering for a different skill. It occupies a well-defined payments niche unlike the broad-overlap anchors at 2-3.

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

15

/

16

Passed

Repository

Dicklesworthstone/pi_agent_rust

Path

tests/ext_conformance/artifacts/agents-wshobson/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.