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.
Install with Tessl CLI
npx tessl i github:Demerzels-lab/elsamultiskillagent --skill doppel-erc-800474
Quality
63%
Does it follow best practices?
Impact
96%
2.74xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xm1kr/doppel-erc-8004/SKILL.mdDiscovery
50%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 excels at specificity and distinctiveness by naming concrete actions and using unique technical terminology (ERC-8004, Doppel hub). However, it critically lacks any 'Use when...' guidance, making it difficult for Claude to know when to select this skill. The trigger terms are also somewhat specialized and may miss how users naturally phrase requests.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to register an agent onchain, set up blockchain identity, or connect to Doppel.'
Include more natural language variations users might say, such as 'blockchain identity', 'crypto agent registration', 'onchain verification', or 'Web3 identity setup'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Set up a wallet, fund it, register on the Identity Registry, and link your onchain identity back to the Doppel hub.' These are clear, actionable steps. | 3 / 3 |
Completeness | Describes what the skill does well, but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance should cap completeness at 2, and this has no trigger guidance at all. | 1 / 3 |
Trigger Term Quality | Includes some relevant technical terms like 'ERC-8004', 'onchain', 'Identity Registry', 'Doppel hub', 'wallet', but these are fairly specialized. Missing common variations users might say like 'blockchain identity', 'crypto registration', or 'agent identity'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche with distinct terminology: 'ERC-8004', 'Identity Registry', 'Doppel hub' are unique identifiers that would not conflict with other skills. Clear domain boundary around onchain agent registration. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with complete executable code examples and clear workflow progression. The main weaknesses are moderate verbosity in explanatory sections and a monolithic structure that could benefit from splitting reference material into separate files. The validation checkpoints and error handling guidance are strong.
Suggestions
Move the 'What ERC-8004 is' section to a separate OVERVIEW.md or remove it entirely—Claude can infer protocol purpose from the registration steps
Extract contract ABIs and subgraph query examples into a separate REFERENCE.md file, keeping only the essential registration flow in the main skill
Add a conditional skip instruction at the start: 'If you already have a funded Base wallet, skip to section 4' (partially present but could be more prominent)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanations (e.g., 'Why it matters' section, explaining what ERC-8004 is when Claude can infer this from context). The wallet setup section is thorough but could be condensed for agents who already have wallets. However, the code examples are lean and the overall structure avoids excessive padding. | 2 / 3 |
Actionability | Excellent executable code throughout with complete TypeScript examples using viem. Every step has copy-paste ready code including wallet setup, registration, event parsing, and API calls. Contract addresses, ABIs, and specific endpoints are all provided. | 3 / 3 |
Workflow Clarity | Clear numbered sections with logical progression from wallet setup through registration to hub verification. Includes validation checkpoints (balance check before proceeding, verification response handling, gas estimation before transaction). The summary provides a clear checklist of the complete workflow. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the document is quite long (~350 lines) and could benefit from splitting detailed reference material (contract ABIs, subgraph queries) into separate files. The inline tables and extensive code examples make the main skill file heavier than necessary for an overview. | 2 / 3 |
Total | 10 / 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 | |
- 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.