Content
50%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a broad reference for Stripe operations via Rube MCP with good structural organization and useful details like ID prefixes and amount formatting. However, it suffers from significant repetition (pitfalls repeated across sections), lacks concrete executable examples or actual tool call syntax, and marks every workflow step as [Optional] which undermines workflow clarity. Financial operations would benefit from explicit validation/verification steps.
Suggestions
Add at least one concrete, end-to-end example showing actual MCP tool call syntax with real parameters and expected response structure (e.g., creating a customer and then a subscription for them).
Remove the [Optional] markers from workflow steps and instead provide distinct workflows for distinct tasks (e.g., 'To create a charge: step 1, step 2, step 3') rather than listing all possible tools as optional.
Consolidate repeated pitfalls (amount formatting, currency units) into the single 'Known Pitfalls' section and remove duplicates from individual workflow sections.
Add validation/verification steps to financial workflows — e.g., after creating a payment intent, verify its status before confirming; after issuing a refund, check the refund status.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has significant repetition — amount formatting pitfalls are mentioned three times (in charges, refunds, and the dedicated section). The 'Known Pitfalls' section repeats information already covered in individual workflow sections. The quick reference table is useful but overlaps heavily with the workflow sections. Some content like 'When to Use: This skill is applicable to execute the workflow or actions described in the overview' is pure filler. | 3 / 5 |
Actionability | The skill names specific tools and parameters, which is helpful, but lacks executable examples — no actual MCP tool call syntax or concrete input/output examples are shown. Every tool in the workflows is marked [Optional], making it unclear what the actual recommended sequence is for a given task. The setup steps are concrete, but the core workflows read more like reference documentation than actionable guidance. | 3 / 5 |
Workflow Clarity | Workflows are listed as sequences but every step is marked [Optional], undermining the concept of a workflow. There are no validation checkpoints — for example, after creating a payment intent, there's no step to verify it was created successfully before confirming it. For financial operations (charges, refunds), the absence of verification/confirmation steps is a notable gap. The setup section has a reasonable sequence with a connection verification step. | 3 / 5 |
Progressive Disclosure | The content is reasonably structured with clear section headers and a useful quick reference table. However, at ~180 lines with significant repetition, some content (like the full quick reference table or detailed per-workflow pitfalls) could be split into separate files. There are no bundle files or external references, and the skill is long enough that progressive disclosure would benefit from them. | 3 / 5 |
Total | 12 / 20 Passed |