Name: yoprint
Rating: 60 (1 reviews)
Author: membranedev

yoprint

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

Quality

70%

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/yoprint/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 body is highly actionable with executable commands and a well-instrumented connection workflow, supported by clean section structure. Its main weakness is conciseness, with a few padded prose passages that could be trimmed.

Suggestions

Trim padded prose such as 'so you can focus on the integration logic rather than auth plumbing' and the generic YoPrint introductory paragraph to improve token efficiency.

Resolve the dangling 'Step 2' reference by labeling the searching/running-actions sections as numbered steps so the connection→search→run sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and tables, but includes unnecessary prose such as the generic YoPrint intro ('It helps print shop owners manage orders...') and 'so you can focus on the integration logic rather than auth plumbing'. Not a 4 because several sentences could be trimmed without losing clarity.	3 / 5
Actionability	Provides copy-paste-ready executable commands throughout (install, login, connection ensure, action run with --input, request proxy) plus a concrete flags table covering the common cases. Fully matches the executable, copy-paste-ready anchor.	5 / 5
Workflow Clarity	The connection workflow is a clear sequence with explicit validation checkpoints (state polling, READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a feedback loop (re-poll after user action). Not a 5 because the dangling 'Step 2' reference leaves the connect→search→run flow slightly ambiguous.	4 / 5
Progressive Disclosure	No bundle files exist; the single document is well-organized with clear section headers and easy navigation. Not a 5 because all reference-style content (entity list, proxy flag table) is inlined rather than split into one-level-deep reference files, leaving minor organization gaps.	4 / 5
	Total	16 / 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 is well-structured with explicit what/when guidance and a clearly distinct niche, but its action verbs and trigger phrases are generic. Tightening specificity and adding entity-level synonyms would raise the weaker dimensions.

Suggestions

Replace generic verbs ('Manage data, records') with concrete YoPrint actions such as 'create orders, manage customers, generate invoices and estimates' to improve specificity.

Expand the trigger clause with natural synonyms, e.g. 'Use when the user wants to manage YoPrint orders, customers, estimates, invoices, or production workflows', so it matches how users actually ask.

Dimension	Reasoning	Score
Specificity	Names the domain ('YoPrint integration') and lists action phrases ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete YoPrint operations like creating orders or invoices. Not a 2 because there is more than a single minimal action, and not a 4 because the verbs lack specificity.	3 / 5
Completeness	Explicitly states what it does ('Manage data, records, and automate workflows') and when to use it ('Use when the user wants to interact with YoPrint data'). Not a 5 because the 'when' trigger is generic rather than enumerating concrete user scenarios.	4 / 5
Trigger Term Quality	Includes the core keyword 'YoPrint' and the phrase 'interact with YoPrint data', but misses natural variations and entity synonyms a user would say (orders, customers, estimates, invoices). Not a 4 because keyword coverage is limited to the app name and 'data'.	3 / 5
Distinctiveness Conflict Risk	Names a specific third-party product (YoPrint) with a distinct trigger ('interact with YoPrint data'), giving it a clear niche with minimal overlap risk against other skills. Clearly matches the distinct-niche anchor.	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/yoprint/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.