CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

routing

Multi-agent routing, channel bindings, and tool policies

45

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/routing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 highly actionable with complete executable examples, but it over-inlines a full API reference, lacks validation checkpoints for destructive operations, and does no progressive disclosure into separate files.

Suggestions

Move the bulk of the TypeScript API reference and built-in agent catalog into a separate reference file (e.g., references/api.md) and keep only a quick-start excerpt in SKILL.md.

Add explicit validation/verification steps for destructive or batch operations (e.g., confirm tool-policy changes and dry-run before 'execute' orders).

Trim redundant tables (Built-in Agents, Tool Categories) that restate the inline code to reduce token usage.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: it inlines a full API reference, four built-in agent configs, and redundant tables that mostly restate the code above, padding the context with material Claude could derive from the executable examples.

2 / 5

Actionability

Every section provides copy-paste-ready, fully executable TypeScript with concrete arguments and outputs, covering the common cases comprehensively.

5 / 5

Workflow Clarity

A rough sequence exists (route → bind → policy) but there are no validation checkpoints or feedback loops for destructive or batch operations like 'execute' trades or tool-policy changes, which caps the score at 3.

3 / 5

Progressive Disclosure

It is a monolithic API reference inlined into SKILL.md with no bundle files and no offloading to separate reference documents; content that clearly belongs in a dedicated file is all inlined.

2 / 5

Total

12

/

20

Passed

Description

42%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 cleanly states what the skill does with specific, mostly-distinct terms, but it lacks any 'Use when...' trigger guidance and relies on technical jargon rather than natural user language.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g., 'Use when routing messages to specialized agents, configuring channel bindings, or managing tool access').

Replace or augment jargon with natural user-facing terms and synonyms (e.g., 'assign messages to agents', 'bind a channel to an agent', 'allow or deny tools').

Confirm completeness by ensuring both the 'what' and the 'when' are present in a single sentence.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'routing', 'channel bindings', and 'tool policies' — with only minor gaps in coverage versus the score-5 anchor.

4 / 5

Completeness

It states a clear 'what' but provides no 'Use when...' trigger clause, so the 'when' is entirely missing, matching the anchor where only the 'what' is present weakly.

2 / 5

Trigger Term Quality

The terms 'routing', 'channel bindings', and 'tool policies' are technical jargon rather than natural phrases a user would say; no common user-facing synonyms are present.

2 / 5

Distinctiveness Conflict Risk

The niche (multi-agent routing + channel bindings + tool policies) is fairly distinct from other skills with only minor overlap risk against generic agent-configuration skills.

4 / 5

Total

12

/

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.

Validation — 15 / 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

alsk1992/CloddsBot

Path

src/skills/bundled/routing/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.