Name: payhere
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

payhere

Payhere integration. Manage Organizations, Users. Use when the user wants to interact with Payhere data.

Quality

69%

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

Quality

Content

72%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 executable commands and good connection-state workflow checkpoints, and is reasonably concise. Its weaknesses are the absence of validation/confirmation steps for destructive payment operations and a total lack of progressive disclosure into bundle files.

Suggestions

Add a validation/confirmation checkpoint before destructive actions, e.g. 'Before running create-refund or cancel-subscription, confirm the target payment/subscription ID and amount with the user and re-check via get-payment/get-subscription.'

Move the Popular actions catalog and the proxy flag reference table into separate bundle files (e.g. references/actions.md, references/proxy.md) and link to them from SKILL.md so the overview stays lean.

Trim the promotional intro paragraph and 'auth plumbing' aside to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-driven with clear tables, but carries minor padding — the marketing-flavored intro ('streamline payment processing and invoicing... small businesses, freelancers, and entrepreneurs') and asides like 'so you can focus on the integration logic rather than auth plumbing' could be trimmed.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every stage (install, login, connection ensure/get, action list, action run, request) with clearly marked placeholders, plus a Popular actions table and a proxy flag table covering the common cases.	5 / 5
Workflow Clarity	The connection setup is a clear sequenced flow with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling feedback, but the skill drives destructive financial operations (create-refund, cancel-subscription) with no validation/confirmation guidance before running them — the destructive-operations cap holds this at 3.	3 / 5
Progressive Disclosure	The body is well-sectioned but everything is inlined in a single ~166-line file with no external references; the Popular actions catalog and proxy flag reference are API-reference material that could live in separate bundle files, and no references/scripts/assets bundle exists.	3 / 5
	Total	15 / 20 Passed

Description

66%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 answers both 'what' and 'when' and is distinct thanks to the named Payhere product, but its action list is thin and misaligned with the skill's actual capabilities. Trigger coverage relies on a single keyword and omits the natural payment-domain terms users would say.

Suggestions

Replace 'Manage Organizations, Users' with the skill's real capabilities, e.g. 'Manage payments, customers, subscriptions, plans, refunds, and payment links'.

Expand the 'Use when' clause with concrete trigger phrases: 'Use when the user wants to accept payments, create payment links, issue refunds, or manage customers and subscriptions in Payhere.'

Add the file/identifier terms users naturally mention (payment links, invoices, subscriptions) to broaden trigger-term coverage beyond the single word 'Payhere'.

Dimension	Reasoning	Score
Specificity	It names the domain ('Payhere integration') and two concrete entities ('Manage Organizations, Users'), but the verb 'Manage' is generic and coverage is far from comprehensive — the body reveals payments, customers, subscriptions, plans, refunds, and payment links that the description omits.	3 / 5
Completeness	It states both what ('Payhere integration. Manage Organizations, Users.') and when ('Use when the user wants to interact with Payhere data.'), so it clears the 'Use when' floor; the 'when' clause is present but generic rather than concrete.	4 / 5
Trigger Term Quality	The only natural keyword is 'Payhere' (repeated in 'Payhere integration' and 'interact with Payhere data'); it is missing the common terms users would actually say such as payments, invoices, customers, subscriptions, or payment links.	3 / 5
Distinctiveness Conflict Risk	'Payhere' is a specific named product, giving the skill a clear niche with distinct triggers and minimal risk of firing for the wrong skill.	5 / 5
	Total	15 / 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/payhere/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.