stripe-best-practices

Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial accounts, integration surfaces (Checkout, Payment Element), and migrating from deprecated Stripe APIs. Use when building, modifying, or reviewing any Stripe integration — including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, or creating connected accounts.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured routing skill that defers detail to real one-level-deep reference files and gives concrete, decisionable guidance. Its only weakness is a stale-prone inline API version number that should be isolated from the lean core content.

Suggestions

Move the pinned API version ("2026-02-25.clover") into a dedicated versioning/deprecated section or a reference file so the lean core content does not carry time-sensitive information that will go stale.

Add a one-line fallback instruction for requests that match none of the routing-table rows (beyond the generic "Key documentation" links) so Claude has an explicit next step.

Consider noting where to find example request/response payloads (or pointing to one of the reference files) so the routing decision connects to executable code rather than only API names.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's intelligence, but it opens with a hard-coded version number ("Latest Stripe API version: 2026-02-25.clover") that is time-sensitive and not placed in a deprecated/old-patterns section, which the rubric penalizes.	2 / 3
Actionability	The routing table maps concrete scenarios to specific APIs and a literal endpoint ("Accounts v2 (`/v2/core/accounts`)"), and the directive to read the named reference file is specific and decisionable guidance for this instruction/routing skill.	3 / 3
Workflow Clarity	The process is unambiguous for a routing skill — match the task to the routing table, then "Read the relevant reference file before answering any integration question or writing code" — with no destructive or batch operations that would require validation checkpoints.	3 / 3
Progressive Disclosure	The body is a concise overview with well-signaled, one-level-deep references (payments.md, connect.md, billing.md, treasury.md — all verified to exist) plus external doc links for non-domain requests, splitting detail appropriately into bundle files.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, third-person description that names concrete capabilities and provides an explicit, natural-language trigger clause covering common user phrasings. It is specific, complete, and clearly distinct from other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete domains and actions — "API selection (Checkout Sessions vs PaymentIntents)", "Connect platform setup (Accounts v2, controller properties)", "billing/subscriptions", "Treasury financial accounts", and "migrating from deprecated Stripe APIs" — rather than vague language.	3 / 3
Completeness	It explicitly answers both what (guides Stripe integration decisions across named domains) and when (an explicit "Use when building, modifying, or reviewing any Stripe integration..." trigger clause).	3 / 3
Trigger Term Quality	The "Use when..." clause covers natural phrases users would say — "accepting payments", "building marketplaces", "processing payments", "setting up subscriptions", and "creating connected accounts" — giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	It occupies a clear Stripe-integration niche with distinct triggers, and the combination of named APIs and trigger scenarios makes it unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 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: openai/plugins
Path: plugins/build-web-apps/skills/stripe-best-practices/SKILL.md
Commit: 11c74d6

Reviewed: 17 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.