Name: yotpo-loyalty-referrals
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

yotpo-loyalty-referrals

Yotpo - Loyalty & Referrals integration. Manage data, records, and automate workflows. Use when the user wants to interact with Yotpo - Loyalty & Referrals data.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/yotpo-loyalty-referrals/SKILL.md

Quality

Content

61%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 a practical, command-driven guide with a strong, state-aware connection workflow and a useful proxy-options table. Its main gaps are some conceptual padding, a broken "Step 2" cross-reference, and the absence of validation/verification steps for potentially destructive action and proxy operations.

Suggestions

Add a verification step after running actions or proxy requests (e.g. re-fetch the affected record or check the response `output`/status before reporting success) to lift the workflow_clarity cap.

Fix the broken navigation: the body references "skip to Step 2" but no Step 2 is labeled — either number the full sequence (1 install → 2 connect → 3 search/run) or remove the dangling reference.

Trim the Yotpo concept-intro paragraph and editorial asides ("focus on the integration logic rather than auth plumbing") to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but includes unnecessary padding such as the Yotpo concept intro paragraph and phrases like "so you can focus on the integration logic rather than auth plumbing", which could be trimmed.	3 / 5
Actionability	It provides concrete, executable CLI commands (install, login, connection ensure, action list/run, request) with flags documented, but every example uses placeholders (CONNECTION_ID, <actionId>, /path/to/endpoint) with no fully concrete worked example, leaving minor gaps.	4 / 5
Workflow Clarity	The connection flow is well-sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll loop, but running actions and proxy requests (potentially destructive POST/PUT/DELETE) lack verification steps, which caps this at 3; the "skip to Step 2" reference also points to a non-existent Step 2.	3 / 5
Progressive Disclosure	No bundle files exist and all content is inline, but the body is organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices); at ~140 lines it is reasonably placed with only minor organization gaps.	4 / 5
	Total	14 / 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 answers both what the skill does and when to use it, with an explicit "Use when" clause and a distinct product-named trigger. Its weakness is generic action verbs ("manage data, records, automate workflows") and a thin set of trigger synonyms, which limit specificity and trigger-term quality.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Create and manage loyalty campaigns, referral programs, rewards, and VIP tiers; query customers and orders."

Add natural trigger synonyms users would say, e.g. "Use when the user wants to manage loyalty points, referral rewards, VIP tiers, or customer/ order data in Yotpo."

Keep the explicit "Use when..." clause but tie it to concrete scenarios (creating campaigns, looking up rewards, syncing orders) rather than "interact with data".

Dimension	Reasoning	Score
Specificity	It names the domain ("Yotpo - Loyalty & Referrals integration") but the actions — "Manage data, records, and automate workflows" — are minimal and generic, matching the anchor for naming the domain with generic actions rather than listing concrete capabilities.	2 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "Use when..." trigger are present, satisfying the no-cap rule; the "when" clause is generic and could be more specific, fitting the anchor where both exist but the when is less explicit.	4 / 5
Trigger Term Quality	The only natural keyword is the product name itself ("interact with Yotpo - Loyalty & Referrals data"); it omits common variations a user would actually say such as "loyalty program", "referral program", "rewards", "points", or "VIP tiers".	3 / 5
Distinctiveness Conflict Risk	The trigger is a specific, named product ("Yotpo - Loyalty & Referrals") giving it a clear niche with distinct 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/yotpo-loyalty-referrals/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.