Modern Ethereum & EVM Developer

PassAudited by ClawScan on May 10, 2026.

Overview

This is an instruction-only Ethereum developer reference with no code or required credentials, but users should review any remote skill files it fetches and require approval before real blockchain transactions.

This skill appears safe to install as an informational Ethereum development reference. Before using it for real deployments or payments, verify any remote SKILL.md files it fetches, never share private keys, use testnets or limited wallets, and require explicit approval for onchain transactions.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If the agent fetches those files, it may rely on content that was not included in this review.

Why it was flagged

The skill directs the agent to fetch external SKILL.md files from a remote domain. This is aligned with a modular documentation skill, but those remote instructions are not pinned in the reviewed artifact and may change later.

Skill content
For individual topics, fetch any of these directly: ... https://ethskills.com/why/SKILL.md ... https://ethskills.com/security/SKILL.md
Recommendation

Treat remotely fetched skill files as unreviewed content unless the user explicitly approves them; prefer pinned or reviewed copies for sensitive work.

What this means

A user could accidentally allow an agent with wallet access to spend funds, sign transactions, or interact with contracts without enough review.

Why it was flagged

The skill discusses autonomous Ethereum payments and agent transactions. This is purpose-aligned educational content, but it would become high-impact if combined with wallet/signing tools or real funds.

Skill content
Agent calls endpoint → gets 402 → signs EIP-3009 payment → retries with payment header ... Fully autonomous economic loop — no humans required.
Recommendation

Use testnets or isolated wallets for development, set spending limits, and require explicit user confirmation before any real transaction, deployment, or payment.