CtrlK
BlogDocsLog inGet started
Tessl Logo

yuki

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

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/yuki/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is an efficient, action-oriented integration guide with a well-structured connection workflow and explicit state-check checkpoints. Its main gaps are the lack of a complete worked example and missing validation/error-recovery guidance on the action-running side.

Suggestions

Add a brief end-to-end worked example that connects to Yuki, searches for an action by intent, and runs it with a concrete input, so the common case is copy-paste ready.

Add validation/error-recovery guidance for running actions and proxy requests (e.g. how to inspect a non-READY state, retry on error, or handle CONFIGURATION_ERROR), capping workflow clarity above 4.

Either explain or remove the cryptic "Yuki Overview" bullets (Task/Subtask/Project/User/Tag) so every section earns its place.

DimensionReasoningScore

Conciseness

The body is mostly lean and command-focused, explaining only Membrane-specific state behavior Claude would not already know; minor trimmable sections like the cryptic "Yuki Overview" bullets and the intro line keep it just below the lean-and-efficient anchor.

4 / 5

Actionability

It provides many concrete, executable commands (connection ensure, action list/run, proxy with a flag table) with clear placeholders, matching the mostly-executable anchor; it falls short of 5 because there is no complete end-to-end worked example tying the steps together.

4 / 5

Workflow Clarity

The connection flow is clearly sequenced with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-after-action feedback loop, but the action-running side has no validation or error-recovery steps, fitting the clear-sequence-with-minor-gaps anchor.

4 / 5

Progressive Disclosure

With no bundle files present, the single SKILL.md is well-organized into clearly labeled sections and includes one clearly signaled external reference (the official docs URL); minor organization gaps (e.g. the unexplained overview bullets) keep it at the good-structure anchor rather than 5.

4 / 5

Total

16

/

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 is brand-specific and includes an explicit "Use when" trigger, but its capability verbs are generic and its keyword coverage lacks synonyms. It is solid but could be sharpened with more concrete actions and richer trigger terms.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Yuki operations such as "search and update customer inquiries, manage projects and tags, run bulk record actions".

Add natural trigger synonyms and phrases users would actually say, e.g. "Use when the user mentions Yuki, customer support tickets, or wants to query/update Yuki records."

Make the "when" clause more specific by naming the contexts that should activate this skill (e.g. handling customer inquiries across channels).

DimensionReasoningScore

Specificity

The description names the Yuki domain and lists several actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete operations, matching the anchor for naming a domain with 1-2 actions that are not comprehensive.

3 / 5

Completeness

It provides both a "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Yuki data"), matching the anchor where both are present but the "when" could be more specific; the "Use when" clause means it is not capped at 3.

4 / 5

Trigger Term Quality

The brand name "Yuki" is the natural trigger and is present, but the surrounding keywords ("data", "records", "workflows") are generic with no synonyms or common variations, fitting the anchor for some relevant keywords but missing variations.

3 / 5

Distinctiveness Conflict Risk

The brand-specific "Yuki integration" and "interact with Yuki data" trigger give it a clear niche with minimal conflict risk, but the generic data/records language leaves minor overlap with related data skills, fitting the mostly-distinct anchor.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.