CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

95

1.42x
Quality

Does it follow best practices?

Impact

100%

1.42x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

A well-structured overview that routes each integration scenario to a real, one-level-deep reference and gives concrete commands and tool names. The only weakness is mild explanatory padding in the Critical rules rationale.

Suggestions

Trim the justification in the Critical rules section — state the rule ('Never include payment_method_types except for Terminal card_present') and link to dynamic payment methods, rather than explaining the conversion rationale inline.

Add a one-line pointer from the security row to the MCP planner or confirm the planner covers security, so the two guidance paths are visibly consistent.

DimensionReasoningScore

Conciseness

Mostly lean — a routing table and terse rules assuming Claude's competence — but the 'Critical rules' section pads the rationale ('which enables you to configure payment method settings from the Dashboard and dynamically display the most relevant eligible payment methods to each customer to maximize conversion') with explanation that could be trimmed.

2 / 3

Actionability

Provides concrete, executable guidance: install command 'npm i -g @stripe/cli', 'stripe sandbox create', specific API path '/v2/core/accounts', the MCP URL and tool name 'stripe_implementation_planner', and exact doc links.

3 / 3

Workflow Clarity

Clear sequence — install the MCP server, call stripe_implementation_planner, else fall back to the routing table, then read the relevant reference file before answering — with an unambiguous decision structure and no destructive/batch operations requiring validation checkpoints.

3 / 3

Progressive Disclosure

The routing table cleanly maps each task to a single one-level-deep reference file (payments.md, connect.md, billing.md, tax.md, treasury.md, security.md), all of which exist, are clearly signaled, and contain no nested internal references.

3 / 3

Total

11

/

12

Passed

Description

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.

A strong, specific description that names concrete capabilities, includes natural trigger terms, and explicitly covers both what and when in third person. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'API selection (Checkout Sessions vs PaymentIntents)', 'Connect platform setup (Accounts v2, controller properties)', 'migrating from deprecated Stripe APIs', and 'security best practices (API key management, restricted keys, webhooks, OAuth)'.

3 / 3

Completeness

Explicitly states both what it does (guides integration decisions across API selection, Connect, billing, Treasury, security) and when to use it via the 'Use when building, modifying, or reviewing any Stripe integration — including...' clause.

3 / 3

Trigger Term Quality

Covers natural phrasings users would say — 'accepting payments', 'building marketplaces', 'integrating Stripe', 'processing payments', 'setting up subscriptions', 'creating connected accounts' — alongside the core 'Stripe integration'.

3 / 3

Distinctiveness Conflict Risk

Tightly scoped to Stripe-specific surfaces with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
stripe/ai
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.