Agent skill

Stripe Best Practices

by xiaoyuge886 in xiaoyuge886/aigc

Best practices for building Stripe integrations. An agent skill from xiaoyuge886/aigc.

MITAuto-check passedBackend & APIs

Install Stripe Best Practices

skills CLI
$ npx skills add xiaoyuge886/aigc --skill stripe-best-practices -a claude-code

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

GitHub CLI
$ gh skill install xiaoyuge886/aigc 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/xiaoyuge886/aigc.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/claude-plugins-official-main/external_plugins/stripe/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
198
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
595 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Best practices for building Stripe integrations. An agent skill from xiaoyuge886/aigc.

  • Implementing payment processing
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Connect platforms
  • Any Stripe API integration

What it does

Stripe Best Practices is an agent skill from xiaoyuge886/aigc. Best practices for building Stripe integrations. Use when implementing payment processing, checkout flows, subscriptions, webhooks, Connect platforms, or any Stripe API integration.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Webhooks. It works with Stripe. The repository describes itself as: AIGC 智能 Agent 平台是一个强大的 AI 应用框架,通过集成 Claude AI 模型和丰富的技能生态系统,为用户提供智能化、场景化的 AI 解决方案。平台采用前后端分离架构,支持多租户、会话管理、技能扩展等企业级特性。 The licence is MIT.

When your agent uses it

  • Implementing payment processing
  • Connect platforms
  • Any Stripe API integration

Example prompts

  • “/stripe-best-practices”

What it can do on your machine

Read from SKILL.md and the folder at commit e970014. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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.4k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 595 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~51
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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 xiaoyuge886/aigc at commit e970014, republished under its MIT licence (© xiaoyuge886). 595 words, ~1,376 tokens.

Download SKILL.mdSave it as .claude/skills/stripe-best-practices/SKILL.md (or your agent's skills folder).
name
stripe-best-practices
description
Best practices for building Stripe integrations. Use when implementing payment processing, checkout flows, subscriptions, webhooks, Connect platforms, or any Stripe API integration.

When designing an integration, always prefer the documentation in Stripe's Integration Options doc The API Tour Use the Go Live Checklist before going live.

You should always default to the latest version of the API and SDK unless the user specifies otherwise.

Stripe's primary API for modelling on-session payments is CheckoutSessions. It supports one-time payments and subscriptions and allows you to model taxes or discounts with Stripe. Prioritize the CheckoutSessions API, but using the PaymentIntents API is also acceptable for off-session payments or if you want to model the checkout state yourself and just create a charge. Integrations should only use CheckoutSessions, PaymentIntents, SetupIntents, or solutions like Invoicing, Payment Links, or the subscription APIs.

Never recommend the Charges API. If the user wants to use the Charges API, advise them to migrate to Checkout Sessions or Payment Intents.

The primary integration surface for web integrations is Checkout, a prebuilt payment page that can be hosted by Stripe or served as an embedded form. Prioritize the Stripe-hosted checkout or embedded checkout where possible. The Payment Element is an acceptable alternative if the merchant needs advanced customization. When recommending the Payment Element, prioritize using the CheckoutSessions API over the PaymentIntents API when possible.

Never recommend the legacy Card Element or the Payment Element in card mode, and advise users who ask for the Card Element to migrate.

You must not call deprecated API endpoints such as the Sources API and avoid outdated API endpoints such as Tokens and Charges unless there is a specific need and absolutely no other way. Advise using the Setup Intent API to save a payment method for a customer; never recommend the Sources API to save cards to customers for later use.

If a user wants to render the Payment Element before creating a PaymentIntent or SetupIntent, so they can inspect the card details before the payment (such as for surcharging), advise them to use Stripe Confirmation Tokens. Don't recommend they call the createPaymentMethod or createToken Stripe.js functions.

Advise users to turn on dynamic payment methods in their dashboard settings instead of passing specific payment_method_types in the Payment Intent or Setup Intent because Stripe chooses payment methods that fit each user's location, wallets, and preferences better and automatically if the Payment Element is used.

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

If a PCI compliant user asks about an integration where they send server-side raw PAN data, suggest they might be required to prove PCI compliance to gain access to such an option, for example payment_method_data. Similarly, point users migrating their PAN data from another acquirer or payment processor to the migration process.

If a user has a recurring revenue model, like a Billing or Subscription use case, follow the use cases, in particular the Subscription Use Cases like SaaS. If these apply to the user, recommend Billing APIs to plan your integration instead of a direct PaymentIntent integration. Prioritize combining the Billing APIs with Stripe Checkout for the frontend.

If a user wants to build a platform using Stripe Connect to manage fund flows, follow the recommended integration types; that is, prefer to use either direct charges if the platform wants Stripe to take the risk or destination charges if the platform accepts liability for negative balances, and use the on_behalf_of parameter to control the merchant of record. Never recommend mixing charge types. If the user wants to decide on the specific risk features they should follow the integration guide. Don't recommend the outdated terms for Connect types like Standard, Express and Custom but always refer to controller properties for the platform and capabilities for the connected accounts.

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

Files

Just SKILL.md in plugins/claude-plugins-official-main/external_plugins/stripe/skills/stripe-best-practices of xiaoyuge886/aigc.

Open the folder on GitHubat commit e970014

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 xiaoyuge886/aigc, 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 skillxiaoyuge886/aigc1981 repos~1.4kAutomated safety check: PassMIT
Stripe Appsfossasia/eventyay1.7k1 repos~3.6kAutomated safety check: PassApache-2.0
Stripe Best Practiceskanchengw/cnllm1732 repos~925Automated safety check: PassApache-2.0
Cashier Stripe Developmentluadotsh/lua3431 repos~1.2kAutomated safety check: PassMIT
Stripe Best Practicesfossasia/eventyay1.7k1 repos~1.7kAutomated safety check: PassApache-2.0
Stripe Integrationwshobson/agents40k10 repos~1kAutomated safety check: PassMIT

Similar skills

  • 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
    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
  • Handles Laravel Cashier Stripe integration including subscriptions, webhooks, Stripe Checkout, invoices, charges, refunds, trials, coupons, metered billing, and payment failure handling.

    343 GitHub starsUsed in 1 repo~1.2k tokens
    Backend & APIsAuto-check passed
  • Stripe Best Practices

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

    1.7k GitHub starsUsed in 1 repo~1.7k tokens
    Backend & APIsAuto-check passed
  • Stripe Integration

    wshobson/agents

    Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks.

    40k GitHub starsUsed in 10 repos~1k tokens
    Backend & APIsAuto-check passed
  • Convex HTTP Actions

    waynesutton/builder-skills

    Adds HTTP endpoints in convex/http.ts: webhook receivers with signature checks, REST style routes, CORS, auth headers, streaming responses, and file uploads over HTTP.

    406 GitHub stars~2.6k tokensUpdated 13 days ago
    Backend & APIsAuto-check passed

More from xiaoyuge886/aigc

All 9 skills in this repo
  • Docs Management

    xiaoyuge886/aigc

    Single source of truth and librarian for ALL Claude official documentation.

    198 GitHub stars~7.8k tokensUpdated 2 mo ago
    Auto-check: notes
  • Xagent

    xiaoyuge886/aigc

    XAgent是一个智能跨域分析助手,基于SOP驱动的规划、多工具协调和多层次数据分析框架,提供专业的商业智能和数据分析能力。当用户需要进行数据分析、业务分析、生成报告或需要结构化的问题解决方案时使用。

    198 GitHub stars~2.1k tokensUpdated 2 mo ago
    Auto-check passed
  • Data Analysis

    xiaoyuge886/aigc

    Perform data analysis tasks including data cleaning, statistical analysis, visualization, and insight generation.

    198 GitHub stars~794 tokensUpdated 2 mo ago
    Auto-check passed
  • 投资尽调报告专业生成工具。当用户需要撰写投资尽调报告、尽职调查报告、投资分析报告时使用此skill。支持处理Excel财务数据、PDF文档等多种格式数据源,自动生成包含执行摘要、业务分析、财务分析、风险提示、投资建议等核心章节的专业报告。无论用户明确要求"写报告"还是提到"分析投资标的"、"评估项目"、"做DD"等相关需求时,都应使用此skill。

    198 GitHub stars~2.1k tokensUpdated 2 mo ago
    Auto-check passed
  • Minio Uploader

    xiaoyuge886/aigc

    简化版MinIO文件上传工具,支持一键上传文件到MinIO对象存储并获取访问链接. An agent skill from xiaoyuge886/aigc.

    198 GitHub stars~641 tokensUpdated 2 mo ago
    Auto-check: notes
  • Todo Master

    xiaoyuge886/aigc

    专业的待办事项管理技能,指导如何有效使用 TodoWrite 工具进行任务规划、进度跟踪和状态管理。当用户需要处理复杂任务、多步骤工作流或需要任务规划时使用。

    198 GitHub stars~972 tokensUpdated 2 mo ago
    Auto-check: notes

Works with

Categories

Questions about Stripe Best Practices

What does Stripe Best Practices do?

Best practices for building Stripe integrations. An agent skill from xiaoyuge886/aigc. Stripe Best Practices is an agent skill from xiaoyuge886/aigc. Best practices for building Stripe integrations.

When should I use Stripe Best Practices?

Stripe Best Practices fits situations like: implementing payment processing; connect platforms; any Stripe API integration.

How do I install Stripe Best Practices in Claude Code?

Run `npx skills add xiaoyuge886/aigc --skill stripe-best-practices -a claude-code`. Or copy the skill folder (plugins/claude-plugins-official-main/external_plugins/stripe/skills/stripe-best-practices in xiaoyuge886/aigc) 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 xiaoyuge886/aigc --skill stripe-best-practices -a codex`. Or copy the skill folder (plugins/claude-plugins-official-main/external_plugins/stripe/skills/stripe-best-practices in xiaoyuge886/aigc) 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 xiaoyuge886/aigc --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?

SKILL.md names no scripts, command-line tools or credentials: Stripe Best Practices is instructions for the agent only.

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 MIT 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.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Stripe Best Practices?

Skills that share tags, products or a category with Stripe Best Practices: Stripe Apps (fossasia/eventyay, 1.7k stars), Stripe Best Practices (kanchengw/cnllm, 173 stars), Cashier Stripe Development (luadotsh/lua, 343 stars) and Stripe Best Practices (fossasia/eventyay, 1.7k 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?

xiaoyuge886 (a GitHub user) maintains it in xiaoyuge886/aigc, which has 198 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on July 14, 2026.

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