본문으로 건너뛰기
cccskills
무료GitHub에 공개

stripe-pay

Helps users send funds to another Stripe business, transfer money to a Stripe Profile handle or network ID, or ask whether an agent can pay a Stripe business. Use Stripe Directory to find or verify a recipient when the user doesn't provide an exact Stripe Profile handle or network ID.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

연동 도구Stripe
설치 방법 보기

포함된 파일(1)

  • SKILL.md4.3 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

stripe pay

Use stripe pay to send money from the authenticated Stripe business to another Stripe business identified by a Stripe Profile handle, for example @recipient.

The stripe pay command is for business-to-business money transfers. Both the sender and the receiving business must have a Stripe Profile. In addition:

If the user needs details about financial accounts, read Money Management. The command resolves the recipient’s payout configuration, which can route the payout to an attached financial account or linked bank account, and reports the fee and delivery timing before confirmation. Don’t assume that a transfer is free or instant.

Safety Rules

  1. Don’t send money unless the user explicitly asks you to make the transfer.
  2. Before running a command that can send money, show the exact stripe pay ... command you plan to run and get confirmation.
  3. Use --agent or --json first so the user can review the transfer details.
  4. Don’t pass -y or --yes until after the user confirms the reviewed transfer.
  5. Don’t guess at the user’s intent. Don’t guess at the username, financial account ID, amount, currency, internal note, memo, or any other detail. Always confirm with the user.
  6. Don’t print full API keys back to the user.

Choose the workflow

Read the documentation to accomplish your goal. You must read the relevant page before taking action:

GoalDocumentation
Find or verify a recipient when the user doesn’t provide an exact Stripe Profile handle or network IDUse Stripe Directory with AI agents
Review, send, handle approval, resume, or dry-run a transferstripe pay CLI reference
Create or manage a Stripe Profile, including a recipient’s transfer destinationStripe Profile
Set up or understand an eligible financial accountMoney Management

Handle setup errors

Don’t continue the transfer when stripe pay reports missing setup. Explain what’s missing and give the user the corresponding next step. Before explaining how to resolve the error, read the documentation for the missing requirement in the workflow table:

  • If the sender is missing a Stripe Profile, tell the user to create one.
  • If the sender is missing an eligible financial account, tell the user to set up Global Payouts with an eligible financial account.
  • If the sender is missing both requirements, tell the user to complete both setup steps before trying the transfer again.
  • If the recipient doesn’t have an eligible transfer destination linked to their Stripe Profile, tell the user that the recipient must complete that setup before the transfer can proceed. Don’t retry the transfer until the recipient’s setup is corrected.
  • If the recipient is missing or invalid, read and follow the Stripe Directory agent workflow. If the user can provide the recipient’s exact Stripe Profile handle or network ID, ask them for it.

For sender setup, direct the user to the relevant Dashboard page:

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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/ai2천2026년 10월 19일 업데이트

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/ai2천2026년 10월 19일 업데이트

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/ai2천2026년 10월 19일 업데이트

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/ai2천2026년 10월 19일 업데이트

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/ai2천2026년 10월 19일 업데이트

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/ai2천2026년 10월 19일 업데이트

stripe의 스킬 모두 보기

이 스킬의 문제 신고