slippage

Slippage estimation, optimization, and protection for trade execution

Quality

22%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/slippage/SKILL.md

Quality

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 identifies a specific trading domain (slippage) but remains too high-level in its action descriptions and completely lacks trigger guidance. It would benefit significantly from concrete action details and an explicit 'Use when...' clause to help Claude select it appropriately from a pool of trading-related skills.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about slippage estimation, minimizing price impact, setting slippage tolerance, or optimizing trade execution parameters.'

List more specific concrete actions, e.g., 'Estimates expected slippage from order book depth, calculates optimal trade sizes to minimize market impact, sets slippage tolerance thresholds for DEX swaps.'

Include natural trigger term variations such as 'price impact', 'market impact', 'execution cost', 'slippage tolerance', 'DEX swap', or 'order routing' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (trade execution slippage) and some actions (estimation, optimization, protection), but these are fairly high-level and not concrete enough to understand exactly what the skill does (e.g., does it calculate expected slippage from order book data? simulate market impact? set slippage tolerance parameters?).	2 / 3
Completeness	Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also fairly weak, this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'slippage', 'trade execution', 'optimization', and 'protection' which users in trading contexts might use. However, it misses common variations and related terms like 'market impact', 'price impact', 'execution quality', 'order book', 'DEX', 'AMM', or 'trading fees'.	2 / 3
Distinctiveness Conflict Risk	The term 'slippage' is fairly specific to trading/DeFi contexts, which helps distinguish it. However, it could overlap with broader trade execution skills, order routing skills, or general trading optimization skills without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Implementation

12%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is a lengthy, speculative API reference for a fictional library ('clodds/slippage') with no real-world executability. It is extremely verbose with repetitive console.log patterns, lacks validation/error-handling workflows critical for financial operations, and dumps everything into a single monolithic file. The content describes rather than instructs, offering no actionable guidance Claude could actually use.

Suggestions

Replace the fictional 'clodds/slippage' API with real, executable code or clearly document which actual platforms/libraries this wraps, so the skill becomes actionable.

Drastically reduce verbosity by removing repetitive console.log output examples — show one complete example and summarize the rest in a table or type definition.

Add explicit error handling and validation workflows (e.g., what happens when slippage exceeds threshold, how to verify order execution, rollback procedures) since these are financial operations.

Split the monolithic content into a concise SKILL.md overview with references to separate files for API reference, DEX-specific guidance, and execution strategies.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive console.log statements that add no instructional value. The skill is essentially a speculative API reference for a non-existent library ('clodds/slippage'), with massive amounts of repetitive code showing output formatting rather than teaching actionable patterns. Many sections could be collapsed significantly.	1 / 3
Actionability	Despite appearing code-heavy, none of this is executable — 'clodds/slippage' is a fabricated library. The chat commands (/slippage estimate, etc.) reference no real tool or platform. There's no real system a user or Claude could actually run this against, making it entirely non-actionable.	1 / 3
Workflow Clarity	There is a logical progression from estimation → analysis → optimization → protection, and the best practices section mentions 'always estimate first' before trading. However, there are no explicit validation checkpoints, error handling flows, or feedback loops for what are potentially costly financial operations.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with every API method inlined. The entire document is ~250 lines of detailed API reference that should be split into separate files (e.g., a quick-start overview in SKILL.md with references to API_REFERENCE.md, DEX.md, etc.). No external references or navigation structure exists.	1 / 3
	Total	5 / 12 Passed

Validation

90%

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 — 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: 11 days ago

Table of Contents

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.