Name: yapily
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

yapily

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

Quality

66%

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/yapily/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 body is highly actionable with copy-paste CLI commands and a well-structured connection workflow including polling feedback, though it stays concise with only light background padding. Its main weakness is the absence of validation/confirmation guidance for destructive action runs like payment initiation.

Suggestions

Add an explicit validation/confirmation checkpoint before destructive action runs (e.g. preview the action and confirm with the user before executing payment or write operations, then verify the response state).

Resolve the dangling 'Step 2' reference — the text says to skip to Step 2 but no Step 2 header exists — by labeling the 'Searching for actions' section as Step 2.

Trim the opening 'Yapily is an open banking platform...' background paragraph or fold it into the overview list, since Claude can infer general context and only Yapily-specific details add value.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands and a flag table, with only minor padding such as the opening background paragraph on what Yapily is, fitting the 'efficient; minor instances of over-explanation that could be trimmed' anchor.	4 / 5
Actionability	It provides copy-paste ready commands for install, login, connection ensure, action list, action run, and proxy requests with a complete options table, covering the common cases per the top anchor.	5 / 5
Workflow Clarity	The connection flow has a clear state-based sequence with polling feedback (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but there is no validation or confirmation checkpoint before running potentially destructive actions such as payments, so the destructive-operation cap applies.	3 / 5
Progressive Disclosure	As a single self-contained file with clear section headers and no nested references, it is well organized with only minor gaps (e.g. the thin Popular actions section and no separate action-catalog reference), matching the 'good structure; minor organization gaps' anchor.	4 / 5
	Total	16 / 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 leverages a distinctive brand name, but its capability phrasing is generic and its trigger terms lack synonyms or concrete use cases. Tightening the action list and trigger phrasing would raise it toward the top anchors.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Yapily capabilities such as initiating payments, retrieving account information, and verifying identities.

Expand the 'Use when' clause with concrete trigger phrases users would actually say, e.g. 'when the user wants to initiate payments, retrieve account balances, or list transactions via Yapily'.

Add natural synonyms/variants (e.g. 'open banking', 'bank account data', 'payment consent') to broaden trigger coverage beyond the single brand term.

Dimension	Reasoning	Score
Specificity	The description names the Yapily domain but its actions ('Manage data, records, and automate workflows') are generic rather than concrete like payments or account retrieval, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	Both a 'what' ('Yapily integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Yapily data') are present, but the 'when' is generic rather than tied to concrete triggers, matching the score-4 anchor.	4 / 5
Trigger Term Quality	It surfaces 'Yapily' and 'Yapily data' as relevant keywords but offers no synonyms or common variations, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The Yapily brand name gives it a clear niche with low conflict risk, though the generic 'interact with Yapily data' trigger leaves minor overlap with other open-banking/fintech skills, fitting 'mostly distinct; minor overlap risk'.	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/yapily/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.