Name: yuja
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

yuja

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

Quality

59%

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/yuja/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 body is a strong, executable guide to driving YuJa through the Membrane CLI, with good command coverage and a well-sequenced connection flow, but it pads with a concept intro, leaves a destructive proxy path unvalidated, and has minor structural gaps.

Suggestions

Trim the opening "YuJa is a video platform..." paragraph and the "so you can focus on the integration logic" editorializing; assume Claude knows the platform basics.

Add a validation/verification checkpoint to the proxy section (e.g., GET before mutating, confirm with the user before DELETE/PUT) so destructive operations are not uncapped.

Fill in one concrete end-to-end example (a real intent query + actionId + --input) and label the referenced "Step 2" to close the workflow gaps.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight command references, but includes unnecessary explanation Claude does not need (the opening "YuJa is a video platform used primarily by educational institutions..." paragraph and editorializing like "so you can focus on the integration logic rather than auth plumbing"), matching the "mostly efficient but includes some unnecessary explanation" anchor.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run with --input, request proxy with a flag table), matching the level-4 anchor; it stops short of 5 because examples use placeholders (CONNECTION_ID, <actionId>) without a concrete filled-in YuJa intent example.	4 / 5
Workflow Clarity	The connection flow is well sequenced with state checks and a re-poll feedback loop, but the proxy section enables destructive methods (DELETE, PUT) with no validation/verification guidance, and the referenced "Step 2" is never labeled — the destructive-operation-without-validation cap holds this at 3.	3 / 5
Progressive Disclosure	Content is organized into clear, well-placed sections (Overview, Install, Auth, Connecting, Searching, Running, Proxy, Best practices) with no nested references, matching the level-4 "good structure, minor organization gaps" anchor; it does not reach 5 because no deeper reference files exist and some sections ("Popular actions") are thin.	4 / 5
	Total	14 / 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 cleanly names the YuJa niche and includes an explicit Use-when trigger, but its capability verbs are generic (manage, automate) and it omits the concrete domain terms (videos, lectures, courses) users would naturally say.

Suggestions

Replace generic verbs with concrete YuJa actions, e.g. "search and manage YuJa videos, recordings, courses, and user records".

Expand the trigger to cover natural terms users say: "Use when the user wants to manage YuJa videos, lectures, recordings, courses, or users."

Mention key resource types (media, live streams, gradebook, LTI) to sharpen distinctiveness from generic data-integration skills.

Dimension	Reasoning	Score
Specificity	The description names the YuJa domain plus a few activities ("Manage data, records, and automate workflows"), but the actions are generic and abstract rather than concrete, matching the "names the domain but actions are minimal or generic" anchor better than the level-3 anchor which requires concrete actions.	2 / 5
Completeness	It states both what ("YuJa integration. Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with YuJa data"), matching the level-4 anchor where both are present but the when could be more specific; it is not capped at 3 because a Use-when clause is present.	4 / 5
Trigger Term Quality	It includes the primary natural keyword "YuJa" and the phrase "interact with YuJa data", but misses common synonyms and concrete terms users would actually say (videos, lectures, recordings, courses), so it sits at the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	"YuJa integration" is a clear, named product niche with minimal conflict risk, but the generic trailing phrase ("manage data, records, workflows") leaves minor overlap risk with other data-integration skills, placing it just below the level-5 anchor.	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/yuja/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.