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

paymill

PAYMILL integration. Manage data, records, and automate workflows. Use when the user wants to interact with PAYMILL 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/paymill/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 skill body is highly actionable with concrete membrane commands and a clear connection workflow, but it is mildly verbose, repeats the action-list command, and omits validation steps for potentially destructive action/proxy operations.

Suggestions

Add a verification step after running actions or proxy requests, e.g. re-check the connection state or inspect the action output/error field before proceeding.

Remove the redundant "Popular actions" section or fold it into "Searching for actions" to eliminate the duplicated command and tighten the doc.

Trim the intro paragraph to the essential "now defunct" note rather than explaining what a payment gateway is.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph over-explains what PAYMILL is and the "Popular actions" section redundantly repeats the search command already shown under "Searching for actions".	3 / 5
Actionability	It provides copy-paste-ready membrane commands with concrete flags (--json, --wait, --input, -X, --query) covering install, auth, connection, action discovery, action runs, and proxying — fully executable guidance for the common cases.	5 / 5
Workflow Clarity	The connect-and-poll sequence has clear state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but running actions and proxy requests — which can be destructive (charges, refunds) — have no validation or verification step, capping this dimension.	3 / 5
Progressive Disclosure	Content is well-organized into clearly labeled sections with no nested references and no bundle files present, but at ~140 inline lines with a redundant "Popular actions" section it has minor organization gaps rather than ideal separation.	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 cleanly answers both what and when with a recognizable brand trigger, but its action language is generic rather than concrete and it lacks synonym coverage for trigger terms.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete PAYMILL operations, e.g. "Create and refund transactions, manage clients, subscriptions, offers, and payments."

Expand the trigger clause with natural user phrases and entity terms, e.g. "Use when the user wants to process PAYMILL payments, issue refunds, or manage subscriptions and clients."

Add a file-format or synonym cue (e.g. "PAYMILL API") to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ("PAYMILL integration") but the listed actions — "Manage data, records, and automate workflows" — are generic and abstract rather than concrete PAYMILL-specific operations, matching the anchor that names a domain with minimal/generic actions.	2 / 5
Completeness	It states both what ("PAYMILL integration. Manage data, records, and automate workflows") and when ("Use when the user wants to interact with PAYMILL data"), though the when clause is somewhat narrow rather than fully concrete.	4 / 5
Trigger Term Quality	The natural keyword "PAYMILL" appears and the trigger "interact with PAYMILL data" is recognizable, but coverage lacks common variations or synonyms, fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	PAYMILL is a distinct payment-gateway brand giving it a clear niche and low conflict risk, but the generic "manage data, records" wording leaves minor overlap risk with adjacent data 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/paymill/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.