CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

yao-agent

Agent management expert. ALWAYS invoke this skill when you need to list available agents, download or reference agent source code, deploy agent code to the host, or query the LLM connector matrix. Do not guess agent structures — use this skill first.

72

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, highly actionable reference: five tools each documented with executable commands, parameter tables, and explicit namespace/security constraints, capped by a concise guidelines section. The only improvement space is minor redundancy between the per-tool sections and the Guidelines recap.

DimensionReasoningScore

Conciseness

The body is lean — each tool gets a one-line description, copy-paste bash calls, and a parameter table — but the Guidelines section repeats facts already stated inline (e.g., the 'agent-smith-dev/assistants/smith/<name>/' and '.references/' landing paths appear twice), which is minor trimming material.

4 / 5

Actionability

Every tool has fully executable, copy-paste-ready `tai tool` commands with concrete example payloads ('{"id": "smith.weather"}', '{"namespace": "smith"}'), plus parameter tables specifying types, required flags, and constraints — fully executable and covering the common cases.

5 / 5

Workflow Clarity

This is a reference of single-command tools rather than a multi-step process, so the simple-skill exception applies: each action is unambiguous, and the Guidelines supply the key ordering rule ('Use agent_list to discover agents before downloading or referencing') plus namespace restrictions. No destructive or batch operation is present, so the validation cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist (references/scripts/assets are absent) and none are needed at this size; the skill is self-contained with clear per-tool section headers, consistent structure, and a closing Guidelines section, making navigation trivial.

5 / 5

Total

19

/

20

Passed

Description

83%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 strong description: concrete, comprehensive in covering all five tool capabilities, with an explicit 'ALWAYS invoke when...' trigger clause. Its only weaknesses are the second-person 'when you need to' phrasing (penalized under the voice rule) and some missing natural trigger synonyms.

Suggestions

Rewrite in third person (e.g., 'Use when the user needs to list, download, reference, or deploy agents...') to avoid the second-person specificity penalty.

Add common trigger synonyms such as 'agent source code', 'models available', or 'connector roles' to broaden natural-term coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('list available agents, download or reference agent source code, deploy agent code to the host, or query the LLM connector matrix'), which would anchor at 5, but the second-person phrasing 'when you need to list available agents' triggers the rubric's 1-point voice penalty, capping it at 4.

4 / 5

Completeness

It explicitly answers what the skill does (the five management actions) and when to use it ('ALWAYS invoke this skill when you need to...'), matching the anchor for a clear what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrases users would say ('list available agents', 'download', 'deploy agent code', 'LLM connector matrix'), but some common variations are missing (e.g., 'agent source', 'connector models', shorthand forms).

4 / 5

Distinctiveness Conflict Risk

The niche (host agent management via `tai tool`) is distinct with specific triggers like 'connector matrix' and 'deploy agent code', but the generic word 'agent' creates minor overlap risk with subagent/agent-related skills in the same environment.

4 / 5

Total

17

/

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-agent/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.