CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

yao-process

Yao process execution expert. ALWAYS invoke this skill when the user needs to call a Yao process, query data models, run scripts, or check process permissions. Do not call processes without checking this skill first.

69

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

An exemplary lean, self-contained skill body: executable commands, parameter tables, and a permission-check-first workflow with error semantics, all in under 50 lines. The only gap is the absence of an explicit verify/retry step after process execution, which keeps workflow clarity just below full marks.

DimensionReasoningScore

Conciseness

The ~45-line body explains nothing Claude already knows and pads nothing — the opener is "Two tools for Yao process execution, called via bash." followed immediately by executable examples and parameter tables. Every token earns its place, matching the lean anchor 5.

5 / 5

Actionability

Fully copy-paste-ready bash commands with realistic JSON payloads cover the common cases (list all allowed rules, check a specific process, call a process with positional args), backed by required/optional parameter tables. Matches the fully-executable anchor 5.

5 / 5

Workflow Clarity

A clear 3-step sequence (process_allowed → doc_inspect → process_call) with a pre-flight permission check and an error-recovery hint ("A 403 error means the process is not in the allowed list"). Not 5 because there is no explicit post-call verification or retry loop after execution — a minor validation gap matching anchor 4.

4 / 5

Progressive Disclosure

Under 50 lines with no external references needed, and the content is cleanly organized into tool sections, a workflow, and guidelines — per the simple-skill exception this earns a 5. The one cross-skill reference ("doc_inspect (from yao-doc skill)") is clearly signaled, one level deep.

5 / 5

Total

19

/

20

Passed

Description

75%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.

A solid description with an excellent, explicit 'Use when'-style trigger clause and concrete enumerated actions. Its weaknesses are the title-style opening that leaves the 'what' implicit, and a couple of overly broad trigger terms ("run scripts", "query data models") that invite conflicts with unrelated skills.

Suggestions

Replace the title-style opening "Yao process execution expert" with a verb-led capability statement (e.g. "Executes Yao processes by name and checks which processes are permitted") so the 'what' is explicit, not inferred.

Tighten the trigger list by qualifying the generic terms — e.g. "run Yao scripts" instead of "run scripts" — to reduce conflict risk with general script-execution or data-query skills.

The trailing guard "Do not call processes without checking this skill first" duplicates the 'ALWAYS invoke' clause; merging them would cut padding without losing the trigger.

DimensionReasoningScore

Specificity

Lists four concrete actions ("call a Yao process, query data models, run scripts, or check process permissions"), matching the 'several specific actions; minor gaps' anchor. Not 5 because the opening "Yao process execution expert" is a title rather than a full concrete capability statement, leaving minor coverage gaps.

4 / 5

Completeness

The 'when' is explicit and strong ("ALWAYS invoke this skill when the user needs to call a Yao process, query data models, run scripts, or check process permissions"), but the 'what' rests on the title phrase "Yao process execution expert" instead of being stated as actions. This sits between anchors 4 and 5 — the weakly stated 'what' prevents a 5 despite the exemplary 'when'.

4 / 5

Trigger Term Quality

"call a Yao process", "query data models", and "check process permissions" are natural phrases a user would say, but "run scripts" is generic and common variations/synonyms are absent. Good coverage with a few natural terms missing, so anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The "Yao process" and "process permissions" triggers define a clear niche, but the generic "run scripts" and "query data models" phrases create minor overlap risk with general script-execution or data-query skills. Mostly distinct with minor overlap, matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

YaoApp/yao

Path

tools/skills/yao-process/SKILL.md

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.