ercdata
Store, verify, and manage AI data on the Ethereum blockchain (Base network) using the ERCData standard. Use when an agent needs to store data fingerprints on-chain, verify data integrity, create audit trails, manage access control for private data, or interact with the ERCData smart contract. Supports public and private storage, EIP-712 verification, snapshots, and batch operations.
94
93%
Does it follow best practices?
Impact
93%
2.32xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly communicates what the skill does, when to use it, and occupies a distinct niche. It provides specific concrete actions, includes a well-structured 'Use when' clause with multiple trigger scenarios, and uses domain-specific terminology that makes it easily distinguishable from other skills. The description is concise yet comprehensive, covering capabilities without unnecessary verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: store data fingerprints on-chain, verify data integrity, create audit trails, manage access control, interact with ERCData smart contract. Also mentions specific capabilities like public/private storage, EIP-712 verification, snapshots, and batch operations. | 3 / 3 |
Completeness | Clearly answers both 'what' (store, verify, manage AI data on Ethereum/Base using ERCData standard) and 'when' (explicit 'Use when' clause listing specific trigger scenarios like storing data fingerprints, verifying integrity, creating audit trails, managing access control). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Ethereum', 'blockchain', 'Base network', 'ERCData', 'on-chain', 'data integrity', 'audit trails', 'access control', 'smart contract', 'EIP-712', 'snapshots', 'batch operations'. Good coverage of both domain-specific and natural terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Ethereum blockchain (Base network), ERCData standard, EIP-712 verification. These are very specific technical domains unlikely to conflict with other skills. The combination of blockchain + AI data + specific standard makes it uniquely identifiable. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
87%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, concise skill that provides actionable CLI commands for blockchain data operations. Its main weakness is the lack of explicit validation/verification workflows after write operations—given that blockchain transactions are irreversible and cost gas, the skill should include steps to verify transaction success and handle failures. The progressive disclosure and conciseness are excellent.
Suggestions
Add a workflow section showing the store-then-verify pattern with explicit validation: e.g., 1) Store data, 2) Check transaction receipt/hash, 3) Verify with `verify` command, 4) Handle failure cases
Include error handling guidance for common failure modes: insufficient gas, missing PROVIDER_ROLE, transaction revert—especially since these are irreversible operations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what Ethereum, Base, or EIP-712 are—it assumes Claude knows. Every section serves a purpose with no padding or unnecessary exposition. | 3 / 3 |
Actionability | Provides fully executable CLI commands with all necessary flags, environment variable configuration, and concrete examples. Commands are copy-paste ready with clear flag patterns. | 3 / 3 |
Workflow Clarity | Commands are clearly listed but there's no explicit validation workflow or error recovery. For blockchain operations (which are destructive/irreversible), there should be validation checkpoints—e.g., verify after store, check transaction receipt, handle failed transactions. The privacy warning about calldata visibility is good but insufficient as a workflow safeguard. | 2 / 3 |
Progressive Disclosure | Clean overview structure with quick start, configuration, command reference table, and a clear pointer to references/api.md for the full contract API. One level deep, well-signaled. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.