Name: alternative-payments
Rating: 60 (1 reviews)
Author: membranedev

alternative-payments

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/alternative-payments/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.

The body is a tight, actionable guide built around concrete Membrane CLI commands with a clear connection workflow and state-based error handling. Its main weaknesses are minor verbosity and slight redundancy between the action-discovery sections.

Suggestions

Trim the opening background paragraph on what alternative payments is and motivational phrases ('burn less tokens', 'focus on integration logic') to respect token budget.

Add a brief verify/inspect step after running an action (e.g. check the `output` field for errors) to close the workflow validation gap.

Merge the redundant 'Searching for actions' and 'Popular actions' sections into a single action-discovery section.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with direct, executable commands, but includes minor trimmable padding such as the opening background paragraph on what alternative payments is and phrases like 'so you can focus on the integration logic rather than auth plumbing' and 'burn less tokens'.	4 / 5
Actionability	It provides copy-paste ready commands for every common case (install, login, connection ensure/get, action list/run, request) plus a concrete flag table, fully executable with clear placeholders for substitution.	5 / 5
Workflow Clarity	The install→auth→connect→search→run flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling logic, but action execution lacks an explicit verify-result checkpoint.	4 / 5
Progressive Disclosure	Content is organized into clear, well-signaled sections (Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references and no bundle files, though the 'Searching for actions' and 'Popular actions' sections are slightly redundant.	4 / 5
	Total	17 / 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 clearly names the target service and includes an explicit 'Use when' trigger, satisfying both the what and when. It is held back by generic action verbs and a lack of natural trigger-term variations that would aid discovery.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Create and track payments, manage payment methods, merchants, and reports'.

Add natural trigger phrases and synonyms users would say, e.g. 'Use when the user mentions alternative payment methods, bank transfers, e-wallets, or Adyen Alternative Payments data'.

Tie the 'Use when' clause to specific intents rather than the generic 'interact with ... data'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Alternative Payments integration') but its actions ('Manage data, records, and automate workflows') are generic and minimal rather than concrete capabilities, matching the score-2 anchor better than the more concrete score-3 examples.	2 / 5
Completeness	It states both what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with Alternative Payments data'), but the 'when' is fairly generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes a relevant keyword ('Alternative Payments') and a 'Use when... interact with Alternative Payments data' trigger, but misses natural variations or synonyms users might say (e.g. 'payments', 'bank transfers', 'e-wallets', 'Adyen').	3 / 5
Distinctiveness Conflict Risk	Naming the specific 'Alternative Payments' service gives it a clear niche with minimal conflict risk, though the generic 'manage data, records' phrasing leaves minor overlap with other data-management 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/alternative-payments/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.