stripe

Stripe payment platform integration. Manage payments, subscriptions, invoices, and customers via Stripe API.

Quality

52%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xterrybit/stripe/SKILL.md

Quality

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.

This description has strong specificity and distinctiveness by clearly naming Stripe and listing concrete capabilities. However, it lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know when to select this skill, and could benefit from additional natural trigger terms users commonly use when discussing payments.

Suggestions

Add a 'Use when...' clause with trigger scenarios like 'Use when the user mentions Stripe, payment processing, billing integration, or needs to handle charges and refunds'

Include additional natural trigger terms users might say: 'billing', 'charges', 'refunds', 'checkout', 'payment gateway', 'recurring payments'

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Manage payments, subscriptions, invoices, and customers' - these are distinct, actionable capabilities within the Stripe domain.	3 / 3
Completeness	Clearly answers 'what' (manage payments, subscriptions, invoices, customers via Stripe API) but lacks an explicit 'Use when...' clause or trigger guidance for when Claude should select this skill.	2 / 3
Trigger Term Quality	Includes good keywords like 'Stripe', 'payments', 'subscriptions', 'invoices', 'customers', and 'API', but missing common variations users might say like 'billing', 'charges', 'refunds', 'checkout', or 'payment processing'.	2 / 3
Distinctiveness Conflict Risk	Clearly scoped to Stripe specifically with 'Stripe payment platform integration' and 'Stripe API' - unlikely to conflict with generic payment skills or other payment provider integrations.	3 / 3
	Total	10 / 12 Passed

Implementation

37%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is admirably concise but sacrifices actionability - it reads more like a feature list than executable guidance. The single curl example is insufficient for the breadth of features advertised, and there are no workflows for complex operations like subscription lifecycle management or webhook verification.

Suggestions

Add executable code examples for each major feature (payment intents, subscriptions, invoices, refunds) - not just curl but complete request/response patterns

Include a workflow for subscription management with validation steps (e.g., check customer exists -> create subscription -> verify status -> handle failures)

Add webhook handling guidance with signature verification code and common event types to handle

Either expand inline with concrete examples or create separate reference files (SUBSCRIPTIONS.md, WEBHOOKS.md) for complex features

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, with no unnecessary explanations of what Stripe is or how payment APIs work. Every section serves a purpose and assumes Claude's competence.	3 / 3
Actionability	The skill provides only one concrete curl example and lists features/usage as vague descriptions. Missing executable code for payment intents, subscriptions, invoices, refunds, and webhook handling - the core advertised features.	1 / 3
Workflow Clarity	No workflows are defined for multi-step processes like subscription management or refund processing. No validation steps, error handling, or sequencing for operations that could fail or have side effects.	1 / 3
Progressive Disclosure	The content is well-organized with clear sections, but for a skill covering this many features (payments, subscriptions, invoices, webhooks), it should either provide more inline detail or reference separate files for each domain.	2 / 3
	Total	7 / 12 Passed

Validation

81%

Warnings & errors only

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: 45f9fac

Reviewed: 27 days ago

Table of Contents

Discovery Implementation Validation

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.