CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

evm

Read-only EVM client: wallets, tokens, gas across 8 chains.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/blockchain/evm/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 an exemplary CLI-skill reference: fully executable commands with realistic examples, explicit setup and verification checkpoints, and unusually honest failure-mode documentation. Its one real weakness is redundancy — the Procedure section largely duplicates the Quick Reference and could be merged to save roughly 60 lines.

Suggestions

Merge the "Procedure" section into "Quick Reference" by adding the one-line context each procedure provides (e.g. "flags UNLIMITED approvals as HIGH risk", "scans all 8 chains in parallel") as annotations next to the corresponding commands, eliminating ~60 lines of duplicated command listings.

Use full rather than abbreviated addresses consistently in examples (0xd8dA...96045 appears alongside the full address elsewhere) so every example is directly runnable as written.

DimensionReasoningScore

Conciseness

The Pitfalls section is dense and genuinely non-obvious (e.g. the L2 gas estimates omitting the L1 data-posting fee) and no space is spent explaining concepts Claude already knows, but the ~60-line "Procedure" section re-lists commands already shown verbatim in "Quick Reference" (wallet, multichain, tx, decode, ens, whale, gas), which is unnecessary duplication; this fits anchor 3 (mostly efficient but could be tightened) better than 4.

3 / 5

Actionability

Every one of the 14 commands is copy-paste ready with real example inputs (vitalik.eth and its full address, a full transaction hash, USDC/USDT contract addresses), concrete flags (--chain, --blocks, --min-usd, --no-prices), and documented expected outputs, fully covering the common cases.

5 / 5

Workflow Clarity

The skill is a set of unambiguous single-action read-only commands, and the body supplies explicit checkpoints: a "Setup Check" (python --version, smoke-run stats), a "Verification" section stating what successful output should look like, and Pitfalls entries with error-recovery guidance ("re-run later or use a block explorer"); the destructive/batch cap does not apply since all operations are read-only.

5 / 5

Progressive Disclosure

The 55KB implementation correctly lives in the single one-level-deep bundle file (scripts/evm_client.py, verified to exist with 45 functions), SKILL.md stays a usage overview with clear section headers, the script path is signaled in Prerequisites, Quick Reference, and Verification, and there are no nested references; nothing that belongs in a separate file is inlined.

5 / 5

Total

18

/

20

Passed

Description

53%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 concise and names a distinct, well-scoped niche, but it lists capability nouns without action verbs and entirely omits any "when to use this" trigger guidance. Adding a Use-when clause and the natural terms users actually say (chain names, balance, price, transactions) would materially improve it.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks about an EVM wallet balance, token price, or gas fees on Ethereum, BSC, Base, Arbitrum, Polygon, Optimism, Avalanche, or zkSync."

Replace the bare noun list with concrete actions, e.g. "Query wallet portfolios, token metadata and prices, gas costs, ENS names, and recent transactions across 8 EVM chains."

Include the most common natural trigger terms (Ethereum, balance, price, transaction) so users phrasing requests in plain language still match.

DimensionReasoningScore

Specificity

"Read-only EVM client: wallets, tokens, gas across 8 chains" names the domain and three concrete capability areas ("wallets, tokens, gas"), but contains no action verbs, so it sits between anchor 2 (domain only, minimal actions) and anchor 3 (domain plus explicit actions); it is more informative than anchor 2 yet not comprehensive (ENS, whale detection, tx decoding are unstated).

3 / 5

Completeness

The "what" is clear (read-only queries of wallets, tokens, and gas across 8 chains), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines; not score 2 because the "what" is specific rather than vague.

3 / 5

Trigger Term Quality

Relevant keywords exist ("EVM", "wallets", "tokens", "gas", "chains") but common natural variations users would say are missing: no chain names (Ethereum, BSC, Base), no "balance", "price", "portfolio", or "transactions", matching anchor 3 (some relevant keywords, missing synonyms).

3 / 5

Distinctiveness Conflict Risk

"EVM" plus "across 8 chains" carves a clear niche that is distinguishable from the related solana skill, and "Read-only" further scopes it; only minor overlap risk remains because the generic nouns "wallets, tokens, gas" also apply to non-EVM chains, so anchor 4 fits better than 5.

4 / 5

Total

13

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/blockchain/evm/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.