stripe-automation
Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds. Always search tools first for current schemas.
72
58%
Does it follow best practices?
Impact
97%
1.32xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/stripe-automation/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is strong in specificity and distinctiveness, clearly identifying Stripe as the domain and listing concrete resource types. However, it lacks an explicit 'Use when...' trigger clause and could benefit from more natural user-facing keywords like 'payment' or 'billing' to improve discoverability.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Stripe payments, billing, subscriptions, or managing Stripe resources.'
Include natural user-facing trigger terms like 'payment', 'billing', 'checkout', 'payment processing' that users would more commonly say than technical entity names.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete entities/actions: customers, charges, subscriptions, invoices, products, refunds. Also includes a concrete operational instruction to search tools first for current schemas. | 3 / 3 |
Completeness | Clearly answers 'what' (automate Stripe tasks across multiple entities), but lacks an explicit 'Use when...' clause. The 'when' is only implied by the domain keywords. Per rubric guidelines, missing 'Use when...' caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes good domain keywords like 'Stripe', 'customers', 'charges', 'subscriptions', 'invoices', 'products', 'refunds', but misses common user phrasings like 'payment', 'billing', 'checkout', 'payment processing'. The mention of 'Rube MCP (Composio)' is technical jargon users wouldn't naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Stripe' and 'Rube MCP (Composio)' as clear identifiers. The specific mention of Stripe-related entities (charges, subscriptions, invoices) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive catalog of Stripe operations via Rube MCP with good structural organization and useful pitfall callouts. Its main weaknesses are the lack of concrete executable examples showing actual tool invocations, repetition of information across sections (especially amount formatting), and missing validation/confirmation steps for financial operations. The content would benefit from being more concise with concrete examples rather than exhaustive parameter listings.
Suggestions
Add at least 2-3 concrete tool invocation examples with actual parameter values (e.g., a complete STRIPE_CREATE_CUSTOMER call and a RUBE_SEARCH_TOOLS call) to improve actionability.
Consolidate repeated pitfalls (amount formatting, currency units) into a single 'Common Pitfalls' section and remove duplicates from individual workflow sections.
Add explicit verification steps after financial operations (e.g., 'After creating a charge, retrieve it to confirm status') — missing validation for destructive/financial operations is a significant gap.
Consider splitting detailed workflow sections into a separate STRIPE_WORKFLOWS.md file, keeping SKILL.md as a concise overview with the setup, common patterns, and quick reference table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but contains significant repetition — amount formatting pitfalls are mentioned at least 3 times across different sections, and the Known Pitfalls section largely duplicates information already stated in individual workflow pitfalls. The quick reference table adds value but the overall content could be tightened by ~30%. | 2 / 3 |
Actionability | Tool names and key parameters are clearly listed, which is helpful. However, there are no executable examples showing actual tool invocations with concrete parameter values — everything remains at the level of listing tool names and parameter names without showing a complete call. The instruction to 'always call RUBE_SEARCH_TOOLS first' is good but no example of what that call looks like is provided. | 2 / 3 |
Workflow Clarity | The setup section has a clear 4-step sequence with a validation checkpoint (confirm ACTIVE status). However, the core workflows mark every step as [Optional] without guidance on which combinations are typical or required, and there are no validation/verification steps after performing operations like creating charges or refunds — risky financial operations that warrant explicit confirmation steps. | 2 / 3 |
Progressive Disclosure | The content is well-sectioned with clear headers and a useful quick reference table. However, at ~180 lines it's quite long and could benefit from splitting detailed workflow sections into separate files, keeping SKILL.md as a concise overview. The external link to Composio docs is good but the inline content is heavy for a single file. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
7cc63f3
- Reviewed
Table of Contents
Is this your skill?
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.