stripe-best-practices
Guides Stripe integration decisions across API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, restricted keys, webhooks, OAuth). Use when building, modifying, or reviewing any Stripe integration, including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling.
82
86%
Does it follow best practices?
Impact
89%
2.69xAverage score across 2 eval scenarios
Advisory
Suggest reviewing before use
Security
1 medium severity finding. This skill can be installed but you should review these findings before use.
W009: Direct money access capability detected (payment gateways, crypto, banking)
What this means
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
Why it was flagged
Direct money access detected (high risk: 1.00). The skill is explicitly a Stripe integration guide and includes concrete, specific payment-execution capabilities: it references the Stripe API and SDK version, gives a CLI command to generate API keys (`stripe sandbox create`), prescribes API key usage, and lists specific payment APIs/endpoints and integrations (Checkout Sessions, PaymentIntent/Setup Intents, Connect Accounts, Billing, Financial Accounts, etc.). These are payment gateway and financial-account APIs that enable direct movement or management of funds and thus constitute direct financial execution authority.