CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kun-tool-router

Route requests to the narrowest real Kun tool family and define the required verification boundary.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./resources/bundled-skills/kun-tool-router/SKILL.md
SKILL.md
Quality
Evals
Security

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 a tightly written, well-structured routing skill with a concrete tool table and a sensible sequenced workflow that includes an explicit verification step. Its main weakness is actionability: the routing and verification directives stay abstract, giving Claude decision principles rather than executable criteria or worked examples.

Suggestions

Add 2–3 concrete routing examples (input → chosen tool with the verification evidence), e.g. 'User asks to edit a canvas shape → design_update_shapes → verify via editable canvas state.'

Define 'verification boundary' operationally — what counts as the 'closest observable output' per output class (file, browser action, presentation, integration).

Delete or differentiate the 'Purpose' section, which duplicates the frontmatter description verbatim and adds no new information.

DimensionReasoningScore

Conciseness

The body is lean — a compact routing table, a five-step workflow, and short gate/boundary sections with no padding or explanations of known concepts. The only trimmable redundancy is the 'Purpose' section repeating the frontmatter description verbatim, which keeps it just below anchor 5's 'every token earns its place.'

4 / 5

Actionability

The tool routing table gives concrete tool-to-use mappings (fast_context, browser_use, office_inspect, etc.), but the workflow steps are abstract directives — 'Choose the most specific advertised tool', 'Perform the smallest coherent action', 'Verify using the closest observable output' — with no decision criteria, worked examples, or definitions of what a 'verification boundary' concretely requires. This matches anchor 3 (some concrete guidance but incomplete, missing key details) rather than anchor 4's mostly executable guidance.

3 / 5

Workflow Clarity

The workflow has a clear, well-sequenced five steps (classify → choose → inspect state → act → verify) with an explicit verification checkpoint in step 5 and supporting completion gates. It falls short of anchor 5 because there is no error-recovery feedback loop describing what to do when verification fails, only 'Report unresolved failures without hiding them.'

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose (routing), has no bundle files, and needs no external references; its sections (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery) are well-organized and easy to navigate. Per the simple-skill guideline, this earns anchor 5 on well-organized sections alone.

5 / 5

Total

16

/

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 is concise and identifies a distinct niche, but it reads more like an internal mission statement than a trigger description. It states a clear 'what' with a couple of concrete actions, yet provides no 'when to use' guidance and relies on jargon rather than natural user vocabulary.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a request targets Kun tools, canvas edits, presentations, Office documents, browser tasks, or MCP integrations, or when choosing between available Kun tools.'

Replace jargon like 'narrowest real Kun tool family' and 'verification boundary' with natural phrasing users would say (e.g., 'pick the right Kun tool', 'verify the result').

Enumerate the concrete capabilities covered (repository exploration, public browsing, canvas editing, presentation export, Office inspection, integration discovery) so the routing scope is explicit.

DimensionReasoningScore

Specificity

Names the domain ("Kun tool family") and two concrete actions ("Route requests", "define the required verification boundary"), but coverage is not comprehensive — no tool families, output types, or example scenarios are listed. It sits above anchor 2 (which offers only minimal or generic actions) and below anchor 4 (which lists several specific actions).

3 / 5

Completeness

The 'what' is stated clearly (route requests to Kun tool families, define verification boundaries) but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not anchor 2 because the 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

Contains some relevant keywords ("route", "requests", "tool") but leans on internal jargon ("narrowest real Kun tool family", "verification boundary") and misses the natural phrases, variations, and synonyms a user would actually say. Better than anchor 2's one-or-two purely generic keywords, but far from anchor 4's good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

The explicit 'Kun' branding carves out a clear niche and makes conflict with unrelated skills unlikely, but 'Route requests' is generic and the absence of distinct trigger phrases leaves minor overlap risk with other routing or tool-selection skills. Closest to anchor 4 rather than anchor 5, whose example includes explicit, distinctive triggers.

4 / 5

Total

13

/

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

KunAgent/Kun

Path

resources/bundled-skills/kun-tool-router/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.