CtrlK
BlogDocsLog inGet started
Tessl Logo

stripe-best-practices

Guides Stripe integration decisions across API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (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, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling.

88

1.67x
Quality

87%

Does it follow best practices?

Impact

87%

1.67x

Average score across 3 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

A well-organized, token-efficient overview that routes Claude to detailed reference files with clear navigation and concrete critical rules. It could add an explicit validate→fix→retry feedback loop and a bit more copy-paste code to reach the top level.

Suggestions

Add an explicit validate→fix→retry feedback loop for destructive or batch operations (e.g., enabling automatic_tax or creating sessions) to lift workflow_clarity from 4 to 5.

Include one or two copy-paste-ready code snippets for the most common integrations (e.g., a minimal Checkout Session create) to improve actionability.

Trim the explanatory prose around dynamic payment methods in the payment_method_types rule to a single actionable sentence.

DimensionReasoningScore

Conciseness

Mostly lean — routing table, version table, and terse critical rules assume Claude's competence; the payment_method_types rule over-explains dynamic payment methods slightly, but it carries actionable guidance so it earns its place. Fits above the midpoint but not a flawless 5.

4 / 5

Actionability

Provides concrete commands (stripe sandbox create, stripe whoami --format json, integration_identifier) and a prescriptive routing table, but offers little copy-paste code; guidance is mostly executable with minor gaps for the common cases.

4 / 5

Workflow Clarity

Clear sequence: read the relevant reference before answering, then apply critical rules with an explicit validation checkpoint (confirm active registration before enabling automatic_tax). It lacks a full validate→fix→retry feedback loop, so it sits just below 5.

4 / 5

Progressive Disclosure

Body is a concise overview with a routing table linking to six one-level-deep, well-signaled reference files (payments, connect, billing, tax, treasury, security), all of which exist in the bundle; navigation is easy and references are not nested.

5 / 5

Total

17

/

20

Passed

Description

96%Weight 40%Scale 1-5

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, third-person description that explicitly covers both what the skill does and when to use it, with rich natural trigger terms. It is comprehensive across the Stripe domain with only minor breadth-related overlap risk.

DimensionReasoningScore

Specificity

Lists many concrete actions across domains — API selection (Checkout Sessions vs PaymentIntents), Connect Accounts v2, billing/subscriptions, Stripe Tax + Registrations, Treasury, migration, and security — giving comprehensive coverage rather than a single vague capability.

5 / 5

Completeness

Explicitly states both what the skill does (first sentence enumerates capabilities) and when to use it via a clear 'Use when building, modifying, or reviewing any Stripe integration, including...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrases abound: 'accepting payments', 'building marketplaces', 'subscriptions', 'sales tax, VAT, or GST', 'connected accounts', 'secure key handling', covering synonyms and variants a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Clearly Stripe-specific with distinct triggers and minimal conflict risk, but the breadth (payments, billing, tax, Treasury, security) means slight overlap with possible narrower single-domain skills; fits between 4 and 5, leaning distinct.

4 / 5

Total

19

/

20

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.