doppel-erc-8004
Register your agent onchain with ERC-8004. Set up a wallet, fund it, register on the Identity Registry, and link your onchain identity back to the Doppel hub for verifiable reputation and token allocation.
68
55%
Does it follow best practices?
Impact
96%
2.74xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xm1kr/doppel-erc-8004/SKILL.mdQuality
Discovery
67%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 strong in specificity and distinctiveness, clearly listing concrete actions and occupying a unique niche around ERC-8004 onchain agent registration. However, it lacks an explicit 'Use when...' clause and could benefit from more natural trigger terms that users would actually say when needing this skill.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to register an agent onchain, set up blockchain identity, or work with ERC-8004.'
Include more natural user-facing trigger terms such as 'agent registration', 'blockchain identity', 'onchain identity', or 'crypto wallet' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: set up a wallet, fund it, register on the Identity Registry, and link onchain identity back to the Doppel hub. Also mentions specific outcomes: verifiable reputation and token allocation. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with the list of actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the nature of the actions described. | 2 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'ERC-8004', 'onchain', 'wallet', 'Identity Registry', and 'Doppel hub', but these are fairly technical. Missing more natural user terms like 'agent registration', 'blockchain identity', or 'crypto wallet setup' that users might actually say. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: ERC-8004 agent registration with the Doppel hub. The combination of ERC-8004, Identity Registry, and Doppel hub creates a highly distinct set of triggers unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability with fully executable TypeScript code, real contract addresses, and complete API examples. However, it is significantly over-length, combining what should be a concise overview with extensive reference material (reputation schemas, dimension tables, subgraph queries) all in one file. The workflow lacks explicit validation checkpoints between critical steps involving real ETH and permanent onchain state.
Suggestions
Extract sections 7 (reputation details, dimensions table) and 8 (contract addresses, onchain query examples, subgraph queries) into separate reference files and link to them from the main skill.
Remove section 1 entirely — Claude doesn't need an explanation of what ERC-8004 is or why identity matters; the skill title and steps already convey this.
Add explicit validation checkpoints: verify transaction receipt status before proceeding to hub reporting, and add a retry/error-handling flow if hub verification fails.
Remove the summary section at the end — it repeats the section headers and adds no new information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines. Section 1 explains what ERC-8004 is and why it matters — concepts that are contextual background, not actionable instructions. The reputation section includes lengthy JSON response examples, a full dimensions table, and explanations of what averageScore means. The summary at the end repeats everything. Much of this could be cut or moved to reference files. | 1 / 3 |
Actionability | Every step includes fully executable TypeScript code with real contract addresses, ABIs, and specific API endpoints. The code is copy-paste ready with viem, includes gas estimation, transaction receipt parsing, and error handling patterns. API calls include both request and response examples. | 3 / 3 |
Workflow Clarity | The multi-step process is clearly sequenced (sections 2-5) with logical ordering. However, there are no explicit validation checkpoints between steps — for example, no verification that the registration transaction succeeded before proceeding to report to the hub, and no feedback loop if the hub verification fails. For an operation involving real money (ETH) and permanent onchain state, this is a gap. | 2 / 3 |
Progressive Disclosure | Everything is in a single monolithic file with no references to separate documents for detailed content. The reputation dimensions table, subgraph query examples, contract verification details, and onchain query examples could all be in separate reference files. The resources section at the end links to external sites but not to any companion skill files. | 1 / 3 |
Total | 7 / 12 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- Demerzels-lab/elsamultiskillagent
- Commit
45f9fac
- 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.