Name: yodiz
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

yodiz

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

Quality

62%

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/yodiz/SKILL.md

Quality

Content

71%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 CLI commands and a clear connection-state workflow, though it carries some generic explanatory padding and inlines reference-style material rather than splitting it into bundle files.

Suggestions

Trim generic intro/context ('Yodiz is an agile project management... combines features of Jira, Trello') that Claude already knows.

Move the proxy flag table and action-discovery details into a references/ file referenced one level deep from SKILL.md.

Add an explicit verification step after running an action (e.g. check the `output`/error fields) to close the workflow loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with ready-to-run CLI commands, but includes some padded explanation Claude could infer (e.g. 'Yodiz is an agile project management and issue tracking tool... combines features of Jira, Trello' and restating Membrane's auth behavior).	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connecting, searching, running, and proxying, with parameter flags and JSON examples covering the common cases.	5 / 5
Workflow Clarity	The connection flow is well sequenced with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and explicit polling, but lacks a final verification step that the action actually succeeded against Yodiz.	4 / 5
Progressive Disclosure	There are no bundle reference files and the structure is sectioned, but content that could live in a separate reference (the full proxy flag table, the popular-actions catalog) is inlined with no one-level-deep references to point to.	3 / 5
	Total	15 / 20 Passed

Description

53%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 names the target app and includes a use-when clause, but the capability language ('Manage data, records, and automate workflows') is generic and omits the natural agile/issue-tracking terms that would help it trigger reliably.

Suggestions

Replace abstract verbs with concrete Yodiz capabilities, e.g. 'Manage sprints, track issues and bugs, and work on user stories and epics in Yodiz.'

Expand trigger terms to natural phrasings users say: 'Use when the user wants to manage Yodiz issues, sprints, backlogs, epics, or agile project data.'

Make the 'what' explicit so it reads as agile/issue tracking rather than generic data management.

Dimension	Reasoning	Score
Specificity	It names the domain (Yodiz) and a couple of generic actions ('Manage data, records, and automate workflows') but these are abstract rather than concrete capabilities like 'track bugs' or 'plan sprints'.	3 / 5
Completeness	There is a clear 'when' clause, but the 'what' is generic ('Manage data, records, and automate workflows') and does not clearly convey what Yodiz actually does; the missing-but-weak-what lands at the 3 anchor (clear what but weak/missing when is symmetric here).	3 / 5
Trigger Term Quality	The trigger 'when the user wants to interact with Yodiz data' is a natural phrasing, but it lacks synonyms or natural variations a user might say (e.g. 'issues', 'sprints', 'backlog', 'agile project management').	3 / 5
Distinctiveness Conflict Risk	Naming the specific app 'Yodiz' gives it a clear niche with minimal conflict risk against other skills; the generic verb phrasing prevents a perfect 5.	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/yodiz/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.