Stripe Automation via Rube MCP

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/stripe-automation

https://github.com/sickn33/antigravity-awesome-skills

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

ORIGIN.md

Stripe Automation via Rube MCP Automate Stripe payment operations through Composio's Stripe toolkit via Rube MCP.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Prerequisites, Common Patterns, Known Pitfalls, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• This skill is applicable to execute the workflow or actions described in the overview.
• Use when the request clearly matches the imported source intent: Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds. Always search tools first for current schemas.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.
• Use when copied upstream references, examples, or scripts materially improve the answer.
• Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.

Operating Table

metadata.json

ORIGIN.md

SKILL.md

SKILL.md

## Related Skills

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds
2. Call RUBEMANAGECONNECTIONS with toolkit stripe
3. If connection is not ACTIVE, follow the returned auth link to complete Stripe connection
4. Confirm connection status shows ACTIVE before running any workflows
5. STRIPESEARCHCUSTOMERS - Search customers by email/name [Optional]
6. STRIPELISTCUSTOMERS - List all customers [Optional]
7. STRIPECREATECUSTOMER - Create a new customer [Optional]

Imported Workflow Notes

Imported: Setup

Get Rube MCP: Add

https://rube.app/mcp

1. Verify Rube MCP is available by confirming

   RUBE_SEARCH_TOOLS

   responds
2. Call

   RUBE_MANAGE_CONNECTIONS

   with toolkit

   stripe

3. If connection is not ACTIVE, follow the returned auth link to complete Stripe connection
4. Confirm connection status shows ACTIVE before running any workflows

Imported: Core Workflows

1. Manage Customers

When to use: User wants to create, update, search, or list Stripe customers

Tool sequence:

1. STRIPE_SEARCH_CUSTOMERS

   - Search customers by email/name [Optional]

2. STRIPE_LIST_CUSTOMERS

   - List all customers [Optional]

3. STRIPE_CREATE_CUSTOMER

   - Create a new customer [Optional]

4. STRIPE_POST_CUSTOMERS_CUSTOMER

   - Update a customer [Optional]

Key parameters:

• email

  : Customer email

• name

  : Customer name

• description

  : Customer description

• metadata

  : Key-value metadata pairs

• customer

  : 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:

1. STRIPE_LIST_CHARGES

   - List charges with filters [Optional]

2. STRIPE_CREATE_PAYMENT_INTENT

   - Create a payment intent [Optional]

3. STRIPE_CONFIRM_PAYMENT_INTENT

   - Confirm a payment intent [Optional]

4. STRIPE_POST_CHARGES

   - Create a direct charge [Optional]

5. 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 ID

• payment_method

  : Payment method ID

• description

  : 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:

1. STRIPE_LIST_SUBSCRIPTIONS

   - List subscriptions [Optional]

2. STRIPE_POST_CUSTOMERS_CUSTOMER_SUBSCRIPTIONS

   - Create subscription [Optional]

3. STRIPE_RETRIEVE_SUBSCRIPTION

   - Get subscription details [Optional]

4. STRIPE_UPDATE_SUBSCRIPTION

   - Modify subscription [Optional]

Key parameters:

• customer

  : Customer ID

• items

  : 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:

1. STRIPE_LIST_INVOICES

   - List invoices [Optional]

2. STRIPE_SEARCH_INVOICES

   - Search invoices [Optional]

3. STRIPE_CREATE_INVOICE

   - Create an invoice [Optional]

Key parameters:

• customer

  : Customer ID for invoice

• collection_method

  : 'charge_automatically' or 'send_invoice'

• days_until_due

  : Days until invoice is due

Pitfalls:

• Invoices auto-finalize by default; use

  auto_advance: false

  for draft invoices

5. Manage Products and Prices

When to use: User wants to list or search products and their pricing

Tool sequence:

1. STRIPE_LIST_PRODUCTS

   - List products [Optional]

2. STRIPE_SEARCH_PRODUCTS

   - Search products [Optional]

3. STRIPE_LIST_PRICES

   - List prices [Optional]

4. STRIPE_GET_PRICES_SEARCH

   - Search prices [Optional]

Key parameters:

• active

  : Filter by active/inactive status

• query

  : 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:

1. STRIPE_LIST_REFUNDS

   - List refunds [Optional]

2. STRIPE_POST_CHARGES_CHARGE_REFUNDS

   - Create a refund [Optional]

3. STRIPE_CREATE_REFUND

   - Create refund via payment intent [Optional]

Key parameters:

• charge

  : Charge ID for refund

• amount

  : 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

Imported: Prerequisites

• Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
• Active Stripe connection via

  RUBE_MANAGE_CONNECTIONS

  with toolkit

  stripe

• Always call

  RUBE_SEARCH_TOOLS

  first to get current tool schemas

Examples

Example 1: Ask for the upstream workflow directly

Use @stripe-automation to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @stripe-automation against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @stripe-automation for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @stripe-automation using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
• Treat generated examples as scaffolding; adapt them to the concrete task before execution.
• Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/stripe-automation

metadata.json

ORIGIN.md

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @server-management

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @service-mesh-expert

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @service-mesh-observability

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

• @sexual-health-analyzer

  - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

references

references/n/a

examples

examples/n/a

scripts

scripts/n/a

agents

agents/n/a

assets

assets/n/a

Imported Reference Notes

Imported: Quick Reference

Imported: 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

  limit

  parameter (max 100)
• Check

  has_more

  in response
• Pass

  starting_after

  with last object ID for next page
• Continue until

  has_more

  is false

Imported: 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_

Imported: 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.