router
Smart order routing for best price, liquidity, and execution
Overall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
33%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too brief and lacks the explicit trigger guidance needed for Claude to reliably select it. While it identifies a specific financial domain (order routing), it fails to list concrete actions or provide 'Use when...' clauses that would help distinguish it from other trading-related skills.
Suggestions
Add a 'Use when...' clause with trigger terms like 'route my order', 'best execution', 'find liquidity', 'trade routing', 'SOR'
List specific concrete actions such as 'analyze venue liquidity', 'compare execution costs across exchanges', 'split orders for optimal fill rates'
Include common user phrases and file types/data formats this skill handles (e.g., 'FIX messages', 'order books', 'market data feeds')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (order routing) and mentions some goals (best price, liquidity, execution), but doesn't list concrete actions like 'route orders to exchanges', 'compare bid/ask spreads', or 'split large orders'. | 2 / 3 |
Completeness | Only addresses 'what' at a high level and completely lacks any 'when' guidance or 'Use when...' clause. Per rubric guidelines, missing explicit trigger guidance caps this at 2, but the 'what' is also weak, warranting a 1. | 1 / 3 |
Trigger Term Quality | Contains some relevant terms ('order routing', 'price', 'liquidity', 'execution') but misses common variations users might say like 'trade execution', 'fill orders', 'SOR', 'best execution', or 'order management'. | 2 / 3 |
Distinctiveness Conflict Risk | The term 'smart order routing' is fairly specific to trading/finance domain, but could overlap with general trading skills, order management skills, or execution algorithms without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable API documentation with executable code examples and clear chat commands. However, it lacks validation workflows critical for financial order routing (no error handling, no confirmation steps before execution), and the content could be more concise by reducing redundancy and splitting the lengthy API reference into a separate file.
Suggestions
Add explicit validation and error handling steps between route finding and execution (e.g., 'Verify route is still valid', 'Check for price changes', 'Confirm before executing')
Move the detailed TypeScript API Reference to a separate REFERENCE.md file, keeping only quick-start examples in the main skill
Consolidate fee information into a single authoritative location instead of repeating it in multiple sections
Add error recovery guidance for common routing failures (market moved, insufficient liquidity, platform unavailable)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some redundancy (fee information repeated in multiple places, verbose console.log examples that could be trimmed). The API reference is comprehensive but could be more condensed. | 2 / 3 |
Actionability | Provides fully executable TypeScript code examples that are copy-paste ready. Chat commands are concrete with clear syntax. All API methods show complete usage patterns with realistic parameters. | 3 / 3 |
Workflow Clarity | The skill shows individual operations clearly but lacks explicit validation checkpoints for the routing workflow. No error handling or verification steps shown between finding a route and executing it, which is important for financial operations. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's a monolithic document with no references to external files for detailed topics. The API reference section is quite long and could be split into a separate reference file. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
91%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.