CtrlK
CommunityDocumentationLog inGet started
Tessl Logo

stripe-best-practices

tessl i github:anthropics/claude-plugins-official --skill stripe-best-practices
github.com/anthropics/claude-plugins-official

Best practices for building Stripe integrations. Use when implementing payment processing, checkout flows, subscriptions, webhooks, Connect platforms, or any Stripe API integration.

Review Score

64%

Validation Score

12/16

Implementation Score

38%

Activation Score

90%

SKILL.md
Review
Evals

Generated

Validation

Total

12/16

Score

Passed
CriteriaScore

metadata_version

'metadata' field is not a dictionary

license_field

'license' field is missing

body_output_format

No obvious output/return/format terms detected; consider specifying expected outputs

body_steps

No step-by-step structure detected (no ordered list); consider adding a simple workflow

Implementation

Suggestions 4

Score

38%

Overall Assessment

This skill provides valuable guidance on Stripe API preferences and deprecated patterns to avoid, with good documentation references. However, it lacks executable code examples, clear workflow structure, and organized sections. The content reads more like a policy document than actionable integration guidance.

Suggestions

  • Add concrete code examples for common patterns (e.g., creating a CheckoutSession, handling webhooks, setting up subscriptions)
  • Restructure content with clear headers: '## Quick Start', '## API Selection Guide', '## Connect Integrations', '## Billing/Subscriptions'
  • Add a workflow section with numbered steps for a typical integration: 1. Choose integration type → 2. Set up test mode → 3. Implement checkout → 4. Add webhooks → 5. Go-live checklist
  • Include validation checkpoints such as 'Verify webhook signatures before processing events' and 'Test in Stripe test mode before going live'
DimensionScoreReasoning

Conciseness

2/3

The content is reasonably efficient and avoids explaining basic concepts, but includes some redundant phrasing and could be tightened. Phrases like 'always prefer' and 'You should always default' add minor verbosity.

Actionability

2/3

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.

Workflow Clarity

1/3

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).

Progressive Disclosure

2/3

Good use of external documentation links for deeper dives, but the skill itself is a wall of text without clear section headers or organization. Content could benefit from structured sections (Quick Start, API Selection, Connect, Billing).

Activation

Suggestions 1

Score

90%

Overall Assessment

This is a strong skill description with excellent trigger terms and completeness. The explicit 'Use when...' clause covers the key scenarios well, and the Stripe-specific terminology makes it highly distinctive. The main weakness is that 'best practices' is somewhat vague compared to listing concrete actions like 'implement webhooks', 'configure checkout sessions', or 'handle subscription lifecycle events'.

Suggestions

  • Replace 'Best practices for building' with specific concrete actions like 'Implement and configure Stripe payment flows, handle webhooks, manage subscriptions'
DimensionScoreReasoning

Specificity

2/3

Names the domain (Stripe integrations) and lists several areas (payment processing, checkout flows, subscriptions, webhooks, Connect platforms) but describes them as 'best practices' rather than concrete actions like 'implement', 'configure', or 'debug'.

Completeness

3/3

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.

Trigger Term Quality

3/3

Excellent coverage of natural terms users would say: 'payment processing', 'checkout flows', 'subscriptions', 'webhooks', 'Connect platforms', 'Stripe API integration' - these are all terms developers naturally use when working with Stripe.

Distinctiveness Conflict Risk

3/3

Highly distinctive with 'Stripe' as a clear differentiator. The specific mention of Stripe-specific concepts like 'Connect platforms' and 'Stripe API' makes it unlikely to conflict with generic payment or API skills.