Name: plisio
Rating: 66.4 (1 reviews)
Author: membranedev

plisio

Plisio integration. Manage Invoices, Payouts, Wallets, Transactions, Users. Use when the user wants to interact with Plisio data.

Quality

80%

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

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 well-structured, highly actionable CLI integration guide with strong validation in the connection-setup workflow. Its main weaknesses are minor padding in the intro, no verification step before destructive action execution, and an orphaned step reference.

Suggestions

Trim the opening paragraph about what Plisio is and who its users are; assume Claude knows the service or link the docs instead.

Add a verification/confirmation checkpoint before running destructive actions (e.g., echo the action and input and confirm with the user before `membrane action run` for payout/withdrawal intents).

Fix the dangling "skip to Step 2" reference by labeling the action-discovery section as Step 2 so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight executable CLI commands and a flag table, but the opening paragraph explaining what Plisio is and naming its primary users, plus phrases like "so you can focus on the integration logic rather than auth plumbing", are trimmable over-explanation; this fits the efficient-with-minor-padding 4 anchor above the mostly-efficient 3.	4 / 5
Actionability	Copy-paste-ready commands cover the common cases end to end (install, login, connection ensure, connection get --wait, action list --intent, action run with --input, request with a full proxy-flag table), matching the fully-executable 5 anchor.	5 / 5
Workflow Clarity	The connection workflow has explicit validation checkpoints and feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED polling, error-state handling, retry after user action), but there is no pre-execution verification for potentially destructive actions (payouts) and the "skip to Step 2" reference is orphaned, keeping it below 5.	4 / 5
Progressive Disclosure	The single-file skill is well-organized with clear ##/### headers and appropriately points to the official Plisio docs; with no bundle files and all content inline, structure is good but there is no internal one-level-deep reference split, fitting the 4 anchor rather than the reference-rich 5.	4 / 5
	Total	17 / 20 Passed

Description

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

A clear, branded description that names Plisio and several concrete resources with an explicit 'Use when' clause. It is distinctive and complete, though the trigger phrasing and action verbs could be more concrete.

Suggestions

Replace the generic verb "Manage" with distinct concrete actions (e.g., "Create and track invoices, send payouts, query wallet balances").

Expand the trigger clause with concrete user phrasings (e.g., "Use when the user wants to create an invoice, send a crypto payout, or check a Plisio wallet/transaction").

Dimension	Reasoning	Score
Specificity	"Manage Invoices, Payouts, Wallets, Transactions, Users" lists several concrete Plisio resources, giving a clear picture of scope; the single generic verb "Manage" is a minor gap versus distinct concrete actions, so it sits at 4 rather than 5 and above the 1-2-action anchor at 3.	4 / 5
Completeness	It states both the what ("Manage Invoices, Payouts, Wallets, Transactions, Users") and an explicit when ("Use when the user wants to interact with Plisio data"); the when is present but could be more specific with concrete triggers, matching the 4 anchor rather than the fully explicit 5.	4 / 5
Trigger Term Quality	"Plisio" plus resource nouns ("Invoices, Payouts, Wallets, Transactions, Users") give good natural keyword coverage a user would say; the trigger clause "Use when the user wants to interact with Plisio data" is generic and omits concrete phrasings like 'send a payout' or 'create an invoice', keeping it just below 5.	4 / 5
Distinctiveness Conflict Risk	"Plisio integration" names a specific branded crypto payment gateway with unique triggers, giving a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	17 / 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/plisio/SKILL.md
Commit: f484c82

Reviewed: 10 hours 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.