Name: paystand
Rating: 61.6 (1 reviews)
Author: membranedev

paystand

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

Quality

72%

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/paystand/SKILL.md

Quality

Content

82%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.

A strong, action-oriented skill body with concrete executable commands and a genuine validate-and-retry loop for connection readiness. Main weaknesses are mild verbosity in the intro/rationale prose and inconsistent step numbering.

Suggestions

Trim the opening marketing paragraph ('B2B payments platform built on blockchain…') and rationale sentences to keep only what Claude needs to act.

Fix step numbering so the connection flow reads as a coherent ordered list (1, 2, 3) rather than '1b' and 'Step 2' with no '1'.

Consider moving the proxy flags table and action inputSchema/outputSchema details into a references/ file to slim the main body.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands and minimal padding, but the opening paragraph explaining Paystand as a 'B2B payments platform built on blockchain' and rationale sentences like 'This is the fastest way to get a connection' are over-explanation that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action run with JSON params) plus a complete proxy-flags table covering the common cases.	5 / 5
Workflow Clarity	Clear install→auth→connect→search→run sequence with an explicit feedback loop on connection readiness (poll --wait, branch on state, re-poll after action), but step numbering is inconsistent ('1b', 'Step 2' with no '1').	4 / 5
Progressive Disclosure	No bundle files exist so the body is self-contained; it is well-sectioned with clear headers, though at ~145 lines some reference-style inline content (full proxy flag table, action schema fields) could warrant a separate reference file in a larger skill.	4 / 5
	Total	17 / 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 correctly answers both what and when and is anchored to a distinct named product, but its action language and trigger keywords are generic rather than reflecting the concrete payments-domain terms the body actually covers.

Suggestions

Replace generic verbs with concrete Paystand actions, e.g. 'Create and track payments, manage transactions and ledger accounts, process refunds and payouts, and automate AR/AP workflows.'

Add natural finance trigger terms a user would actually say, e.g. 'Use when the user wants to work with Paystand payments, transactions, payouts, refunds, or ledger accounts.'

Keep third person ('Manages', 'Automates') as now; just swap the generic nouns for payment-specific ones.

Dimension	Reasoning	Score
Specificity	'Manage data, records, and automate workflows' names the domain and a couple of actions, but they are generic rather than concrete Paystand actions like payments, transactions, payouts, or refunds that the body enumerates.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Paystand data') are present; the 'what' is generic which keeps it off the top level.	4 / 5
Trigger Term Quality	'Paystand' is a genuinely natural keyword, but coverage is thin with no synonyms or the natural finance/accounting terms (payments, AR/AP, invoices) a user would actually say.	3 / 5
Distinctiveness Conflict Risk	'Paystand integration' is a clearly named niche with minimal conflict risk, though the generic 'manage data, records, automate workflows' boilerplate could apply to many integration skills.	4 / 5
	Total	14 / 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/paystand/SKILL.md
Commit: f484c82

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