Name: stripe-payment-links
Rating: 55.2 (1 reviews)
Author: membranedev

stripe-payment-links

Stripe Payment Links integration. Manage data, records, and automate workflows. Use when the user wants to interact with Stripe Payment Links data.

Quality

63%

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-payment-links/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 content is an efficient, actionable operational guide with strong command examples and a sensible connection-state feedback loop. Its main weaknesses are the empty 'Popular actions' section, a broken 'Step 2' reference, and absent validation guidance for destructive proxy requests.

Suggestions

Populate 'Popular actions' with concrete example actions (e.g. creating a payment link, listing line items) instead of restating the discovery command.

Fix the orphaned 'skip to Step 2' reference by either labeling a Step 2 heading or rewording to 'skip to Searching for actions'.

Add a validation/verification checkpoint for destructive proxy requests (e.g. verify the resource exists before DELETE, or confirm the response status before proceeding).

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-and-flag reference material with minimal concept padding, though the 'Popular actions' section redundantly repeats the action-list command and the best-practices bullets restate earlier guidance.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action search/run, and proxy with a clear flags table, but the 'Popular actions' section never lists actual actions and run examples stay on generic placeholders like <actionId>.	4 / 5
Workflow Clarity	A clear install-auth-connect-search-run sequence exists with a polling feedback loop for connection states, but the 'skip to Step 2' reference is orphaned (no Step 2 heading) and destructive proxy operations (POST/PUT/DELETE) lack validation checkpoints, capping this at 3.	3 / 5
Progressive Disclosure	The single-file skill is well-organized into clearly headed sections with no nested references and easy navigation; the only gaps are the redundant 'Popular actions' section and the awkward '1b' / missing 'Step 2' flow.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly includes an explicit 'Use when' trigger and names a distinct domain, but its capability description is generic boilerplate rather than concrete Stripe Payment Links actions. Tightening the 'what' with specific operations would lift specificity and completeness.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Stripe Payment Links actions such as 'create, list, and share payment links and line items'.

Add natural trigger variations like 'payment links', 'Stripe checkout links', or 'sell products via link' to broaden keyword coverage.

Make the 'when' clause more specific, e.g. 'Use when the user wants to create or manage Stripe Payment Links for products or subscriptions.'

Dimension	Reasoning	Score
Specificity	The description names the domain ('Stripe Payment Links integration') but the actions are generic boilerplate ('Manage data, records, and automate workflows') rather than concrete operations like creating or sharing payment links.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Stripe Payment Links data'), though the 'what' is vague and the trigger could be more specific.	4 / 5
Trigger Term Quality	The natural phrase 'Stripe Payment Links' appears and is reused in the trigger clause, but there is little variation or synonym coverage beyond that single term.	3 / 5
Distinctiveness Conflict Risk	The specific 'Stripe Payment Links' trigger gives it a clear niche with minimal conflict risk, though the generic 'manage data, records, and automate workflows' boilerplate overlaps with sibling Membrane integration skills.	4 / 5
	Total	13 / 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-payment-links/SKILL.md
Commit: f484c82

Reviewed: 4 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.