analyzing-mempool
Monitor blockchain mempools for pending transactions, gas analysis, and MEV opportunities. Use when analyzing pending transactions, optimizing gas prices, or researching MEV. Trigger with phrases like "check mempool", "scan pending txs", "find MEV", "gas price analysis", or "pending swaps".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill analyzing-mempool84
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific capabilities (mempool monitoring, gas analysis, MEV), explicit usage guidance with a 'Use when...' clause, and natural trigger phrases that users in the crypto/blockchain space would actually say. The description is concise, uses proper third-person voice, and carves out a clear niche that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Monitor blockchain mempools', 'pending transactions', 'gas analysis', and 'MEV opportunities'. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (monitor mempools, gas analysis, MEV opportunities) AND when with explicit 'Use when...' clause covering analyzing pending transactions, optimizing gas, and researching MEV, plus specific trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'check mempool', 'scan pending txs', 'find MEV', 'gas price analysis', 'pending swaps'. These are realistic phrases a crypto user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on blockchain mempools and MEV - very specific domain that wouldn't overlap with general crypto or trading skills. The trigger terms like 'mempool', 'MEV', and 'pending txs' are unique identifiers. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable guidance for mempool analysis with executable commands and good progressive disclosure. The main weaknesses are some verbosity in explanatory sections and missing validation checkpoints for operations that could inform financial decisions. The structure is clean and references are well-organized.
Suggestions
Remove the 'Useful for traders, MEV researchers, and protocol developers' line and trim the MEV warnings to essential safety notes only
Add a validation step after gas analysis (e.g., 'Verify current block gas before submitting transaction') to prevent acting on stale data
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary context like 'Useful for traders, MEV researchers, and protocol developers' and verbose prerequisites section. The MEV warnings section explains concepts Claude likely knows. | 2 / 3 |
Actionability | Provides fully executable bash commands with clear flags and options. Commands are copy-paste ready with specific examples for each use case including chain selection and verbosity flags. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but lacks validation checkpoints. For operations involving MEV detection or gas analysis that could lead to financial decisions, there's no explicit verification step before acting on results. | 2 / 3 |
Progressive Disclosure | Well-structured with clear overview, organized command sections, and appropriate references to external files (errors.md, examples.md) that are one level deep and clearly signaled with descriptive context. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.