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

Blog Docs Log in Get started

wepay

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

Quality

68%

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

Quality

Content

75%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 clear state-driven connection workflow including feedback loops. Its main weaknesses are an unnecessary concept-explaining intro and slightly dangling step references.

Suggestions

Trim the opening WePay overview paragraph and padded phrases (e.g. "so you can focus on the integration logic") to assume Claude's knowledge of what WePay is.

Replace dangling "skip to Step 2" references with explicit, numbered step labels (e.g. "Step 1a", "Step 2: Search for actions") so the workflow sequence is unambiguous.

Consider moving the proxy flags table and the detailed clientAction state machine into a separate reference file to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands, but the opening paragraph explains what WePay is (a concept Claude already knows) and includes padding phrases like "so you can focus on the integration logic rather than auth plumbing."	3 / 5
Actionability	Provides abundant copy-paste-ready `membrane` commands covering login, connection ensure/wait, action discovery, action execution, and proxy requests, plus a clear flags table.	5 / 5
Workflow Clarity	The connection workflow has explicit state checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and feedback loops (poll until ready, re-poll after action), but "skip to Step 2" references are slightly dangling without explicit step labels.	4 / 5
Progressive Disclosure	A single well-organized SKILL.md with clearly headed sections and no bundle files; content is reasonably scoped for a single-file guide, though the proxy flag table and detailed state machine could arguably split into separate references.	4 / 5
	Total	16 / 20 Passed

Description

62%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 the skill does and when to use it, anchored to a distinct WePay niche. Its main weakness is generic action verbs and missing concrete payment-domain trigger terms that users would naturally say.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete WePay capabilities such as payments, checkouts, refunds, preapprovals, and account withdrawals.

Expand the trigger clause to name natural user phrases, e.g. "Use when the user wants to process WePay payments, issue refunds, or manage checkouts and accounts."

Mention file-format or API synonyms where relevant to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the WePay domain plus several actions ("Manage data, records, and automate workflows"), but the actions are generic verbs rather than concrete WePay-specific operations like payments, checkouts, or refunds.	3 / 5
Completeness	Both a "what" ("WePay integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with WePay data.") are present, though the trigger could be more specific.	4 / 5
Trigger Term Quality	"WePay" and "interact with WePay data" are relevant keywords, but common natural terms a user would say (payments, checkouts, refunds, accounts) and synonyms/extensions are missing.	3 / 5
Distinctiveness Conflict Risk	"WePay integration" is a clear, specific niche with minimal overlap risk; the trigger is tied to WePay, though the phrasing "interact with WePay data" is somewhat generic.	4 / 5
	Total	14 / 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/wepay/SKILL.md
Commit: f484c82

Reviewed: 3 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.