blockchain-developer
Build production-ready Web3 applications, smart contracts, and decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill blockchain-developer55
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 is a strong description with excellent specificity and domain-relevant trigger terms that users would naturally use. The main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions blockchain, cryptocurrency, Web3, smart contracts, Solidity, Ethereum, or decentralized 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 through the domain terms. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Web3', 'smart contracts', 'DeFi', 'NFT', 'DAOs', 'blockchain' - these are all terms users naturally use when requesting blockchain development work. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche in blockchain/Web3 development with distinct terminology (DeFi, NFT, DAOs, smart contracts) that is unlikely to conflict with other skills - this is a specialized domain. | 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 or capability manifest rather than actionable development guidance. It exhaustively lists blockchain technologies, frameworks, and concepts that Claude already understands, without providing any concrete code, commands, or step-by-step workflows. The content would be more appropriate as a job posting than as instructions for completing blockchain development tasks.
Suggestions
Replace capability lists with concrete, executable code examples for common tasks (e.g., deploying a smart contract with Hardhat, integrating Chainlink oracles, setting up a basic ERC-20 token)
Add specific workflow sequences with validation checkpoints for critical operations like smart contract deployment, security auditing, and cross-chain bridge setup
Remove sections that describe what Claude already knows (e.g., what DeFi is, what NFTs are) and focus on project-specific patterns, gotchas, and non-obvious implementation details
Include concrete command-line examples for tooling setup (Foundry, Hardhat) and common debugging/testing workflows with expected outputs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive lists of technologies, concepts, and capabilities that Claude already knows. The content reads like a job description or marketing material rather than actionable instructions, with massive sections explaining what blockchain development involves rather than how to do specific tasks. | 1 / 3 |
Actionability | No concrete code examples, commands, or executable guidance anywhere in the skill. Content is entirely descriptive ('Masters both traditional blockchain patterns...', 'Solidity development with advanced patterns...') without any actual implementation details or copy-paste ready snippets. | 1 / 3 |
Workflow Clarity | The 'Response Approach' section lists generic steps like 'Analyze blockchain requirements' and 'Design system architecture' but provides no specific sequences, validation checkpoints, or feedback loops. No clear workflow for any actual blockchain development task. | 1 / 3 |
Progressive Disclosure | References `resources/implementation-playbook.md` for detailed examples, which is appropriate progressive disclosure. However, the main content is a monolithic wall of capability lists that could be better organized, and it's unclear what the referenced file actually contains. | 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 | |
- 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.