CtrlK
BlogDocsLog inGet started
Tessl Logo

stripe-link-cli

Agent payments via Stripe Link — cards, SPT, approvals.

62

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/payments/stripe-link-cli/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 a strong, executable runbook with clear sequencing, validation checkpoints, and security-conscious handling of card data. Minor verbosity in optional sections and a fully inline structure keep it just below the top anchors on conciseness and progressive disclosure.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no explaining of what a card or MPP is), with only minor trimmable sections such as the optional MCP registration block and the verbose trigger-phrase list.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands with concrete flags covering the common cases (auth, merchant evaluation, payment methods, spend request, secure retrieval, mpp pay).

5 / 5

Workflow Clarity

The 7-step procedure is clearly sequenced with explicit validation checkpoints ("Do not proceed past this step until auth status confirms login", confirm total before issuing) and a terminal verification step, with security handling for the sensitive PAN operation.

5 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with no bundle files needed, but everything is inlined rather than split into one-level-deep references, so it stops short of the explicit reference-signaling the top anchor rewards.

4 / 5

Total

18

/

20

Passed

Description

62%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 is specific and clearly distinct, but it omits explicit "when to use" guidance and relies on jargon (SPT) rather than natural user phrasing, weakening trigger-term quality and completeness.

Suggestions

Add an explicit "Use when..." clause covering natural triggers such as "buy X", "pay for X", or "complete checkout".

Expand "SPT" to a user-recognizable term (e.g., "Shared Payment Tokens") and add common synonyms like "checkout" or "payment method".

Briefly state the gating condition (e.g., "every spend requires in-app approval") so the when/why is explicit.

DimensionReasoningScore

Specificity

"Agent payments via Stripe Link — cards, SPT, approvals" names the domain and lists several specific concrete actions (cards, SPT, approvals), with only minor coverage gaps.

4 / 5

Completeness

The "what" is clear (agent payments via Stripe Link using cards, SPT, approvals) but there is no "Use when..." clause or equivalent trigger guidance, capping completeness at 3.

3 / 5

Trigger Term Quality

It includes relevant domain keywords (Stripe Link, cards, SPT) but leans on technical jargon like "SPT" and lacks the natural phrases a user would say ("buy", "pay for", "checkout").

3 / 5

Distinctiveness Conflict Risk

"Agent payments via Stripe Link — cards, SPT, approvals" carves out a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
NousResearch/hermes-agent
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.