stripe
Stripe payment platform integration. Manage payments, subscriptions, invoices, and customers via Stripe API.
43
45%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xterrybit/stripe/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 concise and specific about the domain (Stripe) and the concrete entities it manages, making it distinctive and actionable. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Adding common trigger term variations like 'billing', 'charges', or 'refunds' would also improve matching.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Stripe integration, payment processing, billing, or managing subscriptions and invoices.'
Include additional natural trigger terms users might say, such as 'billing', 'charges', 'refunds', 'checkout', 'recurring payments', or 'payment gateway'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Manage payments, subscriptions, invoices, and customers via Stripe API' covers four distinct domain objects with a clear action verb and specifies the integration method (Stripe API). | 3 / 3 |
Completeness | Clearly answers 'what does this do' (manage payments, subscriptions, invoices, customers via Stripe API), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes good keywords like 'Stripe', 'payments', 'subscriptions', 'invoices', 'customers', and 'Stripe API', but misses common user variations like 'billing', 'charges', 'refunds', 'checkout', 'payment processing', or 'recurring payments'. | 2 / 3 |
Distinctiveness Conflict Risk | The explicit mention of 'Stripe' as the platform creates a clear niche that is unlikely to conflict with other payment or general API skills. The combination of 'Stripe' + specific entities (payments, subscriptions, invoices) makes it highly distinguishable. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
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 |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- Demerzels-lab/elsamultiskillagent
- Commit
f45fcb5
- 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.