Best practices for building Stripe integrations. Use when implementing payment processing, checkout flows, subscriptions, webhooks, Connect platforms, or any Stripe API integration.
76
63%
Does it follow best practices?
Impact
97%
1.27xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./external_plugins/stripe/skills/stripe-best-practices/SKILL.mdPayment API and checkout surface selection
CheckoutSessions API used
0%
100%
No Charges API
100%
100%
Stripe-hosted or embedded checkout
33%
100%
No Card Element
100%
100%
Dynamic payment methods
100%
100%
No Sources API
100%
100%
No Tokens API
100%
100%
Latest SDK import
100%
100%
Integration plan rationale
62%
100%
No createToken / createPaymentMethod misuse
100%
100%
Subscription billing and payment method storage
Billing/Subscription API used
100%
100%
Checkout for subscription frontend
30%
100%
SetupIntent for saving payment method
100%
100%
No Sources API
100%
100%
Sources API explicitly discouraged
100%
100%
No Charges API
100%
100%
CheckoutSessions preferred
37%
100%
No Tokens for card storage
100%
100%
Customer object created
100%
100%
Architecture rationale present
100%
100%
Stripe Connect platform architecture
Direct charges chosen
75%
100%
No destination charges mixed
90%
100%
on_behalf_of used
0%
30%
No Standard/Express/Custom terminology
0%
100%
Controller properties used
0%
100%
No Charges API
100%
100%
No Sources API
100%
100%
Capabilities configured
100%
100%
Charge model rationale
90%
100%
CheckoutSessions or PaymentIntents used
100%
100%
158ef95
Table of Contents
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.