Name: yespo
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

yespo

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

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/yespo/SKILL.md

Quality

Content

82%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 strong, state-aware connection workflow including feedback loops. Its main weaknesses are a small amount of marketing padding and slightly loose section sequencing rather than structural problems.

Suggestions

Trim the introductory marketing paragraph to a one-line platform identity, since Claude does not need the e-commerce growth rationale.

Reconcile the duplicate action-discovery sections ("Searching for actions" and "Popular actions") and fix the dangling "Step 2" reference so the install→login→connect→search→run sequence reads as one numbered flow.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command examples with minimal prose, though the marketing-flavored intro paragraph ("designed to help e-commerce businesses grow...drive sales") and the filler line "Use action names and parameters as needed" are minor over-explanation that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands for the full flow (install, login, connection ensure, action list/run, request proxy) with a flag table and concrete parameter examples, covering the common cases executably.	5 / 5
Workflow Clarity	The connection workflow has explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) with a poll-again feedback loop, but the overall document flow is loosely sequenced (an unexplained "Step 2" reference, redundant "Popular actions" vs "Searching for actions" sections), leaving minor gaps.	4 / 5
Progressive Disclosure	Content is well-sectioned under clear headers in a single appropriately-scoped file with no nested references; the long feature inventory is inline but serves discovery, so structure is good with only minor organization gaps.	4 / 5
	Total	17 / 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 cleanly names the Yespo platform and includes an explicit "Use when" trigger, but its action verbs are generic and it omits the concrete task terms (email, SMS, campaigns) that users would naturally mention. It is distinct but only moderately specific.

Suggestions

Replace generic verbs ("Manage data, records") with concrete Yespo capabilities such as "send email and SMS campaigns, manage segments and orders, build automations".

Expand the "Use when" clause with concrete trigger phrases users actually say, e.g. "Use when the user wants to send Yespo email/SMS campaigns, manage contacts or segments, or query orders."

Dimension	Reasoning	Score
Specificity	Names the domain and a few actions ("Manage data, records, and automate workflows") but the verbs are generic ("manage") rather than concrete API operations, so it sits at the domain-plus-1-2-actions level rather than a comprehensive action list.	3 / 5
Completeness	Both "what" (Yespo integration; manage data, records, automate workflows) and "when" ("Use when the user wants to interact with Yespo data") are present, but the "when" clause is generic rather than listing concrete trigger phrases, capping it below 5.	4 / 5
Trigger Term Quality	The natural keyword "Yespo" is present and the "Use when the user wants to interact with Yespo data" clause gives a trigger, but the description omits the task terms users actually say (email, SMS, campaigns, segments, orders) that appear only in the body.	3 / 5
Distinctiveness Conflict Risk	"Yespo integration" names a specific branded platform with a distinct trigger ("interact with Yespo data"), giving it a clear niche with minimal overlap risk against other skills.	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/yespo/SKILL.md
Commit: f484c82

Reviewed: ~21 hours 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.