Content
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 warnings. However, it suffers from redundancy (amount formatting and pitfalls repeated multiple times), lacks concrete executable examples of actual MCP tool calls, and marks every workflow step as [Optional] which undermines actionability. Financial operations like charges and refunds would benefit from explicit validation/verification steps.
Suggestions
Add at least one concrete, complete example showing an actual RUBE_SEARCH_TOOLS call followed by a Stripe tool call with real input parameters and expected output structure.
Remove the [Optional] annotations from workflow steps and instead clearly indicate which steps are required vs optional, or show the minimum viable sequence for each workflow.
Add explicit validation steps after destructive/financial operations (e.g., verify charge was created successfully, confirm refund status) to improve workflow safety.
Consolidate the duplicated pitfalls — remove per-section 'amount is in smallest currency unit' warnings and keep only the 'Common Patterns' section for shared knowledge.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but has significant redundancy — the 'Known Pitfalls' section repeats amount unit warnings already stated in multiple workflow sections, and the quick reference table largely duplicates information from the core workflows. The ID prefixes and amount formatting sections appear twice in different forms. | 2 / 3 |
Actionability | The skill provides specific tool names and parameter lists, which is useful, but lacks any executable code or concrete MCP call examples with actual input/output. Every tool step is marked [Optional], making it unclear what the actual recommended sequence is. The instruction to 'Always call RUBE_SEARCH_TOOLS first' is good but no example call is shown. | 2 / 3 |
Workflow Clarity | The setup section has a clear 4-step sequence with a validation checkpoint (confirm ACTIVE status). However, the core workflows lack validation steps — for example, after creating a charge or refund, there's no verification step. For financial operations (charges, refunds), missing validation/feedback loops is a notable gap. Every step being marked [Optional] undermines the sequential clarity. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table, but it's quite long (~180 lines) with no bundle files to offload detail into. The repeated pitfalls and the large reference table could be split into separate files. The single external link to Composio docs is appropriate but the monolithic structure could benefit from splitting workflows into separate references. | 2 / 3 |
Total | 8 / 12 Passed |