Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

router

Smart order routing for best price, liquidity, and execution

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/router/SKILL.md

Quality

Content

72%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 comprehensive executable TypeScript examples and clean section structure, but it is a monolithic single-file reference with no progressive disclosure and, critically, lacks validation/confirmation steps around irreversible order execution.

Suggestions

Add explicit validation or confirmation checkpoints before execute/split operations (e.g., confirm route details and net cost before executing an irreversible trade).

Move the bulk API reference, platform comparison, and fee/liquidity analysis into separate reference files linked from a concise overview in SKILL.md to improve progressive disclosure.

Trim redundant mode examples (the 'Routing Modes' section restates findBestRoute calls already shown) and condense repeated console.log blocks to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is a lean API reference that assumes competence — no padding explaining what routing or libraries are — with only minor redundancy (the 'Routing Modes' section repeats findBestRoute four times, and verbose console.log blocks in every example). Not a 5 because of that redundancy; not a 3 because it does not explain concepts Claude already knows.	4 / 5
Actionability	Provides fully executable, copy-paste-ready TypeScript covering the common cases (findBestRoute, compare, splitOrder, execute, analyzeFees, analyzeLiquidity) with imports and concrete outputs. Not a 4 because the examples are complete rather than having minor gaps.	5 / 5
Workflow Clarity	A route→execute sequence is implied via chat commands, but executing routed orders is an irreversible financial operation with no validation or confirmation checkpoints, capping workflow clarity at 3 per the destructive-operations guideline. Not a 4 because validation is absent; not a 2 because a rough sequence is present.	3 / 5
Progressive Disclosure	Section headers provide structure, but the entire API reference, comparison tables, and fee/liquidity analyses are inlined in one ~234-line file with no references to separate files and no bundle files present. Not a 4 because content that belongs in separate files is inlined; not a 2 because the section headers give real navigability.	3 / 5
	Total	15 / 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 names a distinct, well-scoped capability with concrete optimization criteria, but it omits any 'Use when…' trigger guidance, which caps completeness and limits trigger discoverability.

Suggestions

Add an explicit 'Use when…' clause stating when Claude should invoke this skill (e.g., 'Use when routing orders across platforms for best execution').

Include natural trigger phrases users would actually say, such as 'route this order', 'best execution', or 'compare platforms', to improve trigger-term coverage.

Optionally name a second concrete capability (e.g., splitting large orders) to lift specificity beyond a single action.

Dimension	Reasoning	Score
Specificity	Names the domain ('Smart order routing') and concrete optimization criteria ('best price, liquidity, and execution'), but only a single action is described rather than multiple distinct capabilities. Not a 4 because it lacks several specific actions; not a 2 because the three named criteria add real concreteness beyond a bare domain label.	3 / 5
Completeness	Has a clear 'what' (smart order routing for price/liquidity/execution) but no 'Use when…' or equivalent trigger guidance, capping completeness at 3 per the rubric guideline. Not a 4 because 'when' is entirely absent; not a 2 because the 'what' is concrete rather than vague.	3 / 5
Trigger Term Quality	Includes relevant domain keywords ('order routing', 'best price', 'liquidity', 'execution') a trader might say, but offers no natural synonyms or variations. Not a 4 because common phrasings are missing; not a 2 because the terms are domain-relevant rather than purely generic.	3 / 5
Distinctiveness Conflict Risk	'Smart order routing' is a clear, distinct niche unlikely to fire for unrelated skills. Not a 5 because the terse description lacks explicit trigger phrases that fully disambiguate; not a 3 because it is more specific than the 'somewhat specific but overlapping' anchor.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/router/SKILL.md
Revision: c930628

Reviewed: 1 month ago

Discovery Implementation Validation

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.

router

Table of Contents

Is this your skill?