Content
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a thin skeleton that lists many Stripe capabilities but provides almost no actionable guidance for any of them. Only one curl example is given, with no workflows, error handling, or validation for financial operations. It reads more like a feature advertisement than an instructional skill.
Suggestions
Add concrete, executable curl or SDK code examples for each major feature (payment intents, subscriptions, refunds, invoices) rather than just listing them as bullets.
Include a multi-step workflow for at least one common operation (e.g., creating a payment intent → confirming → handling errors) with explicit validation checkpoints.
Add error handling guidance and common failure modes (e.g., invalid API key, declined payments, idempotency keys) since these are financial operations.
Either provide detailed reference files for each feature area (e.g., SUBSCRIPTIONS.md, WEBHOOKS.md) or expand the main skill with actionable content for the advertised capabilities.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Reasonably brief, but the feature bullet list is essentially a table of contents that doesn't add actionable value. The usage examples section lists natural language prompts without showing how they map to actual API calls, which is filler. | 2 / 3 |
Actionability | Only one concrete API call is provided (list charges via curl). There are no executable examples for payment intents, subscriptions, invoices, refunds, or webhooks—the core advertised features. The natural language usage examples are not actionable instructions. | 1 / 3 |
Workflow Clarity | There is no multi-step workflow, no sequencing of operations, and no validation or error-handling guidance. For a payment integration skill involving destructive/financial operations, the absence of any verification steps or feedback loops is a significant gap. | 1 / 3 |
Progressive Disclosure | The content is short and organized into sections, which is fine for a simple skill. However, there are no references to any supporting files for the many features listed, and the single API example is insufficient to cover the breadth of topics mentioned. The feature list promises depth that isn't delivered anywhere. | 2 / 3 |
Total | 6 / 12 Passed |