blockchain-developer

Build production-ready Web3 applications, smart contracts, and decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations.

Quality

41%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/blockchain-developer/SKILL.md

Quality

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, Solidity, DeFi protocols, NFTs, DAOs, or Web3 integration.'

Consider adding file extensions or framework names as trigger terms (e.g., '.sol', 'Solidity', 'Hardhat', 'ethers.js', 'ERC-20', 'ERC-721') to improve trigger term coverage for more specific queries.

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. The 'when' is only implied by the domain terms, which caps this at 2 per the rubric guidelines.	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 terms like DeFi, NFT, DAO, and blockchain are unlikely to conflict with other skills. This has a clear, well-defined domain.	3 / 3
	Total	11 / 12 Passed

Implementation

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 persona description or capability catalog rather than an actionable skill document. It exhaustively lists blockchain technologies and concepts Claude already knows without providing any concrete code, commands, workflows, or decision frameworks. The content is almost entirely wasted tokens — it would be more effective as a 10-line skill with specific patterns, code templates, and validation steps for common blockchain development tasks.

Suggestions

Replace the extensive capability lists with 3-5 concrete, executable code examples for the most common tasks (e.g., deploying a Solidity contract with Hardhat, integrating Chainlink price feeds, setting up an upgradeable proxy).

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 'Behavioral Traits', 'Knowledge Base', 'Example Interactions', and most of the 'Capabilities' bullet lists — these describe what Claude already knows and waste context window space.

Create actual bundle files (e.g., security-checklist.md, deployment-workflow.md, common-patterns.md) with detailed reference content, and keep SKILL.md as a concise overview pointing to them.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive lists of technologies, frameworks, and concepts that Claude already knows. The 'Capabilities' section is essentially a resume listing dozens of blockchain topics without adding actionable knowledge. Sections like 'Behavioral Traits', 'Knowledge Base', and 'Example Interactions' are padding that consume tokens without teaching Claude anything new.	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 providing concrete guidance on how to do anything. The 'Response Approach' is a generic checklist of abstract steps.	1 / 3
Workflow Clarity	No clear multi-step workflows are defined. The 'Response Approach' lists 8 abstract steps without validation checkpoints, error recovery, or concrete sequencing. For a skill involving smart contract development (which involves destructive/irreversible operations), the complete absence of validation steps and feedback loops is a critical gap.	1 / 3
Progressive Disclosure	The content is a monolithic wall of bullet-pointed lists with no meaningful structure for navigation. It references `resources/implementation-playbook.md` once but no bundle files are provided. The massive inline content (capabilities, traits, knowledge base, examples) should be split into separate reference files but instead creates an overwhelming single document.	1 / 3
	Total	4 / 12 Passed

Validation

90%

Warnings & errors only

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: 8854d4e

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

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.