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 within a well-defined niche (ERC-8004 onchain agent registration). However, it lacks an explicit 'Use when...' clause, which caps completeness, and the trigger terms lean heavily technical without covering more natural language variations a user might employ.
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 language trigger terms such as 'blockchain identity', 'agent registration', '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 'blockchain identity', 'agent registration', or 'crypto wallet setup' that users might actually say. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: ERC-8004 agent registration, Identity Registry, and Doppel hub are highly distinctive terms unlikely to conflict with other skills. This is a clearly defined domain. | 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 concrete API examples throughout. However, it is significantly over-length — the conceptual explanation in section 1, the detailed reputation breakdown tables, the full subgraph query examples, and the summary section all add tokens without proportional value. The content would benefit greatly from splitting into a concise SKILL.md overview with references to separate files for contract ABIs, reputation details, and read-only query examples.
Suggestions
Remove or drastically shorten section 1 ('What ERC-8004 is') — Claude doesn't need a conceptual overview; the actionable steps already convey the purpose.
Extract contract ABIs, the reputation dimensions table, subgraph query examples, and read-only query code into a separate REFERENCE.md file, linking to it from the main skill.
Add explicit validation checkpoints: verify transaction receipt status before proceeding to hub reporting, and include error handling guidance if the hub PATCH returns a verification failure.
Remove the Summary section at the end — it repeats the numbered section headers verbatim and adds no new information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ 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 dimension table, and explanations of scoring concepts. 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 using viem, with concrete examples for wallet setup, registration, event parsing, URI updates, and reputation queries. | 3 / 3 |
Workflow Clarity | The steps are clearly sequenced (wallet → fund → register → report → update → check reputation) with numbered sections. However, there are no explicit validation checkpoints between critical steps — e.g., no verification that the registration transaction succeeded before proceeding to report to the hub, and no error recovery guidance if the transaction reverts or the hub verification fails. | 2 / 3 |
Progressive Disclosure | Everything is in a single monolithic file with no references to external documents. The contract addresses table, full subgraph query examples, reputation dimension tables, and read-only query examples could all be in separate reference files. The inline ABI definitions alone add significant bulk that could be externalized. | 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.