Name: stripe
Rating: 62.4 (1 reviews)
Author: membranedev

stripe

Stripe integration. Manage Customers, Products, Payouts, Transfers. Use when the user wants to interact with Stripe data.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/stripe/SKILL.md

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 body is highly actionable with concrete Membrane commands and useful tables, but loses points for explaining Stripe concepts Claude already knows and for offering no verification guidance around destructive operations. Structure is good but everything is inlined into one long file.

Suggestions

Remove or drastically shorten the opening paragraph explaining what Stripe is — Claude already knows this; lead instead with the actionable Membrane workflow.

Add an explicit verification/confirm-before-acting step for destructive actions (delete-product, update-product/subscription/price), e.g. read-then-write or a dry-run check, and resolve the dangling "skip to Step 2" reference.

Move the popular-actions and proxy-flags tables into a separate reference file (e.g. ACTIONS.md) referenced from the body to reduce inline length and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("Stripe is a payment processing platform that enables businesses to accept online payments...") explains what Stripe is — a concept Claude already knows and which the rubric penalizes — alongside a few fluffy sentences ("so you can focus on the integration logic rather than auth plumbing"); the rest is mostly efficient commands and tables.	3 / 5
Actionability	The body provides fully executable, copy-paste-ready commands ("membrane connection ensure", "membrane action list --intent", "membrane action run", "membrane request") plus a popular-actions table with keys and a proxy-flags table, covering the common cases as anchor 5 requires.	5 / 5
Workflow Clarity	The connection sequence has explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-after-action feedback loop, but the skill enables destructive actions (delete-product, update-product/subscription/price) with no verification guidance, and the "skip to Step 2" reference is dangling — the rubric's destructive-operation cap prevents scoring above 3.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections, but with no bundle files everything lives in a single ~180-line file (exceeding the 50-line simple-skill exception) and reference-like material (the popular-actions and proxy-flags tables) is inlined rather than split into a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

78%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 cleanly states what the skill does and when to use it, with Stripe-specific entities that make it highly distinct. Its main weakness is a single generic verb and a "when" clause that lists no concrete user trigger phrases.

Dimension	Reasoning	Score
Specificity	"Manage Customers, Products, Payouts, Transfers" names the Stripe domain plus several concrete entities, but relies on a single generic verb ("Manage"); the multiple specific objects lift it above the anchor-3 midpoint rather than reaching the multi-verb comprehensiveness of anchor 5.	4 / 5
Completeness	Both "what" ("Stripe integration. Manage Customers, Products, Payouts, Transfers.") and "when" ("Use when the user wants to interact with Stripe data.") are present, but the "when" clause is generic and lacks the concrete trigger phrases that anchor 5 requires.	4 / 5
Trigger Term Quality	Natural terms "Stripe", "Customers", "Products", "Payouts", "Transfers" give good keyword coverage, but common synonyms users say (payments, subscriptions, invoices, charges) are missing, keeping it below anchor 5.	4 / 5
Distinctiveness Conflict Risk	"Stripe integration" with Stripe-specific entities is a clear niche with distinct triggers and minimal overlap risk with other skills, matching the anchor-5 example.	5 / 5
	Total	17 / 20 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: membranedev/application-skills
Path: skills/stripe/SKILL.md
Commit: f484c82

Reviewed: ~19 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.