stripe-automation
Automate Stripe Operations with Rube MCP
Stripe operations require exact IDs, amount units, and tool sequences. This skill guides Claude, Codex, and Claude Code through Rube MCP workflows for common Stripe tasks.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "stripe-automation" from https://skillstore.io/skills/sickn33-stripe-automation.md and its manifest at https://skillstore.io/api/skills/sickn33-stripe-automation/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "stripe-automation". Find a customer by email and update the billing note.
Expected outcome:
The skill first searches customers, shows matching customer IDs, asks which customer to update, then prepares the metadata change.
Using "stripe-automation". Refund 50 dollars on a specific charge.
Expected outcome:
The skill converts the amount to 5000 cents, verifies the charge, and asks for approval before creating a partial refund.
Using "stripe-automation". Create a subscription for a customer with a known price.
Expected outcome:
The skill retrieves available subscription tools, confirms the customer and price item, then prepares the subscription request.
Security Audit
High RiskMost static external command findings are false positives from Markdown backticks around tool names and parameters. The hardcoded Rube MCP URL is a real external dependency, and semantic review found risk from privileged Stripe operations without explicit approval or trust-boundary guidance. No prompt injection text was found in SKILL.md.
Confirmed security concerns (2)
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚙️ External commands (57)
🌐 Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-stripe-automation/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-stripe-automation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-stripe-automation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-stripe-automation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-stripe-automation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). stripe-automation security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-stripe-automation/audits/4BibTeX citation
@techreport{sickn33-sickn33-stripe-automation-2026,
author = {sickn33},
title = {stripe-automation security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/sickn33-stripe-automation/audits/4},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "stripe-automation security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-stripe-automation/audits/4"
identifiers:
- type: other
value: "skillstore:sickn33-stripe-automation:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Customer Support Updates
Search customers, review billing records, and update customer metadata after verifying the customer ID.
Revenue Operations Review
List subscriptions, invoices, products, and prices to reconcile account state before billing changes.
Developer Billing Tasks
Create test payment intents, subscriptions, invoices, or refunds while checking amount units and object IDs.
Try These Prompts
Use the Stripe automation skill to search for a customer by email. Show the matching customer IDs before suggesting any update.
Use Rube MCP to create a draft Stripe invoice for this customer. Confirm collection method, due date, and auto_advance setting first.
List the customer subscriptions, retrieve the target subscription, and summarize the price IDs before preparing an update.
Review the charge, confirm the refund amount in smallest currency units, and prepare the refund request only after my approval.
Best Practices
- Search or retrieve objects before creating charges, subscriptions, invoices, or refunds.
- Confirm amounts in the smallest currency unit before every payment or refund action.
- Use test mode or limited permissions when validating new Stripe workflows.
Avoid
- Do not create direct charges when a payment intent flow is available.
- Do not issue refunds or capture payments without explicit user approval.
- Do not assume email addresses uniquely identify Stripe customers.