mev

MEV protection against sandwich attacks and front-running

Quality

30%

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

Quality

Discovery

22%

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 reads as a topic label rather than a functional skill description. It lacks concrete actions (no verbs describing what the skill does), has no 'Use when...' clause, and while the domain is somewhat niche, the absence of specificity makes it hard for Claude to know exactly when and how to apply this skill.

Suggestions

Add concrete action verbs describing what the skill does, e.g., 'Analyzes pending transactions for MEV exposure, detects sandwich attack patterns, and recommends protection strategies such as private mempools or slippage limits.'

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about protecting DeFi transactions from front-running, sandwich attacks, MEV extraction, or transaction ordering manipulation.'

Include additional natural trigger terms users might say, such as 'mempool', 'flashbots', 'DEX', 'slippage', 'transaction protection', or 'blockchain security'.

Dimension	Reasoning	Score
Specificity	The description names a domain (MEV protection) and mentions two attack types (sandwich attacks, front-running), but does not describe any concrete actions the skill performs. There are no verbs indicating what the skill actually does—it reads more like a topic label than a capability description.	1 / 3
Completeness	The description weakly addresses 'what' (protection against attacks) but provides no 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent, which per the rubric should cap completeness at 2, and the 'what' itself is too vague to merit even a 2.	1 / 3
Trigger Term Quality	It includes some relevant technical keywords users might say ('MEV', 'sandwich attacks', 'front-running'), but misses common variations like 'mempool', 'flashbots', 'transaction ordering', 'DEX trading', 'slippage protection', or 'blockchain'. Coverage of natural trigger terms is incomplete.	2 / 3
Distinctiveness Conflict Risk	The MEV/sandwich attack domain is fairly niche and unlikely to conflict with most other skills, but the lack of specificity about what the skill actually does (analysis? code generation? transaction simulation?) means it could overlap with general blockchain or DeFi security skills.	2 / 3
	Total	6 / 12 Passed

Implementation

37%

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

This skill provides a broad API reference for MEV protection with typed code examples and useful summary tables, but it lacks executable completeness (undefined variables, fictional library) and has no workflow sequencing or validation steps for what are inherently risky financial operations. The content reads more like API documentation than an actionable skill that guides Claude through protecting trades safely.

Suggestions

Add a clear end-to-end workflow (e.g., 1. Simulate risk → 2. Choose protection level → 3. Execute protected trade → 4. Verify inclusion → 5. Analyze result) with explicit validation checkpoints and error recovery steps.

Make code examples truly executable by defining or explaining prerequisite variables (routerAddress, swapCalldata, swapInstructions) and adding error handling for common failure modes like bundle rejection or timeout.

Add explicit error handling guidance: what happens when Flashbots bundles aren't included, when Jito tips are too low, or when MEV Blocker rejects a transaction.

Consider splitting the detailed per-provider API reference into separate files and keeping SKILL.md as a concise overview with the core workflow and quick-start example.

Dimension	Reasoning	Score
Conciseness	The content is reasonably organized but includes some unnecessary verbosity—console.log examples for every field, redundant comments explaining obvious things, and tables that restate what's already shown in code. The attack types table and best practices are useful but could be tighter.	2 / 3
Actionability	The code examples look concrete and typed, but they reference a fictional 'clodds/mev' library with no installation instructions or verification that it exists. Functions like `calculateMinOut`, `routerAddress`, and `swapCalldata` are used without definition, making the examples not truly copy-paste executable.	2 / 3
Workflow Clarity	There is no clear multi-step workflow for protecting a trade end-to-end. The skill presents isolated API calls without sequencing them into a coherent process. For a task involving financial transactions where errors can be costly, there are no validation checkpoints, error handling, or feedback loops (e.g., what to do if a Flashbots bundle fails or times out).	1 / 3
Progressive Disclosure	The content is structured with clear sections and headers, and the tables provide quick-reference summaries. However, it's a long monolithic document (~180 lines of API reference) with no references to external files for detailed topics like provider setup or advanced configuration.	2 / 3
	Total	7 / 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.