slippage

Slippage estimation, optimization, and protection for trade execution

Quality

56%

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 financial/trading niche (slippage) but remains too abstract and lacks explicit trigger guidance. It would benefit from concrete action verbs and a clear 'Use when...' clause to help Claude distinguish this skill from other trading-related skills.

Suggestions

Add a 'Use when...' clause with trigger terms like 'slippage tolerance', 'price impact', 'swap execution', 'DEX trades', or 'execution costs'

Replace abstract nouns with concrete actions: e.g., 'Calculates expected slippage, sets tolerance limits, recommends optimal trade sizes to minimize price impact'

Include common user phrases and variations: 'slippage settings', 'max slippage', 'price slippage', 'trading slippage protection'

Dimension	Reasoning	Score
Specificity	Names the domain (trade execution) and lists some actions (estimation, optimization, protection), but these are somewhat abstract and not fully concrete actions like 'calculate expected slippage' or 'set slippage tolerance limits'.	2 / 3
Completeness	Describes what the skill does at a high level but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant terms like 'slippage', 'trade execution', and 'protection', but misses common variations users might say such as 'price impact', 'swap', 'DEX', 'trading fees', or 'execution price'.	2 / 3
Distinctiveness Conflict Risk	'Slippage' is a fairly specific term that narrows the domain, but 'trade execution' could overlap with general trading skills, order management, or market analysis skills without clearer boundaries.	2 / 3
	Total	7 / 12 Passed

Implementation

79%

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

This is a well-written API reference with excellent actionability and conciseness - every code example is executable and the content respects Claude's intelligence. However, it lacks explicit multi-step workflows showing how to combine estimation, optimization, and protected execution in sequence, and the comprehensive content would benefit from being split across multiple files with clear navigation.

Suggestions

Add a 'Common Workflows' section showing complete sequences like: estimate slippage → check if acceptable → optimize if needed → execute with protection → verify actual slippage

Split the extensive API reference into separate files (e.g., ESTIMATION.md, OPTIMIZATION.md, PROTECTION.md) and keep SKILL.md as a concise overview with navigation links

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, presenting API references and commands without unnecessary explanation. It assumes Claude understands trading concepts and jumps directly to executable examples.	3 / 3
Actionability	Provides fully executable TypeScript code examples that are copy-paste ready, with concrete chat commands and clear parameter specifications. Every section includes working code with realistic outputs.	3 / 3
Workflow Clarity	While individual API methods are clear, there's no explicit workflow for common multi-step scenarios like 'estimate → optimize → execute with protection'. The protection section shows execution but lacks a complete workflow with validation checkpoints.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but it's a monolithic document with no references to external files for advanced topics. The extensive API reference could be split into separate files with the main skill providing an overview.	2 / 3
	Total	10 / 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: 2a8c94e

Reviewed: 29 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.