blockchain-developer
Build production-ready Web3 applications, smart contracts, and decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations.
62
45%
Does it follow best practices?
Impact
90%
1.01xAverage score across 3 eval scenarios
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.
This description excels at specificity and trigger term coverage, listing a comprehensive set of Web3-related capabilities with natural keywords users would employ. 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, Solidity, DeFi protocols, NFTs, DAOs, or Web3 integration.'
Consider including file extensions or framework names as trigger terms (e.g., '.sol files', 'Solidity', 'Hardhat', 'ethers.js', 'ERC-20', 'ERC-721') to improve trigger term coverage for specific tooling requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and domains: 'Web3 applications, smart contracts, decentralized systems, DeFi protocols, NFT platforms, DAOs, enterprise blockchain integrations.' These are concrete, identifiable deliverables. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. 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 space would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Web3/blockchain/smart contracts is a very distinct niche. The specific terminology (DeFi, NFT, DAO, smart contracts) makes it highly unlikely to conflict with non-blockchain skills. | 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 content is essentially a persona description and capability catalog rather than an actionable skill. It lists hundreds of technologies and concepts Claude already knows without providing any concrete code, commands, specific patterns, or executable guidance. The content would need a fundamental restructuring to become useful—replacing descriptive lists with concrete implementation examples, security checklists, and validated workflows.
Suggestions
Replace the extensive capability lists with concrete, executable code examples for the most common tasks (e.g., a complete Hardhat deployment script, a secure ERC-20 template with tests, a Foundry testing workflow).
Add explicit validation workflows with checkpoints for critical operations like smart contract deployment: compile → test → audit → deploy to testnet → verify → deploy to mainnet, with specific commands at each step.
Remove 'Behavioral Traits', 'Knowledge Base', 'Capabilities' catalog sections entirely—these describe what Claude already knows. Replace with project-specific patterns, gotchas, and anti-patterns that add genuine value.
Add concrete security checklists with specific vulnerability patterns and their fixes (e.g., reentrancy guard code, access control patterns) rather than just naming the vulnerabilities.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive lists of technologies, concepts, and capabilities that Claude already knows. The content reads like a resume or marketing document rather than actionable instructions. Sections like 'Capabilities', 'Knowledge Base', 'Behavioral Traits' are entirely unnecessary padding that describe what Claude should already be capable of. | 1 / 3 |
Actionability | Contains zero executable code, no concrete commands, no specific examples with inputs/outputs. Everything is abstract description ('Solidity development with advanced patterns', 'Gas optimization techniques') rather than actionable instructions. The 'Example Interactions' section lists prompts but provides no actual implementation 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. There are no feedback loops for security-critical operations like smart contract deployment, which is especially concerning given the domain involves irreversible blockchain transactions. | 1 / 3 |
Progressive Disclosure | There is one reference to 'resources/implementation-playbook.md' for detailed examples, which shows some awareness of progressive disclosure. However, the main file is a monolithic wall of bullet-pointed lists that should be split into separate reference files, and the single external reference is vaguely signaled ('If detailed examples are required'). | 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 | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
d739c8b
- 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.