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), 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, creating connected accounts, or implementing secure key handling.
90
86%
Does it follow best practices?
Impact
96%
1.29xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 an excellent skill description that thoroughly covers the Stripe integration domain with specific product names, API references, and concrete use cases. It includes a well-structured 'Use when...' clause with natural trigger terms that developers would actually use. The description is comprehensive without being padded, and its Stripe-specific terminology makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial accounts, integration surfaces, migrating from deprecated APIs, and security best practices with specific examples like API key management, restricted keys, webhooks, OAuth. | 3 / 3 |
Completeness | Clearly answers both 'what' (guides Stripe integration decisions across multiple domains) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios like building marketplaces, accepting payments, setting up subscriptions, and implementing secure key handling. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Stripe integration', 'payments', 'subscriptions', 'marketplaces', 'connected accounts', 'Checkout', 'PaymentIntents', 'webhooks', 'API key', 'billing'. These are terms developers naturally use when working with Stripe. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the description is clearly scoped to Stripe-specific integrations with named Stripe products and APIs (Checkout Sessions, PaymentIntents, Connect, Treasury, Accounts v2). This is unlikely to conflict with generic payment or API skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured integration routing skill that efficiently directs Claude to the right Stripe API and reference material based on the use case. Its strengths are excellent conciseness, clear progressive disclosure via a routing table with reference links, and a critical rule about payment_method_types that prevents a common mistake. Its main weakness is the lack of executable code examples in the main file and the absence of explicit multi-step workflow sequences with validation checkpoints.
Suggestions
Add at least one minimal executable code example (e.g., a Checkout Session creation) to improve actionability in the main skill file, even if detailed examples live in reference files.
Consider adding a brief workflow sequence for the most common integration path (e.g., 1. Choose integration surface → 2. Implement → 3. Test with test keys → 4. Review go-live checklist) with explicit validation checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It uses a routing table to convey integration decisions concisely, states critical rules without over-explaining, and assumes Claude understands Stripe concepts. Every section earns its place with no unnecessary preamble or concept explanations. | 3 / 3 |
Actionability | The routing table and critical rules provide concrete guidance on which APIs to use and what to avoid, but there are no executable code examples or copy-paste ready snippets in the main skill file. The actionability depends heavily on the referenced files which are not provided for evaluation. | 2 / 3 |
Workflow Clarity | The routing table provides clear decision-making for which API to use, and the instruction to 'read the relevant reference file before answering' establishes a workflow. However, there are no explicit multi-step sequences with validation checkpoints for integration tasks, and no feedback loops for error recovery in what can be complex, multi-step integration processes. | 2 / 3 |
Progressive Disclosure | The skill is structured as a clear overview with a well-organized routing table pointing to one-level-deep reference files (payments.md, connect.md, billing.md, treasury.md, security.md). Navigation is easy and references are clearly signaled with descriptive labels. However, since no bundle files were provided, we cannot verify the referenced paths exist, but the structure itself is exemplary. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.