Build production-ready Web3 applications, smart contracts, and decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations.
55
45%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/blockchain-developer/SKILL.mdQuality
Discovery
82%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 trigger term coverage, listing concrete Web3 capabilities with natural keywords users would use. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. The domain is distinctive enough to avoid conflicts with other skills.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about blockchain development, smart contracts, DeFi, NFTs, DAOs, or Web3 applications.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Build production-ready Web3 applications, smart contracts, and decentralized systems' and 'Implements DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations.' These are concrete, specific capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the domain terms. Per rubric guidelines, missing 'Use when' caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Web3', 'smart contracts', 'DeFi', 'NFT', 'DAOs', 'blockchain', 'decentralized'. These cover the major terms a user working in this domain would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Web3/blockchain/smart contracts is a very distinct niche. The specific terms like DeFi, NFT, DAOs, and smart contracts are unlikely to conflict with other skills. This has clear, unique triggers. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a comprehensive capability description or persona prompt rather than an actionable skill document. It exhaustively lists blockchain technologies, frameworks, and concepts Claude already knows, consuming enormous token budget without providing any concrete, executable guidance. The skill would benefit from being drastically reduced to focus on specific workflows, code templates, and validation steps for the most common blockchain development tasks.
Suggestions
Replace the extensive capability listings with 3-5 concrete, executable code examples for common tasks (e.g., deploying a Solidity contract with Hardhat, integrating Chainlink price feeds, setting up an ERC-20 token).
Add explicit multi-step workflows with validation checkpoints for critical operations like smart contract deployment, upgrade procedures, and security auditing — including specific commands and verification steps.
Remove the 'Capabilities', 'Behavioral Traits', 'Knowledge Base', and 'Example Interactions' sections entirely, as they describe what Claude already knows and consume tokens without adding actionable value.
Move detailed reference material (token standards, DeFi patterns, security checklists) into the referenced 'resources/implementation-playbook.md' bundle file and keep SKILL.md as a lean overview with clear pointers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and padded with extensive lists of technologies, concepts, and capabilities that Claude already knows. The 'Capabilities' section is essentially a resume listing dozens of blockchain technologies without providing any actionable guidance. The 'Behavioral Traits', 'Knowledge Base', and 'Example Interactions' sections add significant token cost with no instructional value. | 1 / 3 |
Actionability | Contains zero executable code, no concrete commands, no specific examples with inputs/outputs, and no copy-paste ready snippets. The entire skill is descriptive rather than instructive — it tells Claude what it should be capable of rather than showing how to do anything. The 'Instructions' section is four generic bullet points with no blockchain-specific guidance. | 1 / 3 |
Workflow Clarity | The 'Response Approach' section lists 8 high-level steps but they are vague and lack any validation checkpoints, error recovery, or concrete sequencing. For a skill involving smart contract development (which involves destructive/irreversible operations), there are no verification steps, no testing workflows, and no deployment checklists. | 1 / 3 |
Progressive Disclosure | There is a reference to 'resources/implementation-playbook.md' for detailed examples, which suggests some attempt at progressive disclosure. However, no bundle files are provided to verify this reference works, and the massive amount of content that should be in separate reference files is instead inlined in the SKILL.md body. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
90%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 | |
9d0b37c
Table of Contents
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.