Name: paygreen
Rating: 52.8 (1 reviews)
Author: membranedev

paygreen

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

Quality

58%

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

Quality

Content

76%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 content is highly actionable with copy-paste-ready commands and a logical flow, and it stays lean without over-explaining basics. Its main gap is the absence of validation/verification checkpoints around potentially mutating workflow automation, which caps workflow clarity.

Suggestions

Add an explicit verify step before running mutating actions (e.g. 'Before running write actions, confirm the connection state is READY and dry-run with action list first').

Tighten the duplicated search guidance — the 'Popular actions' section restates the same action list command already shown under 'Searching for actions'.

Consider moving the proxy flag table and clientAction detail into a short reference so the connecting workflow reads as a tighter overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — it leads with executable CLI commands and flags and avoids explaining what PayGreen or a CLI is; minor over-explanation ('This is the fastest way to get a connection...', the 'Popular actions' section restating the search command) keeps it just below a 5.	4 / 5
Actionability	Nearly every step is given as a copy-pasteable command with flags and expected output fields described (e.g. connection ensure, action list/run, request proxy with its full flag table), matching 'Fully executable; copy-paste ready'.	5 / 5
Workflow Clarity	There is a clear install -> authenticate -> connect -> search/run sequence with polling states, but actions can mutate or automate PayGreen workflows with no explicit validation/verification checkpoint before running them, so the destructive/batch cap of 3 applies.	3 / 5
Progressive Disclosure	The body is well sectioned (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and stays at one level with no nested references; it is dense but coherent, and there are no external reference files to signal, leaving it just short of the score-5 'clear overview pointing to one-level references' anchor.	4 / 5
	Total	16 / 20 Passed

Description

41%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 anchors clearly to the PayGreen niche and includes an explicit 'Use when' trigger, but its actions are generic and the trigger vocabulary is thin, leaving it below the strongest examples. Specificity and trigger-term coverage are the weakest areas.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete PayGreen actions, e.g. 'Create and track transactions, manage merchant accounts, and automate payment workflows'.

Broaden the trigger phrase to match real user language, e.g. 'Use when the user wants to process payments, query transactions, or manage PayGreen merchants'.

Add a couple of synonyms/file markers users might say (payments, transactions, PayGreen API) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain (PayGreen) and a couple of generic verbs ('Manage data, records, and automate workflows') but no concrete PayGreen actions like creating transactions, managing merchants, or processing payments; closer to 'Names the domain but actions are minimal or generic' than the score-3 anchor's '1-2 concrete actions'.	2 / 5
Completeness	It states a clear 'what' ('Manage data, records, and automate workflows') and includes an explicit 'Use when the user wants to interact with PayGreen data' clause, but the 'what' is generic and the trigger guidance is shallow; the presence of a 'Use when...' clause justifies a 3 rather than 4.	3 / 5
Trigger Term Quality	Only one natural-ish phrase ('interact with PayGreen data') appears; it lacks the common phrasings or synonyms a user would actually say, matching 'One or two generic keywords; missing the natural phrases users say'.	2 / 5
Distinctiveness Conflict Risk	'PayGreen integration' is a clear, narrow niche tied to a specific platform, so it is unlikely to trigger for unrelated skills; only the generic verbs keep it from a 5.	4 / 5
	Total	11 / 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/paygreen/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.