Name: stripe-best-practices
Rating: 91.8 (1 reviews)
Author: stripe

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.

1.86x

Quality

89%

Does it follow best practices?

Impact

95%

1.86x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is stripe-best-practices in stripe/ai

Quality

Content

78%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 content is a well-structured overview that routes Stripe integration questions to appropriately scoped one-level-deep references with concrete commands and guarded rules. It could be tightened slightly around the SDK version table and a few explanatory clauses.

Suggestions

Trim the explanatory rationale under the payment_method_types rule to the directive plus the one-line reason; the dynamic-payment-methods benefits clause is context Claude largely already knows.

Consider collapsing the SDK version table into a single line or moving it to a reference, since per-language version numbers are time-sensitive and add token weight to the core SKILL.md.

Add an explicit error-recovery note for the sandbox/MCP flow (e.g. what to do if 'stripe sandbox claim' fails) to turn the current guarded rules into a full validate-fix-retry loop.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient and assumes Claude's knowledge, but the dynamic-payment-methods rationale and the full multi-language SDK version table add bulk that could be trimmed; time-sensitive version info is justified as 'latest' guidance.	4 / 5
Actionability	It provides concrete executable commands (e.g. 'npm i -g @stripe/cli', 'stripe sandbox create', 'stripe whoami --format json') and exact endpoints/parameters in the routing table, with only minor gaps since full code samples are delegated to references.	4 / 5
Workflow Clarity	A clear first step ('Read the relevant reference file before answering…') and guarded critical rules act as checkpoints (e.g. confirm registration before enabling automatic_tax), though an explicit error-recovery feedback loop is absent.	4 / 5
Progressive Disclosure	The body is a clear overview with a routing table pointing one level deep to real, verified reference files (payments, connect, billing, tax, treasury, security) via well-signaled <references/...> paths, with no nested references.	5 / 5
	Total	17 / 20 Passed

Description

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

This is a strong, comprehensive description that clearly states what the skill does and when to use it, with concrete domain-specific terminology and rich natural trigger terms. It is clearly distinguishable from other skills.

Dimension	Reasoning	Score
Specificity	The description lists many concrete capabilities with specific API and parameter names such as 'Checkout Sessions vs PaymentIntents', 'Accounts v2, controller properties', and 'automatic_tax, product tax codes', giving comprehensive concrete coverage.	5 / 5
Completeness	It explicitly answers both what (guides Stripe integration decisions across named domains) and when ('Use when building, modifying, or reviewing any Stripe integration…') with concrete trigger phrases, in third-person voice.	5 / 5
Trigger Term Quality	It includes comprehensive natural trigger terms and synonyms a user would say — 'accepting payments', 'building marketplaces', 'collecting sales tax, VAT, or GST', 'creating connected accounts', and 'secure key handling'.	5 / 5
Distinctiveness Conflict Risk	It is firmly Stripe-specific with distinct triggers (Stripe Tax, Connect accounts, Treasury), creating a clear niche with minimal risk of triggering for the wrong skill.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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: stripe/ai
Path: providers/cursor/plugin/skills/stripe-best-practices/SKILL.md
Commit: 6838252

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.