CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mev

MEV protection against sandwich attacks and front-running

57

Quality

72%

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/mev/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 content is highly actionable with comprehensive executable examples and stays lean, but it lacks an explicit end-to-end workflow with validation checkpoints and inlines a large API reference that should be split into separate files.

Suggestions

Add an explicit numbered workflow with validation checkpoints (simulate risk -> set level -> execute protected -> analyze transaction) instead of presenting the APIs as disconnected calls.

Move the full TypeScript API reference and per-provider details into a separate reference file, keeping SKILL.md as an overview with one-level-deep links.

Surface a pre-trade validation gate ("Only proceed when simulateRisk returns low/medium") to satisfy the destructive/batch validation expectation.

DimensionReasoningScore

Conciseness

The body is mostly lean code examples and reference tables with no padding about basic concepts Claude already knows; only minor inline comments ("// EVM trade with protection", "// Default level") could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready TypeScript covering the common cases (create, executeProtected, flashbots, mevBlocker, jito, analyzeTransaction, simulateRisk, setLevel) plus concrete chat commands, matching the fully-executable anchor.

5 / 5

Workflow Clarity

Operations are presented as isolated API calls rather than a sequenced workflow; pre/post validation primitives (simulateRisk, analyzeTransaction) exist but are not wired into an explicit validate-then-execute loop for these financially impactful trades.

3 / 5

Progressive Disclosure

No bundle files exist and the entire TypeScript API reference is inlined in a 240-line SKILL.md, well past the 50-line simple-skill exception; section headers provide structure, but content that belongs in a separate reference file is inline.

3 / 5

Total

15

/

20

Passed

Description

61%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 clearly identifies the MEV-protection niche and uses natural trigger terms, but it lacks any "use when" guidance and relies on a generic action verb. Adding explicit trigger phrases and concrete actions would lift the weaker dimensions.

Suggestions

Add a "Use when..." clause with concrete triggers, e.g. "Use when executing trades on Ethereum/Solana, or when the user mentions MEV, sandwich attacks, front-running, or slippage protection."

Replace the generic "protection" with concrete actions, e.g. "Route trades through private mempools (Flashbots/Jito), simulate MEV risk, and analyze past transactions for sandwich attacks and front-running."

Include common synonyms (slippage, MEV bots, private mempool) to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the MEV domain and two concrete threats ("sandwich attacks and front-running"), but the action verb is the generic "protection" rather than a concrete operation, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

It clearly states what the skill does ("MEV protection against sandwich attacks and front-running") but includes no "Use when..." clause or equivalent trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

"MEV protection", "sandwich attacks", and "front-running" are natural phrases a user would say, giving good keyword coverage, though a few common synonyms (slippage, MEV bots) are missing.

4 / 5

Distinctiveness Conflict Risk

MEV protection is a clear niche with distinct triggers, but the absence of explicit "use when" guidance leaves minor overlap risk with a broader DeFi/trading skill.

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

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.