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

Blog Docs Log in Get started

gopay

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

Quality

62%

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

Quality

Content

67%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 a solid, command-driven integration guide with a clear connection workflow and real validation/feedback loops. Its main weaknesses are mild verbosity and duplicated command examples, plus inconsistent step numbering that slightly muddies the workflow.

Suggestions

De-duplicate the action-list command: keep one canonical `membrane action list` example and remove the near-identical `npx @membranehq/cli@latest action list` line in 'Popular actions'.

Fix the step numbering — add a '1a' heading or relabel so the referenced 'Step 2' is an explicit, labeled step.

Trim concept explanations Claude already infers (the 'PayPal of Indonesia' framing and 'auth plumbing' commentary) to recover tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete commands, but it carries some unnecessary explanation (the GoPay 'PayPal of Indonesia' intro, the 'auth plumbing' commentary) and duplicates the action-list command across 'Searching for actions' and 'Popular actions', so it fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than a 4.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy with a full flag table — mostly executable guidance — but relies on placeholders (CONNECTION_ID, <actionId>, 'QUERY') with no worked end-to-end example, leaving the minor gaps that cap it at 4 rather than 5.	4 / 5
Workflow Clarity	The connect-to-GoPay flow has a clear sequence with explicit state validation (READY / BUILDING / CLIENT_ACTION_REQUIRED) and a poll-then-repoll feedback loop, but step numbering is inconsistent (a '1b' with no '1a', a referenced 'Step 2' that is never labeled), the minor gaps that fit anchor 4 rather than 5.	4 / 5
Progressive Disclosure	As a single self-contained file with no bundle files, it is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with content appropriately placed; it is not a 5 only because the detailed clientAction state machine and proxy flag table could live in one-level-deep reference files for a >50-line skill.	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 correctly pairs a 'what' with an explicit 'Use when' trigger and anchors on a distinct named product, but its actions are generic ('manage data, automate workflows') rather than concrete GoPay operations. Tightening the verb list and adding payment/e-wallet trigger synonyms would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete GoPay capabilities (e.g. 'query transactions, manage merchants, initiate payments') to raise specificity.

Add natural user synonyms to the trigger clause such as 'e-wallet', 'payments', or 'Indonesian payment' so it matches how users actually ask.

Make the 'Use when' clause more specific, e.g. 'Use when the user wants to query GoPay transactions or manage merchant accounts.'

Dimension	Reasoning	Score
Specificity	Names the domain ('GoPay integration') but the actions — 'Manage data, records, and automate workflows' — are generic verbs with no concrete GoPay-specific operations, matching the 'names domain but actions are minimal or generic' anchor rather than the 1-2 concrete actions needed for a 3.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with GoPay data'), matching the anchor where both are present but the 'when' could be more specific; not a 5 because neither side is concretely spelled out.	4 / 5
Trigger Term Quality	'GoPay' and 'interact with GoPay data' provide the core natural keyword a user would say, but common synonyms a user might actually utter (e-wallet, payments, Indonesian payment) are missing, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'GoPay' is a specific named product giving it a clear niche with low conflict risk, but the generic 'data/records/workflows' framing leaves minor overlap with broad data-integration skills, so it sits at 4 rather than 5.	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/gopay/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.