Name: yoco
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

yoco

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

Quality

64%

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/yoco/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 well-structured, highly actionable guide to driving Yoco through the Membrane CLI, with a clear connection workflow that includes state-check feedback loops. Its main weaknesses are mild verbosity (a redundant intro and repeated action-list command) and a 'Popular actions' section that restates discovery rather than naming concrete actions.

Suggestions

Trim the introductory paragraph that explains what a POS/payment platform is, since Claude already knows this.

Make 'Popular actions' list concrete Yoco actions (e.g. Create Payment, Create Refund, List Settlements) with example `membrane action run` invocations instead of repeating the discovery command.

Add a brief validation note for financially significant operations (e.g. verify a payment/settlement id before issuing a refund).

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the intro paragraph restates what Yoco/POS is and the action-list command is repeated across 'Searching for actions' and 'Popular actions', so it could be tightened.	3 / 5
Actionability	It provides many concrete copy-paste commands (login, connection ensure, action list/run, request proxy) plus a flags table, but 'Popular actions' merely repeats the list command instead of showing real action IDs from the overview, leaving a minor gap.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based feedback loops (poll with --wait, handle CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR, re-poll after user action), with only minor validation gaps around running financially significant actions like refunds.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Authentication, Connecting, Searching, Running, Proxy, Best practices) with appropriately inline material for a CLI-wrapper skill; no external references are used, but none are strongly required, leaving only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

61%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 names the Yoco domain and includes an explicit 'Use when' trigger with strong distinctiveness, but its capability list is generic ('manage data, records, automate workflows') rather than concrete Yoco actions. Trigger-term coverage is limited to the brand name without the natural payment/refund vocabulary users would say.

Suggestions

Replace generic verbs with concrete Yoco actions, e.g. 'Create and list payments, issue refunds, and retrieve settlements and transactions.'

Expand trigger terms to include natural user phrases like 'Yoco payments, charges, refunds, settlements, or transactions'.

Tighten the 'Use when' clause to reference those specific Yoco operations rather than the vague 'interact with Yoco data'.

Dimension	Reasoning	Score
Specificity	It names the Yoco domain but the stated actions are generic ('Manage data, records, and automate workflows') rather than concrete Yoco operations like charges, payments, or refunds, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when the user wants to interact with Yoco data' trigger are present; the 'what' is generic and the 'when' could be more specific, matching 'has both what and when; when could be more explicit'.	4 / 5
Trigger Term Quality	The core keyword 'Yoco' and phrase 'interact with Yoco data' are present, but it lacks the natural variations a user would actually say (payments, charges, refunds, settlements), fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Yoco is a specific branded POS/payments platform, giving a clear niche with distinct brand-keyword triggers and minimal conflict risk with other skills.	5 / 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/yoco/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.