Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds. Always search tools first for current schemas.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill stripe-automation62
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Connection setup and payment processing workflow
RUBE_SEARCH_TOOLS first
0%
100%
RUBE_MANAGE_CONNECTIONS setup
0%
100%
ACTIVE status check
0%
100%
Search before create customer
100%
100%
Payment intent over direct charge
100%
100%
Amount in cents
100%
100%
Lowercase currency code
100%
100%
Duplicate customer pitfall noted
100%
100%
Customer ID prefix
100%
100%
Payment intent ID prefix
100%
100%
Without context: $0.5980 · 2m 13s · 20 turns · 159 in / 7,199 out tokens
With context: $0.3265 · 1m 21s · 15 turns · 20 in / 4,246 out tokens
Subscription setup with product catalog and pagination
RUBE_SEARCH_TOOLS first
0%
100%
Connection verification
0%
100%
Price IDs for subscriptions
100%
100%
Products-prices separation
70%
100%
Payment method prerequisite
100%
100%
Pagination limit parameter
100%
100%
Pagination has_more check
100%
100%
Pagination starting_after
100%
100%
Cancellation options
0%
0%
Correct tool for subscription creation
0%
100%
Without context: $0.4738 · 2m 22s · 22 turns · 73 in / 8,096 out tokens
With context: $0.3436 · 1m 27s · 15 turns · 265 in / 4,902 out tokens
Draft invoicing and refund processing
RUBE_SEARCH_TOOLS first
0%
100%
Connection setup documented
0%
100%
auto_advance false for drafts
100%
100%
Collection methods named
100%
100%
days_until_due parameter
100%
100%
Full refund by omitting amount
100%
100%
Valid refund reasons
100%
100%
USD amount in cents
100%
100%
JPY zero-decimal amount
100%
100%
List charges before refund
100%
100%
Without context: $0.3592 · 1m 40s · 18 turns · 63 in / 5,410 out tokens
With context: $0.3382 · 1m 16s · 17 turns · 177 in / 4,140 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.