erc8004

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/erc8004/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 very specific and niche capability (ERC-8004 Trustless Agents on Ethereum), which gives it strong distinctiveness. However, it lacks a 'Use when...' clause entirely, provides only a single action rather than listing multiple concrete capabilities, and misses natural language trigger terms that users might employ when needing this skill.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to register an AI agent on Ethereum, deploy an ERC-8004 contract, or set up on-chain agent identity.'

Include natural trigger term variations such as 'blockchain identity', 'on-chain agent', 'smart contract registration', 'decentralized agent identity', and 'agent DID'.

List additional concrete actions beyond registration, such as 'query registered agents', 'verify agent identity on-chain', or 'deploy ERC-8004 contracts'.

Dimension	Reasoning	Score
Specificity	Names a specific domain (Ethereum, ERC-8004) and a single action ('Register AI agent identity'), but does not list multiple concrete actions or elaborate on sub-capabilities like querying, updating, or verifying registrations.	2 / 3
Completeness	Describes what the skill does (register AI agent identity via ERC-8004) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant technical keywords like 'ERC-8004', 'Ethereum', 'AI agent identity', and 'Trustless Agents', but misses common natural variations users might say such as 'on-chain identity', 'agent registration', 'smart contract', 'blockchain identity', or 'decentralized identity'.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the very specific standard (ERC-8004) and narrow use case (AI agent identity registration on Ethereum). Unlikely to conflict with other skills given the niche domain.	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.

The skill is concise and well-organized with useful reference information like contract addresses and command syntax. However, it lacks a clear end-to-end workflow with validation steps for what is a financially consequential on-chain operation, and the slash commands assume a specific tooling context without explaining the underlying mechanism or providing fallback executable code.

Suggestions

Add a step-by-step registration workflow with explicit validation checkpoints (e.g., verify wallet balance, confirm transaction hash, verify on-chain registration via lookup command)

Provide executable code (e.g., using ethers.js, viem, or cast) as a fallback for interacting with the contracts directly, since the slash commands assume specific tooling

Add error handling guidance for common failure modes (insufficient gas, nonce issues, failed transactions) given this involves real ETH

Dimension	Reasoning	Score
Conciseness	The content is lean and well-structured. The brief 'What is ERC-8004?' section is borderline but provides genuinely useful context (registry types) rather than explaining concepts Claude already knows. Every section earns its place.	3 / 3
Actionability	The skill provides concrete commands and a JSON format, but the commands appear to be slash commands for a specific tool/plugin without explaining how they connect to actual on-chain transactions. There's no executable code showing how to interact with the smart contracts directly (e.g., using ethers.js or cast), and the setup section is minimal with just environment variables.	2 / 3
Workflow Clarity	The commands are listed but there's no clear sequential workflow for registration (e.g., setup wallet → fund with ETH → register → verify registration). For an operation involving real ETH and on-chain transactions, there are no validation checkpoints, error handling guidance, or confirmation steps to verify the registration succeeded.	2 / 3
Progressive Disclosure	The content is reasonably organized with clear sections, but everything is inline in a single file. The contract addresses table, registration format, and detailed command reference could be split into separate files. However, the skill is short enough (~60 lines) that this is a minor issue. No references to external documentation files are provided despite linking to the website.	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: 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.