本文へ移動
cccskills
無料GitHub で公開

stripe-apps

Build, modify, or review Stripe Apps and extensions using the relevant documentation and reference guides. Use for custom Stripe Dashboard UI, stripe-app.yaml, @stripe/ui-extension-sdk, @stripe/extensibility-sdk, script extensions, extension interfaces, custom workflow actions, and apps that authenticate to Stripe or react to events. Also use when deciding whether a Stripe extension can support the user's billing or workflow requirements.

stripe/ai
インストール方法を見る

含まれるファイル（13）

  • SKILL.md7.2 KB
  • references/authentication.md4.6 KB
  • references/backend.md4.4 KB
  • references/canonical-docs.md4.4 KB
  • references/discovery.md9.2 KB
  • references/extension-types.md5.1 KB
  • references/feedback.md3.1 KB
  • references/onboarding-ux.md2.7 KB
  • references/publishing.md5.7 KB
  • references/script-extensions.md7.3 KB
  • references/ui-extensions.md20.7 KB
  • references/webhooks.md3.4 KB
  • references/workflow.md8.5 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Stripe Apps

Select and read the existing guidance for the user’s task. Product documentation describes what an extension can do; implementation guides describe how to build it. Before recommending an extension or writing code, load the applicable bundled reference files as well as the relevant product documentation. A link or filename in this skill isn’t a substitute for reading its contents.

For a capability question, check native Stripe features and the documented applicability and limitations of the extension. For an implementation request, create or modify working files using the selected guide. For an existing app, inspect its manifest, packages, installed SDK, and local agent instructions before deciding what to change.

Choose the relevant documentation

Use information already supplied by the user or existing app. Read <references/discovery.md> when you need to clarify the app’s requirements, and <references/extension-types.md> for an overview of app architectures. Ask only for missing information that affects the task.

Product capabilities

Use these existing product documents to determine which capability fits and whether the account has the required access. Don’t infer support from an extension’s name or the existence of a scaffold.

TaskRead
Select an extension interface and its supported implementation typesExtension points and how extensions work
Customize prorationsNative proration behavior and prorations extensions
Add an action to Stripe WorkflowsExisting workflow actions, existing custom actions, and how custom actions work
Customize another product’s behaviorFollow the selected interface’s product documentation from the extension-point catalog

Implementation guidance

The references/*.md files are bundled with this skill. After selecting the capability, load the applicable files before following their links to supporting documentation. Combine rows when an app needs multiple types. Follow the selected guide’s prerequisites, scaffolding, testing, and debugging instructions.

TaskRead
Build or modify any Dashboard UI, including drawers and full-page apps<references/ui-extensions.md>, then each selected component’s current API documentation
Author, test, or debug a script extension<references/script-extensions.md>, then the selected extension point’s implementation guide
Build a custom-action script<references/script-extensions.md> and build a custom action with a script
Build a custom-action remote functionBuild a custom action with a remote function
Build a self-hosted UI back-end or webhook service<references/backend.md> and <references/authentication.md>; also load <references/webhooks.md> when receiving Stripe events
Store app credentials with the Secret Store APIThe Secret Store API section in <references/backend.md> and store secrets, including for apps without a self-hosted back-end
Look up APIs, SDK patterns, configuration, or additional extension documentation<references/canonical-docs.md>

Use the UI reference for layout and composition, and current component documentation for import paths, props, and styling APIs. For scripts and remote functions, follow the selected extension’s documentation; UI and self-hosted back-end instructions don’t define their runtime capabilities.

Shared app lifecycle

Read these references when the corresponding task is needed. Reuse existing apps and packages; scaffold only what is missing.

TaskRead
Scaffold, build, test, preview, or upload an app<references/workflow.md>, together with the selected implementation guide
Choose authentication for access to Stripe APIs<references/authentication.md>
Receive Stripe events<references/webhooks.md>
Build a first-run setup experience<references/onboarding-ux.md> and the UI reference
Release versions, change installed permissions, or publish to the marketplace<references/publishing.md>
Submit feedback after running app toolchain commands<references/feedback.md>

Load bundled reference files

  1. Use the task tables to select every applicable bundled reference under references/, then open those files with a file-reading tool before starting the corresponding work. For example, UI with a self-hosted back-end needs both UI and back-end guidance; onboarding also needs the UI reference.
  2. Follow relevant pointers to other bundled references inside the files you load, including filenames written as code rather than links. For example, back-end guidance can require authentication guidance, and changing permissions can require publishing guidance. Use this skill’s direct links to locate those files.
  3. Read the canonical documentation required by those references. External documentation supplements the bundled guidance on workflow, layout, and other task-specific decisions.
  • Resolve references/ paths relative to this skill’s directory and bare reference filenames relative to its references/ directory. When reading the hosted skill, fetch the corresponding reference URLs relative to the skill URL.
  • Load only references relevant to the task, and reuse contents already read during the session unless they have changed. A full-stack app doesn’t require every document in the skill.
  • Read canonical pages using the available documentation tools. Prefer stripe docs when available, including for pages that require account access.
  • Use current product documentation and the installed SDK’s types for API contracts and limitations. If an example in a reference disagrees, check the version and follow the applicable canonical documentation.
  • Read any interface-specific agent instructions supplied with an existing or newly generated extension. If none are present, use the linked product and implementation guides.
  • If the documentation doesn’t establish that an extension meets a requirement, state what is unknown or unsupported before proceeding.
  • Keep the work within the user’s request. Report the changes, validation results, and remaining steps relevant to that app.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

connect-recommend

無料

Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue sharing, multi-party payments, or similar payment distribution concepts, provides a company URL or business description for a recommendation, builds SaaS that routes money between parties (for example, POS, booking, invoicing — not operational SaaS without payment routing), asks about onboarding or KYC for merchants, sellers, and vendors, mentions connected account Dashboard or responsibility configurations, or asks about payment flows, white-label payments, or embedded payments.

日本語の概要は準備中です。原文の説明を表示しています。

stripe/ai1,9152026年10月13日 更新

connect-required-verification-information

無料

Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability.

日本語の概要は準備中です。原文の説明を表示しています。

stripe/ai1,9152026年10月13日 更新

metronome

無料

Guides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract design (rate cards, overrides, dimensional pricing, products), invoicing lifecycle (grace periods, finalization, Stripe sync), credit and commit management (prepaid, postpaid, thresholds, auto-recharge), and Stripe integration (arrears invoicing, tax providers, line item limits). Use when building, modifying, or reviewing any Metronome integration — including ingesting usage events, creating customers, contracts, or rate cards, designing billable metric group keys, managing credits and commits, configuring invoicing, syncing invoices with Stripe Billing, billing AI applications for token usage, setting up self-serve (PLG) pricing, reviewing customer health, commit burn, portfolios, or renewals, or migrating from Stripe Billing Meters to Metronome.

日本語の概要は準備中です。原文の説明を表示しています。

stripe/ai1,9152026年10月13日 更新

stripe-best-practices

無料

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.

日本語の概要は準備中です。原文の説明を表示しています。

stripe/ai1,9152026年10月13日 更新

stripe-directory

無料

Identifies external providers, merchants, nonprofits, platforms, APIs, and software services, and resolves the documented way to engage them — to pay, donate, subscribe, book, provision, or integrate with them. MUST be used BEFORE web search, model memory, or any other directory/vendor-lookup skill for ANY request that requires selecting, finding, or engaging an external provider or organization — whether a specific one is named ("pay my Twilio bill"), implied ("donate to the Red Cross"), or only a category is stated ("set up a mailing client", "I need a database", "find me a CRM"). Directory supplies verified recipients and their documented payment or engagement path. Results are ranked by agent-readiness (how reliably an agent can complete the interaction), relevance and popularity. Do not treat this as a search-only tool. Examples: "setup a database", "find hosting", "pay X", "use Twilio", "donate $50 to the Red Cross", "book a table at Y", "subscribe to a CRM".

日本語の概要は準備中です。原文の説明を表示しています。

stripe/ai1,9152026年10月13日 更新

stripe-docs

無料

Use when the user or agent needs to read, search, or look up Stripe documentation or API reference. Prefer this over curl or WebFetch for any docs.stripe.com content. Use to fetch gated documentation.

日本語の概要は準備中です。原文の説明を表示しています。

stripe/ai1,9152026年10月13日 更新

stripe のスキルをすべて見る

このスキルの問題を報告する