Name: upayments
Rating: 55.2 (1 reviews)
Author: membranedev

upayments

UPayments integration. Manage data, records, and automate workflows. Use when the user wants to interact with UPayments 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/upayments/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 highly actionable with concrete CLI commands and a reasonable connection-state workflow, but it carries some background/marketing padding, references an undefined "Step 2", and lacks validation checkpoints before destructive payment operations. Trimming the intro, fixing the step numbering, and adding a verify-before-run step would lift the weaker dimensions.

Suggestions

Remove the introductory "UPayments is a payment processing platform..." paragraph and marketing phrases; assume Claude knows the platform context.

Define or relabel the "Step 2" target referenced in the connection flow (e.g. add explicit "Step 1 / Step 2" headers) so the skip instruction resolves.

Add a validation/verification checkpoint before running payment actions (e.g. confirm the action and amount with the user, or dry-run/inspect the outputSchema) to satisfy the destructive-operations feedback-loop requirement.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command reference, but the opening paragraph ("UPayments is a payment processing platform... typically used by e-commerce businesses, SaaS companies") and phrases like "so you can focus on the integration logic rather than auth plumbing" and "burn less tokens" are unnecessary explanation/marketing that could be trimmed, fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	The body is packed with copy-paste-ready, executable commands (npm install, membrane login, connection ensure, connection get --wait, action list/run, request) plus a flags table, covering the common cases with concrete placeholders explained, matching the fully-executable anchor.	5 / 5
Workflow Clarity	There is a clear sequenced flow with state-checking and a poll/retry feedback loop for CLIENT_ACTION_REQUIRED, but the referenced "Step 2" is never defined, and because running UPayments actions is destructive/financial yet no validation or verification step precedes execution, the destructive-operations cap holds at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-organized into clear sections (Overview, Authentication, Connecting, Searching, Popular actions, Best practices) with no nested references, fitting the good-structure anchor; minor gaps (the thin, partly-redundant "Popular actions" section) keep it just below the cleanly-split 5.	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 pairs a what and a when and anchors on a distinct named platform, but its capability language is generic and its trigger terms lack natural synonyms. Tightening the action list to concrete UPayments operations and adding payment/transaction/invoice keywords would raise specificity and trigger quality.

Suggestions

Replace generic verbs with concrete UPayments capabilities, e.g. "Create and track payments, manage invoices and subscriptions, and configure tax rates."

Expand the trigger clause with natural user phrases: "Use when the user wants to process payments, issue invoices, manage subscriptions, or query UPayments transactions."

Keep third-person imperative voice (currently correct) while making the "what" as concrete as the "when".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain and three actions, but all are generic abstractions rather than concrete capabilities (compare "Processes PDF files"), so it sits at the domain-named-but-generic level rather than the concrete-actions level.	2 / 5
Completeness	Both a "what" (UPayments integration; manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with UPayments data") are present, but the "when" is generic and the "what" is vague, so it lands at the both-present-but-could-be-more-specific level rather than the concrete-trigger-phrase level.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with UPayments data" surfaces the keyword "UPayments" but omits natural synonyms users would say (payments, transactions, invoices, subscriptions), matching the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific platform "UPayments" gives a clear niche with low conflict risk, but the generic action phrasing (manage data, automate workflows) leaves minor overlap with other data-handling skills, fitting the mostly-distinct anchor rather than the clear-distinct-triggers anchor.	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/upayments/SKILL.md
Commit: f484c82

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