New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Stripe Best Practices

by fossasia in fossasia/eventyay

Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents)…

Apache-2.0Auto-check passedBackend & APIs

Install Stripe Best Practices

skills CLI
$ npx skills add fossasia/eventyay --skill stripe-best-practices -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install fossasia/eventyay stripe-best-practices --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/fossasia/eventyay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/stripe-best-practices .claude/skills/stripe-best-practices && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
stripe-best-practices
GitHub stars
1.7k
Used in
1 other repo
Token cost
~1.7k tokens
SKILL.md length
611 words
Files
7 (incl. references)
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents)…

  • Reviewing any Stripe integration
  • SKILL.md covers Integration routing, Critical rules and Key documentation
  • Calls stripe and npm
  • Including choosing a development environment

What it does

Stripe Best Practices is an agent skill from fossasia/eventyay. Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatictax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, API key…

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/billing.md`, `references/connect.md` and `references/payments.md`).

It sits in Backend & APIs, covering Tax preparation, Webhooks and Cryptography. It works with Stripe. The repository describes itself as: Open Source Event Management, Ticketing and Checkins, Talks and Schedules, Video and Interpretations, Badges, Exhibitions and more https://eventyay.com. The licence is Apache-2.0.

When your agent uses it

  • Reviewing any Stripe integration
  • Including choosing a development environment
  • Accepting payments
  • Building marketplaces

Example prompts

  • “Use the stripe-best-practices skill to guide Stripe integration decisions across development and test environment planning (separate sandboxes vs…”
  • “/stripe-best-practices”

Requirements

  • Python 3
  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit 286485c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • stripe
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.stripe.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Stripe Best Practices loads about 1.7k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 229 tokens; SKILL.md has 611 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~229
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~17k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from fossasia/eventyay at commit 286485c, republished under its Apache-2.0 licence (© fossasia). 611 words, ~1,679 tokens.

Download SKILL.mdSave it as .claude/skills/stripe-best-practices/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
stripe-best-practices
description
Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), 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, API key permissions, webhooks, OAuth). Use when planning, building, modifying, testing, or reviewing any Stripe integration, including choosing a development environment, 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.

Latest Stripe API version: 2026-08-26.dahlia. Always use the latest API version and SDK unless the user specifies otherwise.

Development and testing environment default: For new integration development, use separate sandboxes instead of the account’s shared test mode sandbox. Sandboxes isolate settings and test data from live mode. Use separate sandboxes for local development and CI. When stronger isolation is useful, dedicate sandboxes to development teams or testing scenarios. Use the shared test mode sandbox only for an existing integration that depends on it or when a required feature doesn’t support general sandboxes.

Latest SDK versions:

LanguageLatest version
Ruby19.6.0
Python15.6.0
Node.js22.6.0
PHP21.3.0
Java33.4.0
Go86.4.0
.NET52.4.0

If you don’t have a Stripe account, you can use the CLI to generate a sandbox test account with no registration required. Install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create, which creates test API keys for you. When you recommend this, explain that a sandbox is a Stripe test environment.

If stripe sandbox create is used, don’t use MCP.

If you try to use MCP after running sandbox creation, first make sure stripe sandbox claim is run. Use stripe whoami --format json for CLI auth checks; do not run stripe config --list.

API key default: Always recommend a restricted API key (RAK) (rk_ prefix) over a secret key (sk_ prefix).

Integration routing

Building…Recommended APIDetails
One-time paymentsCheckout Sessionsreferences/payments.md
Custom payment form with embedded UICheckout Sessions + Payment Elementreferences/payments.md
Saving a payment method for laterSetup Intentsreferences/payments.md
Connect platform or marketplaceAccounts v2 (/v2/core/accounts)references/connect.md
Usage-based billing (new integration)Metronomereferences/billing.md
Subscriptions or recurring billingBilling APIs + Checkout Sessionsreferences/billing.md
Sales tax, VAT, or GST complianceStripe Tax + Registrations APIreferences/tax.md
Embedded financial accounts / bankingv2 Financial Accountsreferences/treasury.md
Security (key management, RAKs, webhooks, OAuth, 2FA, Connect liability)See security referencereferences/security.md

Read the relevant reference file before answering any integration question or writing code.

Show full SKILL.md (283 more words)Show less

Critical rules

  • Before enabling automatic_tax: { enabled: true } (or calculating tax for a custom PaymentIntent), read the tax reference and confirm the user has an active registration. Without one, Stripe calculates and collects no tax while the user believes tax is on (the most common Stripe Tax mistake).

  • Never include payment_method_types in any Stripe API call, with one exception: Terminal (in-person payments) integrations must pass payment_method_types: ['card_present'] on the PaymentIntent. For all other integrations, omit this parameter entirely to enable dynamic payment methods, 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. To customize which payment methods you accept, use payment_method_configurations or excluded_payment_method_types instead of payment_method_types.

  • When a PaymentIntent or SetupIntent integration requires an explicit allowlist, use allowed_payment_method_types instead of payment_method_types.

  • Never present webhooks as optional. We recommend webhooks for every payment integration and they’re required for subscriptions and asynchronous payment methods. Fulfillment belongs in a handler for both checkout.session.completed and checkout.session.async_payment_succeeded (gated on payment_status), not the success page. See references/payments.md.

  • On API version 2026-03-25.dahlia or later, pass the parameter integration_identifier to checkout.sessions.create to tag sessions with a custom label for tracking and comparing checkout flows in the Dashboard. The label should include a suffix of 8 random letters.

  • Always instantiate a StripeClient and call methods on that instance. Do not use the deprecated global/module-level API key pattern (stripe.api_key = …, Stripe.setApiKey, stripe.Key = …, StripeConfiguration.ApiKey = …). The global pattern is deprecated in all current SDKs.

Key documentation

When the user’s request does not clearly fit a single domain above, consult:

© fossasia, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (references) in .agents/skills/stripe-best-practices of fossasia/eventyay.

  • SKILL.md
  • references/billing.md
  • references/connect.md
  • references/payments.md
  • references/security.md
  • references/tax.md
  • references/treasury.md

Open the folder on GitHubat commit 286485c

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in fossasia/eventyay, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Stripe Best Practices next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Stripe Best Practices compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Stripe Best Practices this skillfossasia/eventyay1.7k1 repos~1.7kAutomated safety check: PassApache-2.0
Stripe Best PracticesAsymmetric-al/core381—~1.3kAutomated safety check: PassAGPL-3.0
Stripe Best Practiceskanchengw/cnllm1732 repos~925Automated safety check: PassApache-2.0
cmux Billing Runbookmanaflow-ai/cmux28k—~2.8kAutomated safety check: PassCustom licence
Stripe Patternsbybren-llc/safe-agentic-workflow423—~1.2kAutomated safety check: PassMIT
Stripe Integration Expertalirezarezvani/claude-skills28k1 repos~3.7kAutomated safety check: PassMIT

Similar skills

  • Stripe Best Practices

    Asymmetric-al/core

    Guides Stripe integration decisions across API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and…

    381 GitHub stars~1.3k tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • Stripe Best Practices

    kanchengw/cnllm

    Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…

    173 GitHub starsUsed in 2 repos~925 tokens
    Backend & APIsAuto-check passed

  • cmux Billing Runbook

    manaflow-ai/cmux

    Runbook for the cmux billing code: Stripe Checkout, customer portal, subscription changes, webhooks and how Pro plan entitlement is resolved from Stack metadata.

    28k GitHub stars~2.8k tokensUpdated today
    Backend & APIsAuto-check passed

  • Stripe Patterns

    bybren-llc/safe-agentic-workflow

    Stripe payment integration patterns for checkout flows, webhooks, and subscriptions.

    423 GitHub stars~1.2k tokensUpdated 2 mo ago
    Backend & APIsAuto-check passed

  • Stripe Integration Expert

    alirezarezvani/claude-skills

    Production-grade Stripe integrations: subscriptions with trials and proration, one-time payments, usage-based billing, checkout sessions, idempotent webhook handlers, customer portal, and invoicing.

    28k GitHub starsUsed in 1 repo~3.7k tokens
    Backend & APIsAuto-check passed

  • Payment Integration

    aiskillstore/marketplace

    Integrate Stripe, PayPal, and payment processors. An agent skill from aiskillstore/marketplace.

    433 GitHub starsUsed in 8 repos~916 tokens
    Backend & APIsAuto-check passed

More from fossasia/eventyay

All 21 skills in this repo

  • Stripe Projects

    fossasia/eventyay

    A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.

    1.7k GitHub starsUsed in 5 repos~2k tokens
    Auto-check: notes

  • Stripe Apps

    fossasia/eventyay

    A skill your agent uses when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g.

    1.7k GitHub starsUsed in 1 repo~3.6k tokens
    Auto-check passed

  • Connect Recommend

    fossasia/eventyay

    A skill your agent uses when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform…

    1.7k GitHub starsUsed in 1 repo~5.9k tokens
    Auto-check: warnings

  • Django Run Locally

    fossasia/eventyay

    Steps for initiating the Django development server without Docker

    1.7k GitHub stars~411 tokensUpdated today
    Auto-check passed

  • Docker Deployment

    fossasia/eventyay

    Docker Compose, container services, deployment. An agent skill from fossasia/eventyay.

    1.7k GitHub stars~574 tokensUpdated today
    Auto-check: notes

  • Repo Navigation

    fossasia/eventyay

    Repository layout and where to find code. An agent skill from fossasia/eventyay.

    1.7k GitHub stars~752 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Stripe Best Practices

What does Stripe Best Practices do?

Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents)…. Stripe Best Practices is an agent skill from fossasia/eventyay.

When should I use Stripe Best Practices?

Stripe Best Practices fits situations like: reviewing any Stripe integration; including choosing a development environment; accepting payments; building marketplaces.

How do I install Stripe Best Practices in Claude Code?

Run `npx skills add fossasia/eventyay --skill stripe-best-practices -a claude-code`. Or copy the skill folder (.agents/skills/stripe-best-practices in fossasia/eventyay) into .claude/skills/stripe-best-practices in your project. Claude Code loads it when a task matches its description.

How do I install Stripe Best Practices in Codex?

Run `npx skills add fossasia/eventyay --skill stripe-best-practices -a codex`. Or copy the skill folder (.agents/skills/stripe-best-practices in fossasia/eventyay) into .agents/skills/stripe-best-practices in your project. Codex loads it when a task matches its description.

Can I use Stripe Best Practices in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fossasia/eventyay --skill stripe-best-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stripe-best-practices, .gemini/skills/stripe-best-practices, .github/skills/stripe-best-practices and .opencode/skills/stripe-best-practices in your project.

What does Stripe Best Practices need to run?

Going by SKILL.md and its folder, Stripe Best Practices needs the command-line tools its instructions call (stripe and npm). Our summary lists: Python 3; Node.js.

Does Stripe Best Practices access the network?

SKILL.md names 1 domain. As links in the text: docs.stripe.com. This is read from the text; nothing was executed.

Is Stripe Best Practices safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Stripe Best Practices use?

Stripe Best Practices is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Stripe Best Practices use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.

What are the alternatives to Stripe Best Practices?

Skills that share tags, products or a category with Stripe Best Practices: Stripe Best Practices (Asymmetric-al/core, 381 stars), Stripe Best Practices (kanchengw/cnllm, 173 stars), cmux Billing Runbook (manaflow-ai/cmux, 28k stars) and Stripe Patterns (bybren-llc/safe-agentic-workflow, 423 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Stripe Best Practices?

fossasia (a GitHub organization) maintains it in fossasia/eventyay, which has 1,701 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 11, 2026.

Source: fossasia/eventyay on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.