Name: u301
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

u301

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

Quality

65%

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/u301/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 delivers executable Membrane CLI guidance with a well-sequenced, validated connection flow, but is marred by a stray refusal line, an unrelated docs link, and some prose padding.

Suggestions

Delete the placeholder refusal line ('I don't have enough information to do that...') and the unrelated 'Official docs: https://support.usa.canon.com/' link; they add noise and signal an unfinished draft.

Trim explanatory prose that restates the commands (e.g., 'so you can focus on the integration logic rather than auth plumbing') to tighten the token budget.

Fix the dangling 'skip to Step 2' reference by labeling the action-search/run section as Step 2 so the workflow sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command reference, but it opens with a stray refusal line ('I don't have enough information to do that...') and an unrelated Canon support link, plus prose padding like 'so you can focus on the integration logic rather than auth plumbing' that restates what the commands already show.	3 / 5
Actionability	It provides concrete, copy-pasteable commands across the common cases (install, login, connection ensure/get, action list/run, request) with a flag table, fitting the anchor for mostly executable guidance with minor gaps (ID/intent placeholders).	4 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit validation checkpoints (polling --wait, READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR state checks and recovery), though 'skip to Step 2' references a Step 2 that is never labeled, leaving a minor sequencing gap.	4 / 5
Progressive Disclosure	No bundle files exist, so the single SKILL.md is evaluated on its own structure; it is well organized into clearly headed sections (Overview, Working with U301, Connecting, Searching, Popular actions, Proxy, Best practices), with only minor organization gaps like the thin overview bullet list and the stray opening line.	4 / 5
	Total	15 / 20 Passed

Description

62%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 answers both what and when in third person with a distinct U301 niche, but its action list is generic and trigger terms are narrow.

Suggestions

Replace generic verbs ('Manage data, records') with concrete actions (e.g., 'create, update, query, and delete U301 records; build and trigger U301 workflows') to raise specificity.

Broaden trigger terms with synonyms users would actually say (e.g., 'U301 records, U301 workflows, sync U301 data, U301 automation') beyond the single phrase 'interact with U301 data'.

Dimension	Reasoning	Score
Specificity	It names the domain ('U301 integration') and lists three actions ('Manage data, records, and automate workflows'), but the actions are generic ('manage data') rather than concrete, matching the anchor that names the domain with a few actions that are not comprehensive.	3 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with U301 data'), but the 'when' is a single trigger phrase rather than the multiple concrete triggers of a 5.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with U301 data' surfaces relevant keywords (U301, data) but offers few natural variations or synonyms, fitting the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	'U301 integration' is a clear niche tied to a specific app with a distinct trigger and low conflict risk, though the generic action verbs leave minor overlap with other data-management skills rather than the minimal risk of a 5.	4 / 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/u301/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.