stripe-automation

Automate Stripe tasks via Rube MCP (Composio): customers, charges, subscriptions, invoices, products, refunds. Always search tools first for current schemas.

1.32x

Quality

—

Does it follow best practices?

Impact

97%

1.32x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

50%

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

The body is well-structured and actionable, with concrete tool slugs, parameters, and pitfalls across six workflows plus a useful quick-reference table. It is held at 2 across dimensions by redundant pitfall content, absent call examples, missing verification on financial operations, and a monolithic single-file layout.

Suggestions

Add explicit validation/verification steps to the destructive financial workflows (e.g., retrieve and confirm a charge or refund status after creating it) to raise workflow clarity.

Remove the duplicated amount-unit and ID-prefix content between 'Common Patterns', 'Known Pitfalls', and per-workflow pitfalls — keep each fact in one place to improve conciseness.

Provide at least one complete example tool-call payload (e.g., a full STRIPE_CREATE_PAYMENT_INTENT argument object) so guidance is copy-paste ready, and consider moving the full Quick Reference table into a one-level-deep reference file.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's competence (no 'what is Stripe' padding), but the 'Known Pitfalls' section repeats amount-unit and ID-prefix info already covered in 'Common Patterns' and per-workflow pitfalls, and the Quick Reference table duplicates tool slugs already listed in each workflow.	2 / 3
Actionability	It names real tool slugs (e.g. STRIPE_CREATE_CUSTOMER) and key parameters with specific values, but provides no complete executable tool-call examples with argument payloads, leaving guidance concrete but not copy-paste ready.	2 / 3
Workflow Clarity	Setup has a numbered sequence with a validation checkpoint ('Confirm connection status shows ACTIVE'), but the destructive/financial workflows (charges, refunds) lack verification steps, capping workflow clarity at 2 per the rubric.	2 / 3
Progressive Disclosure	Content is well-organized into clear sections but is entirely inline in a ~200-line SKILL.md with no external references; the detailed per-workflow reference and Quick Reference table are candidates for one-level-deep split files.	2 / 3
	Total	8 / 12 Passed

Description

72%

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 specific and distinctive, listing six concrete Stripe resource areas with natural trigger terms. It is held back by the absence of an explicit 'Use when' trigger clause and generic action verbs.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when the user needs to manage Stripe customers, charges, subscriptions, invoices, products, or refunds') to satisfy the completeness 'when' requirement.

Replace the generic verb 'Automate Stripe tasks' with concrete actions (e.g., 'create, search, update, and refund') to raise specificity from domain-and-objects to enumerated actions.

Dimension	Reasoning	Score
Specificity	Names the Stripe domain and six concrete resource types ('customers, charges, subscriptions, invoices, products, refunds') but the action verbs are generic ('Automate Stripe tasks') rather than enumerated concrete actions like create/list/refund, so it is not fully comprehensive.	2 / 3
Completeness	It clearly answers 'what' (Automate Stripe tasks across six resource types) but lacks an explicit 'Use when...' trigger clause, so per the rubric guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Covers natural terms users would say — 'Stripe', 'customers', 'charges', 'subscriptions', 'invoices', 'products', 'refunds' — giving good coverage of the phrasings a user would naturally use when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The Stripe + Rube MCP (Composio) niche is distinct with specific resource triggers, making it unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Commit: 366e45b

Reviewed: about 23 hours 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.