router
Smart order routing for best price, liquidity, and execution
38
23%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/router/SKILL.mdQuality
Discovery
32%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 a single short phrase that hints at a specific financial trading domain but lacks concrete actions, explicit trigger guidance, and a 'Use when...' clause. It reads more like a tagline than a functional skill description, making it difficult for Claude to reliably select this skill from a large pool.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about routing orders across exchanges, optimizing trade execution, or finding best prices across venues.'
List specific concrete actions the skill performs, such as 'Analyzes order books across multiple venues, splits orders to minimize market impact, selects optimal execution venues based on latency and fill probability.'
Include natural keyword variations users might say, such as 'SOR', 'trade execution', 'venue selection', 'order splitting', 'best execution', 'market microstructure'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (order routing) and mentions some goals (best price, liquidity, execution), but does not list concrete actions like 'split orders across venues', 'compare bid/ask spreads', or 'route to dark pools'. | 2 / 3 |
Completeness | Provides a brief 'what' (smart order routing for best price/liquidity/execution) but completely lacks any 'when' clause or explicit trigger guidance, which per the rubric caps completeness at 2 at best—and since the 'what' is also thin, it falls to 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'order routing', 'price', 'liquidity', and 'execution' that a user in trading/finance might use, but misses common variations such as 'SOR', 'trade execution', 'venue selection', 'fill rate', or 'market order'. | 2 / 3 |
Distinctiveness Conflict Risk | The phrase 'smart order routing' is fairly niche within trading/finance, reducing conflict with unrelated skills, but it could overlap with other trading or execution-related skills due to the generic terms 'price', 'liquidity', and 'execution'. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an overly verbose API reference dump that lacks workflow structure, validation steps, and progressive disclosure. It explains concepts that are self-evident, duplicates information across sections, and provides no error handling or verification for financial order execution — a domain where such safeguards are critical. The content would benefit greatly from being restructured into a concise overview with references to detailed sub-documents.
Suggestions
Restructure into a concise SKILL.md overview (under 50 lines) with links to separate files for API reference, fee comparison, and liquidity analysis
Add an end-to-end workflow with explicit validation steps: check route validity, verify liquidity, confirm before execution, handle partial fills and errors
Remove redundant console.log examples and the duplicated routing modes section (table + code); keep only the table and one brief code example
Add error handling patterns and verification steps for order execution — e.g., what to do when a route becomes stale, how to handle failed executions, and how to verify fills
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with excessive console.log examples that add no instructional value. The repeated pattern of logging every field of every response object is pure padding. The routing modes section is shown both as a code example AND a table, duplicating information. Much of this content (like what 'best-price' means) is self-evident to Claude. | 1 / 3 |
Actionability | The code examples look executable and use a consistent API, but they reference a fictional 'clodds/router' package with no indication of whether this is real or how to install/configure it. The chat commands (/route) are presented without explaining what system processes them. It's unclear if this is documenting a real API or a hypothetical one. | 2 / 3 |
Workflow Clarity | There is no clear workflow sequence for routing an order end-to-end. The skill presents isolated API calls without connecting them into a coherent process. There are no validation checkpoints — no error handling, no verification that a route is still valid before execution, no feedback loops for failed orders or partial fills. For financial order execution, this is a significant gap. | 1 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. The full API reference, fee tables, liquidity analysis, and best practices are all inlined. The detailed TypeScript API reference should be in a separate file, with SKILL.md serving as a concise overview with navigation links. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%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 | |
- Repository
- alsk1992/CloddsBot
- Commit
e71a5f6
- 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.