stripe-best-practices
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.mdQuality
Discovery
89%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 solid skill description with excellent trigger terms and completeness. The main weakness is the vague 'best practices' framing which doesn't specify concrete actions Claude will perform. The description would benefit from listing specific capabilities like 'implement webhook handlers, configure checkout sessions, set up subscription billing'.
Suggestions
Replace 'Best practices for building' with specific actions like 'Implements webhook handlers, configures checkout sessions, sets up subscription billing, handles Connect platform onboarding'
Add concrete deliverables or outputs the skill produces (e.g., 'generates idempotent API calls, creates proper error handling')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Stripe integrations) and lists several areas (payment processing, checkout flows, subscriptions, webhooks, Connect platforms), but 'best practices' is vague and doesn't describe concrete actions like 'implement webhook handlers' or 'configure subscription billing'. | 2 / 3 |
Completeness | Clearly answers both what ('Best practices for building Stripe integrations') and when ('Use when implementing payment processing, checkout flows, subscriptions, webhooks, Connect platforms, or any Stripe API integration') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Stripe', 'payment processing', 'checkout flows', 'subscriptions', 'webhooks', 'Connect platforms', 'Stripe API'. These cover common variations of how users would describe payment integration needs. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Stripe' as a clear differentiator. The specific mention of Stripe-specific concepts (Connect platforms, Stripe API) makes it unlikely to conflict with generic payment or coding skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides valuable guidance on Stripe API preferences and migration paths, with good external documentation references. However, it lacks executable code examples, clear workflow sequencing, and proper structural organization. The content reads more like a policy document than an actionable integration guide.
Suggestions
Add section headers (e.g., '## Recommended APIs', '## Deprecated APIs to Avoid', '## Integration Workflow') to improve navigation and organization
Include at least one executable code example showing a basic CheckoutSession creation with the recommended approach
Add a numbered workflow for typical integration steps (e.g., 1. Set up test mode, 2. Implement checkout, 3. Configure webhooks, 4. Verify with Go Live Checklist)
Convert the paragraph-based constraints into a scannable format like bullet points or a decision table
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient and avoids explaining basic concepts, but includes some redundant phrasing and could be tightened. Phrases like 'You should always default to' and 'If a user wants to' add unnecessary words. | 2 / 3 |
Actionability | Provides clear guidance on which APIs to use and avoid, with good links to documentation. However, lacks concrete code examples - no executable snippets showing how to implement CheckoutSessions, PaymentIntents, or webhooks. | 2 / 3 |
Workflow Clarity | No clear sequencing of integration steps. Content reads as a list of preferences and constraints rather than a workflow. Missing validation checkpoints for payment integration (e.g., test mode verification, webhook setup confirmation). | 1 / 3 |
Progressive Disclosure | Good use of external documentation links for detailed information, keeping the skill focused on guidance. However, the content lacks clear section headers and organization - it's a wall of paragraphs without visual hierarchy or navigation structure. | 2 / 3 |
Total | 7 / 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.
- Repository
- anthropics/claude-plugins-official
- Commit
158ef95
- 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.