CtrlK
BlogDocsLog inGet started
Tessl Logo

stripe-automation

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

78

1.32x
Quality

69%

Does it follow best practices?

Impact

97%

1.32x

Average score across 3 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/stripe-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

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

The content is well-structured and actionable with concrete Rube tool slugs and pitfalls, but it is held back by redundant amount-formatting/ID details and a lack of validation feedback loops for its destructive financial operations.

Suggestions

Consolidate the repeated "smallest currency unit" and ID-prefix information into a single section to remove redundancy.

Add explicit validate-then-confirm checkpoints to the charges and refunds workflows (e.g., verify the charge/refund status before proceeding).

Include one concrete example showing the actual MCP tool call shape so the tool sequences are copy-paste ready.

DimensionReasoningScore

Conciseness

The body is efficient and avoids re-explaining Stripe basics, but repeats "smallest currency unit" and ID-prefix information across Common Patterns and Known Pitfalls sections that could be trimmed.

4 / 5

Actionability

Concrete tool slugs, parameters with example values ('cus_xxx', 'usd', cents), and specific pitfalls make the guidance mostly executable; the minor gap is the absence of an actual MCP call-syntax example showing how a tool is invoked.

4 / 5

Workflow Clarity

Workflows list clear numbered tool sequences with a setup validation checkpoint, but the financial/destructive operations (charges, refunds, subscription changes) lack validate-then-confirm feedback loops, which caps workflow clarity at 3 per the rubric.

3 / 5

Progressive Disclosure

No bundle files exist, so the skill is a single self-contained SKILL.md, but it is well-sectioned (workflows, common patterns, pitfalls, quick reference table) with clear internal navigation; lacking external references it stops just short of a 5.

4 / 5

Total

15

/

20

Passed

Description

70%Weight 40%Scale 1-5

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 clearly communicates its Stripe-automation niche and lists concrete resources, but it lacks an explicit "Use when..." trigger clause, which limits its completeness. Distinctiveness and trigger terms are strong.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to manage Stripe customers, charges, subscriptions, invoices, products, or refunds."

Include natural synonyms users say ("payments", "billing", "payment intents", "checkout") to broaden trigger coverage.

Express resource handling as verbs (create, search, list, refund) rather than bare nouns to sharpen specificity.

DimensionReasoningScore

Specificity

Names the Stripe domain and several concrete resource areas ("customers, charges, subscriptions, invoices, products, refunds") plus a concrete action ("search tools first"), but actions are mostly domain nouns rather than verbs, leaving minor coverage gaps short of comprehensive.

4 / 5

Completeness

The "what" is clear (automate Stripe tasks across listed resources), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms like "Stripe", "customers", "charges", "subscriptions", "invoices", "refunds", but common variations a user might say ("payments", "billing", "payment intents", "checkout") are missing.

4 / 5

Distinctiveness Conflict Risk

Clearly scoped to Stripe automation via Rube MCP (Composio) with distinct triggers, giving it a clear niche and minimal conflict risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.