💼 Stripe Automation
Stripeの顧客管理、請求、サブスクリプション、返金といった様々なタスクを自動化するためのSkillです。
📺 まず動画で見る(YouTube)
▶ 【自動化】AIガチ勢の最新活用術6選がこれ1本で丸分かり!【ClaudeCode・AIエージェント・AI経営・Skills・MCP】 ↗
※ jpskill.com 編集部が参考用に選んだ動画です。動画の内容と Skill の挙動は厳密には一致しないことがあります。
📜 元の英語説明(参考)
Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds. Always search tools first for current schemas.
🇯🇵 日本人クリエイター向け解説
Stripeの顧客管理、請求、サブスクリプション、返金といった様々なタスクを自動化するためのSkillです。
※ jpskill.com 編集部が日本のビジネス現場向けに補足した解説です。Skill本体の挙動とは独立した参考情報です。
⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。
🎯 このSkillでできること
下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。
📦 インストール方法 (3ステップ)
- 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
- 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
- 3. 展開してできたフォルダを、ホームフォルダの
.claude/skills/に置く- · macOS / Linux:
~/.claude/skills/ - · Windows:
%USERPROFILE%\.claude\skills\
- · macOS / Linux:
Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。
詳しい使い方ガイドを見る →- 最終更新
- 2026-05-17
- 取得日時
- 2026-05-17
- 同梱ファイル
- 1
💬 こう話しかけるだけ — サンプルプロンプト
- › Stripe Automation で、私のビジネスを分析して改善案を3つ提案して
- › Stripe Automation を使って、来週の会議用の資料を作って
- › Stripe Automation で、現状の課題を整理してアクションプランに落として
これをClaude Code に貼るだけで、このSkillが自動発動します。
📖 Claude が読む原文 SKILL.md(中身を展開)
この本文は AI(Claude)が読むための原文(英語または中国語)です。日本語訳は順次追加中。
Stripe Automation via Rube MCP
Automate Stripe payment operations through Composio's Stripe toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Stripe connection via
RUBE_MANAGE_CONNECTIONSwith toolkitstripe - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitstripe - If connection is not ACTIVE, follow the returned auth link to complete Stripe connection
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Manage Customers
When to use: User wants to create, update, search, or list Stripe customers
Tool sequence:
STRIPE_SEARCH_CUSTOMERS- Search customers by email/name [Optional]STRIPE_LIST_CUSTOMERS- List all customers [Optional]STRIPE_CREATE_CUSTOMER- Create a new customer [Optional]STRIPE_POST_CUSTOMERS_CUSTOMER- Update a customer [Optional]
Key parameters:
email: Customer emailname: Customer namedescription: Customer descriptionmetadata: Key-value metadata pairscustomer: Customer ID for updates (e.g., 'cus_xxx')
Pitfalls:
- Stripe allows duplicate customers with the same email; search first to avoid duplicates
- Customer IDs start with 'cus_'
2. Manage Charges and Payments
When to use: User wants to create charges, payment intents, or view charge history
Tool sequence:
STRIPE_LIST_CHARGES- List charges with filters [Optional]STRIPE_CREATE_PAYMENT_INTENT- Create a payment intent [Optional]STRIPE_CONFIRM_PAYMENT_INTENT- Confirm a payment intent [Optional]STRIPE_POST_CHARGES- Create a direct charge [Optional]STRIPE_CAPTURE_CHARGE- Capture an authorized charge [Optional]
Key parameters:
amount: Amount in smallest currency unit (e.g., cents for USD)currency: Three-letter ISO currency code (e.g., 'usd')customer: Customer IDpayment_method: Payment method IDdescription: Charge description
Pitfalls:
- Amounts are in smallest currency unit (100 = $1.00 for USD)
- Currency codes must be lowercase (e.g., 'usd' not 'USD')
- Payment intents are the recommended flow over direct charges
3. Manage Subscriptions
When to use: User wants to create, list, update, or cancel subscriptions
Tool sequence:
STRIPE_LIST_SUBSCRIPTIONS- List subscriptions [Optional]STRIPE_POST_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS- Create subscription [Optional]STRIPE_RETRIEVE_SUBSCRIPTION- Get subscription details [Optional]STRIPE_UPDATE_SUBSCRIPTION- Modify subscription [Optional]
Key parameters:
customer: Customer IDitems: Array of price items (price_id and quantity)subscription: Subscription ID for retrieval/update (e.g., 'sub_xxx')
Pitfalls:
- Subscriptions require a valid customer with a payment method
- Price IDs (not product IDs) are used for subscription items
- Cancellation can be immediate or at period end
4. Manage Invoices
When to use: User wants to create, list, or search invoices
Tool sequence:
STRIPE_LIST_INVOICES- List invoices [Optional]STRIPE_SEARCH_INVOICES- Search invoices [Optional]STRIPE_CREATE_INVOICE- Create an invoice [Optional]
Key parameters:
customer: Customer ID for invoicecollection_method: 'charge_automatically' or 'send_invoice'days_until_due: Days until invoice is due
Pitfalls:
- Invoices auto-finalize by default; use
auto_advance: falsefor draft invoices
5. Manage Products and Prices
When to use: User wants to list or search products and their pricing
Tool sequence:
STRIPE_LIST_PRODUCTS- List products [Optional]STRIPE_SEARCH_PRODUCTS- Search products [Optional]STRIPE_LIST_PRICES- List prices [Optional]STRIPE_GET_PRICES_SEARCH- Search prices [Optional]
Key parameters:
active: Filter by active/inactive statusquery: Search query for search endpoints
Pitfalls:
- Products and prices are separate objects; a product can have multiple prices
- Price IDs (e.g., 'price_xxx') are used for subscriptions and checkout
6. Handle Refunds
When to use: User wants to issue refunds on charges
Tool sequence:
STRIPE_LIST_REFUNDS- List refunds [Optional]STRIPE_POST_CHARGES_CHARGE_REFUNDS- Create a refund [Optional]STRIPE_CREATE_REFUND- Create refund via payment intent [Optional]
Key parameters:
charge: Charge ID for refundamount: Partial refund amount (omit for full refund)reason: Refund reason ('duplicate', 'fraudulent', 'requested_by_customer')
Pitfalls:
- Refunds can take 5-10 business days to appear on customer statements
- Amount is in smallest currency unit
Common Patterns
Amount Formatting
Stripe uses smallest currency unit:
- USD: $10.50 = 1050 cents
- EUR: 10.50 = 1050 cents
- JPY: 1000 = 1000 (no decimals)
Pagination
- Use
limitparameter (max 100) - Check
has_morein response - Pass
starting_afterwith last object ID for next page - Continue until
has_moreis false
Known Pitfalls
Amount Units:
- Always use smallest currency unit (cents for USD/EUR)
- Zero-decimal currencies (JPY, KRW) use the amount directly
ID Prefixes:
- Customers:
cus_, Charges:ch_, Subscriptions:sub_ - Invoices:
in_, Products:prod_, Prices:price_ - Payment Intents:
pi_, Refunds:re_
Quick Reference
| Task | Tool Slug | Key Params |
|---|---|---|
| Create customer | STRIPE_CREATE_CUSTOMER | email, name |
| Search customers | STRIPE_SEARCH_CUSTOMERS | query |
| Update customer | STRIPE_POST_CUSTOMERS_CUSTOMER | customer, fields |
| List charges | STRIPE_LIST_CHARGES | customer, limit |
| Create payment intent | STRIPE_CREATE_PAYMENT_INTENT | amount, currency |
| Confirm payment | STRIPE_CONFIRM_PAYMENT_INTENT | payment_intent |
| List subscriptions | STRIPE_LIST_SUBSCRIPTIONS | customer |
| Create subscription | STRIPE_POST_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS | customer, items |
| Update subscription | STRIPE_UPDATE_SUBSCRIPTION | subscription, fields |
| List invoices | STRIPE_LIST_INVOICES | customer |
| Create invoice | STRIPE_CREATE_INVOICE | customer |
| Search invoices | STRIPE_SEARCH_INVOICES | query |
| List products | STRIPE_LIST_PRODUCTS | active |
| Search products | STRIPE_SEARCH_PRODUCTS | query |
| List prices | STRIPE_LIST_PRICES | product |
| Search prices | STRIPE_GET_PRICES_SEARCH | query |
| List refunds | STRIPE_LIST_REFUNDS | charge |
| Create refund | STRIPE_CREATE_REFUND | charge, amount |
| Payment methods | STRIPE_LIST_CUSTOMER_PAYMENT_METHODS | customer |
| Checkout session | STRIPE_CREATE_CHECKOUT_SESSION | line_items |
| List payment intents | STRIPE_LIST_PAYMENT_INTENTS | customer |
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.