mev

MEV protection against sandwich attacks and front-running

Quality

52%

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

40%

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 specialized blockchain security domain with some specific attack types, giving it good distinctiveness. However, it lacks concrete action verbs describing what the skill actually does and completely omits trigger guidance for when Claude should use it. The description reads more like a topic label than an actionable skill description.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about protecting transactions from MEV, configuring flashbots, or analyzing mempool risks'

Include concrete actions the skill performs, e.g., 'Detects sandwich attack patterns, configures MEV protection strategies, analyzes transaction ordering risks'

Expand trigger terms to include related concepts users might mention: 'mempool', 'flashbots', 'private transactions', 'DEX swaps', 'slippage protection'

Dimension	Reasoning	Score
Specificity	Names the domain (MEV protection) and mentions specific attack types (sandwich attacks, front-running), but doesn't describe concrete actions like 'detect', 'prevent', 'analyze', or 'configure'.	2 / 3
Completeness	Only partially addresses 'what' (protection against attacks) but completely missing 'when' - no 'Use when...' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant technical terms users might say ('MEV', 'sandwich attacks', 'front-running'), but missing common variations like 'mempool', 'flashbots', 'transaction protection', 'DEX trading', or 'slippage'.	2 / 3
Distinctiveness Conflict Risk	MEV protection is a clear niche in blockchain/DeFi with distinct terminology; unlikely to conflict with other skills due to specialized domain vocabulary.	3 / 3
	Total	8 / 12 Passed

Implementation

64%

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

This skill provides comprehensive, actionable MEV protection guidance with excellent code examples and clear API documentation. However, it's overly long for a single file and lacks explicit workflow validation steps for what are inherently risky financial operations. The content would benefit from being split into overview + detailed reference files.

Suggestions

Add explicit workflow with validation: 1) Simulate risk, 2) If high risk, enable protection, 3) Execute trade, 4) Verify transaction wasn't attacked, 5) If attacked, document and adjust settings

Split into SKILL.md (quick start + when to use) and separate API_REFERENCE.md and PROVIDERS.md files

Remove explanatory comments that Claude already knows (e.g., 'MEV bots watch everything', basic descriptions of attack types)

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with good code examples and tables, but includes some unnecessary explanatory comments and the 'Best Practices' section contains advice Claude would already know (e.g., 'MEV bots watch everything').	2 / 3
Actionability	Provides fully executable TypeScript code examples with complete function signatures, configuration objects, and result handling. Chat commands are copy-paste ready with clear syntax.	3 / 3
Workflow Clarity	Individual operations are clear, but lacks explicit validation checkpoints for the multi-step trading workflow. The 'simulate risk -> execute protected trade -> verify' flow is implied but not explicitly sequenced with error recovery steps.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections and tables, but everything is in one monolithic file. API reference details could be split into separate files with the main skill providing a quick-start overview.	2 / 3
	Total	9 / 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.