Name: openpayd
Rating: 58.4 (1 reviews)
Author: membranedev

openpayd

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

Quality

67%

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/openpayd/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 executable Membrane CLI commands and a reasonable connection workflow, but it is padded in places, has inconsistent step numbering, and lacks validation checkpoints for destructive payment actions or proxy calls.

Suggestions

Add an explicit verification step after running actions and proxy requests (e.g. check the response status/error field and confirm the operation succeeded before proceeding), since payments and proxy mutations are destructive.

Fix the step numbering by labeling 'Step 1a/1b' and 'Step 2' consistently, or remove the dangling 'Step 2' / '1b' references.

Trim explanatory prose such as the OpenPayd intro paragraph and the 'burn less tokens' best-practice line, and de-duplicate the action-list command that appears in both 'Searching for actions' and 'Popular actions'.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands but includes padded explanation ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection...') and a duplicated action-list command across 'Searching for actions' and 'Popular actions', fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'; not a 4 because the intro and best-practices prose could be noticeably trimmed.	3 / 5
Actionability	It provides copy-paste-ready, executable commands for the common cases (install, login, connection ensure, action list/run with --input JSON, request proxy) plus a complete flag table, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The install→authenticate→connect→search→run→proxy sequence exists with state-based checkpoints and a poll-after-action feedback loop, but step numbering is inconsistent ('skip to Step 2' and '1b' with no labeled Step 2 / 1a) and there is no validation/verification step after running potentially destructive payment actions or proxy POST/PUT/DELETE calls, which caps the score at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	Content is organized into clear, navigable sections with the operational detail appropriately inline for a CLI integration skill; it is not a 5 because no reference files exist at all and some detailed reference material (the full proxy flag table, clientAction field reference) is inlined that could be split out, and not a 3 because the sectioning is genuinely good rather than poorly organized.	4 / 5
	Total	15 / 20 Passed

Description

66%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-statement with an explicit 'Use when' trigger and leverages a distinct brand name, but its capability wording ('Manage data, records, and automate workflows') is generic and omits the natural payment-domain keywords users would actually say.

Suggestions

Replace generic verbs with concrete OpenPayd operations, e.g. 'Send and receive payments, list transactions, manage accounts and balances'.

Add natural trigger keywords users would say, such as 'payments', 'transactions', 'transfers', or 'OpenPayd accounts'.

Sharpen the 'when' clause with concrete triggers, e.g. 'Use when the user wants to send payments, check balances, or query OpenPayd transactions.'

Dimension	Reasoning	Score
Specificity	Names the OpenPayd domain and lists a few action categories ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete payment-specific operations, fitting the 'names domain and 1-2 concrete actions, not comprehensive' anchor; not a 2 because more than a single minimal action is named, not a 4 because no specific concrete operations (e.g. send payments, list transactions) are enumerated.	3 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with OpenPayd data') are present, so it clears the missing-trigger cap of 3; it stays at 4 rather than 5 because the 'when' is generic and lacks concrete trigger phrases like payments or transactions.	4 / 5
Trigger Term Quality	The natural keyword 'OpenPayd' and 'OpenPayd data' appear, but common payment-domain terms a user would actually say (payments, transactions, transfers, accounts) are absent, matching the 'some relevant keywords but missing common variations or synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	The brand-specific 'OpenPayd' niche with a distinct 'interact with OpenPayd data' trigger gives it a clear niche with minimal conflict risk against other skills, matching the top anchor.	5 / 5
	Total	15 / 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/openpayd/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.