CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

slippage

Slippage estimation, optimization, and protection for trade execution

56

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/slippage/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is a highly actionable, executable API reference with lean code-first organization, but it functions as a monolithic 300-line catalog with no progressive disclosure to separate files and no explicit workflow validation checkpoints for its destructive execution operations.

Suggestions

Move the bulk TypeScript API reference into a separate file (e.g. references/API.md) and keep SKILL.md as an overview with one-level-deep, clearly signaled links.

Add an explicit sequenced workflow with validation checkpoints for execution (e.g. estimate → check depth → set protection → execute → verify actual vs expected slippage → retry/revert on breach).

Factor out the repeated platform/market/side boilerplate by stating shared parameters once and showing only the differing parts in subsequent examples.

DimensionReasoningScore

Conciseness

The body is lean and code-driven with no explanations of concepts Claude already knows, though repeated boilerplate params (platform/market/side) across examples could be trimmed to reach level 5.

4 / 5

Actionability

Fully executable, copy-paste-ready TypeScript snippets and concrete chat commands cover the common cases comprehensively (estimate, depth, impact, optimize, split, TWAP, timing, protection, DEX, history).

5 / 5

Workflow Clarity

A rough recommended order appears in 'Best Practices' (estimate first, split, monitor) but there are no explicit validation checkpoints or feedback-loop steps; because trade execution is destructive, workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

Section headers organize the content well, but ~300 lines of API reference are fully inlined in SKILL.md with no references to separate files and no bundle files present, matching the level-3 anchor of structured-but-inline content.

3 / 5

Total

15

/

20

Passed

Description

58%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 specific and distinct, naming a clear niche with three concrete action categories, but it omits any 'Use when…' trigger guidance and relies on a single core keyword without synonyms.

Suggestions

Add an explicit 'Use when…' clause stating when Claude should invoke this skill, e.g. 'Use when estimating, minimizing, or protecting against slippage on trade execution.'

Include natural trigger synonyms users say, such as 'price impact' or 'orderbook depth', to broaden keyword coverage.

Ground the action verbs in more concrete operations (e.g. 'estimate price impact', 'split orders', 'set max-slippage tolerances') to reach full specificity.

DimensionReasoningScore

Specificity

Names the domain ('slippage', 'trade execution') and several concrete action categories — 'estimation, optimization, and protection' — with only minor gaps in granularity compared to the level-5 anchor's finer-grained verbs.

4 / 5

Completeness

Clearly states what the skill does ('Slippage estimation, optimization, and protection for trade execution') but provides no 'Use when…' trigger clause, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural keywords ('slippage', 'trade execution') a user would say, but lacks common synonyms like 'price impact' and any variations, matching the level-3 anchor.

3 / 5

Distinctiveness Conflict Risk

The 'slippage' niche is clearly distinct with minimal conflict risk, but the absence of an explicit trigger phrase keeps it just below the level-5 anchor.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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/slippage/SKILL.md

Revision

c930628

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill