Name: securionpay
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

securionpay

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

Quality

66%

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

Quality

Content

75%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 copy-paste CLI commands and a well-sequenced connection workflow that includes state-check feedback loops, though it carries a promotional overview paragraph and some redundant examples that slightly undermine conciseness.

Suggestions

Remove or trim the opening marketing paragraph about what SecurionPay is and who uses it — Claude does not need that context to run the CLI.

Dedupe the `membrane action list --intent=QUERY` example that appears in both 'Searching for actions' and 'Popular actions'.

Fix the dangling 'Step 2' reference and the inconsistent '#### 1b' numbering so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but the opening promotional paragraph ('SecurionPay is a payment processing platform that focuses on security and fraud prevention... typically used by e-commerce businesses') and the duplicated `membrane action list --intent=QUERY` example across 'Searching for actions' and 'Popular actions' are unnecessary.	3 / 5
Actionability	It provides fully executable, copy-paste-ready bash commands across the whole flow — install, login (including headless), connection ensure, polling, action list/run with JSON input, and a proxy flags table — covering the common cases.	5 / 5
Workflow Clarity	The connect-to-run sequence is clear with explicit state-check feedback loops (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR and re-polling), but 'Step 2' is referenced without a matching numbered header and '#### 1b' numbering is inconsistent.	4 / 5
Progressive Disclosure	The single-file skill is well-organized with clear section headers and no nested references, and no bundle files exist; it stops short of a 5 only because some inlined material (the proxy flags table, the duplicated action-list block) could be tightened or split out.	4 / 5
	Total	16 / 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 includes an explicit 'Use when...' trigger and names the target product, but its capability list is generic ('manage data, records, automate workflows') and it omits the concrete payment-domain trigger terms users would naturally say.

Suggestions

Replace the generic action list with concrete SecurionPay operations, e.g. 'Create and capture charges, manage customers and cards, handle subscriptions, plans, payouts, and disputes'.

Add natural trigger terms a user would say, such as 'payments', 'charges', 'subscriptions', 'payouts', or 'chargebacks', alongside 'SecurionPay'.

Tighten the 'when' clause to reference those payment tasks rather than the abstract phrase 'interact with SecurionPay data'.

Dimension	Reasoning	Score
Specificity	It names the domain (SecurionPay) but the actions are minimal and generic — 'Manage data, records, and automate workflows' are abstract categories rather than concrete operations like 'create charges' or 'manage subscriptions'.	2 / 5
Completeness	It answers both 'what' ('SecurionPay integration. Manage data, records, and automate workflows') and 'when' with an explicit 'Use when the user wants to interact with SecurionPay data', though both could be more specific.	4 / 5
Trigger Term Quality	The only natural keyword is the product name 'SecurionPay' plus 'data'; it is missing the common payment-domain phrases a user would actually say (payments, charges, subscriptions, payouts, tokens).	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'SecurionPay' gives it a clear niche with minimal conflict risk, though it could still overlap with other generic payment-integration 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/securionpay/SKILL.md
Commit: f484c82

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