blockchain-developer

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

Quality

45%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/blockchain-developer/SKILL.md

Quality

Content

25%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is a verbose persona-and-capability catalog that adds little beyond Claude's existing blockchain knowledge: it lacks executable code, concrete validation checkpoints, and working external references.

Suggestions

Replace the capability catalog with a concise overview and move detailed technology lists into reference files (e.g. references/smart-contracts.md, references/defi-patterns.md) that actually exist.

Add concrete executable guidance — example Hardhat/Foundry commands, a minimal ERC-20 template, or a deployment+verify script — instead of abstract 'implement production-ready code' steps.

Insert explicit validation/feedback checkpoints in the workflow (e.g. 'run `forge test` and only deploy when tests and slither audit pass') given the destructive/financial risk of contract work.

Dimension	Reasoning	Score
Conciseness	The body is a ~200-line catalog enumerating technologies and domain knowledge Claude already has (Solidity patterns, Solana/Cosmos/Polkadot/NEAR/Cardano, AMM mechanics, etc.) with no executable instruction, which is noticeably verbose padding rather than earned tokens.	2 / 5
Actionability	Guidance is high-level and abstract ('Analyze blockchain requirements', 'Implement production-ready code', 'Apply relevant best practices') with zero concrete code or commands; the only concrete pointer (resources/implementation-playbook.md) targets a non-existent file.	2 / 5
Workflow Clarity	The 8-step Response Approach is a rough abstract sequence with poorly defined steps and no concrete validation checkpoints or fix-retry feedback loops, which is inadequate for high-stakes/destructive contract deployment work.	2 / 5
Progressive Disclosure	No bundle files exist and the single reference (resources/implementation-playbook.md) is broken; the large Capabilities/Knowledge Base catalogs clearly belong in separate reference files but are inlined into the SKILL.md body.	2 / 5
	Total	8 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 uses correct third-person voice and names a coherent, distinctive blockchain/Web3 domain with strong trigger terms, but it lacks any explicit 'Use when' trigger guidance, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases (e.g. 'Use when building or auditing smart contracts, DeFi protocols, NFT marketplaces, or DAOs').

Include common user-facing synonyms (dApp, crypto, Solidity, Ethereum, Web3 dApp) to broaden trigger-term coverage.

Tighten capability phrasing from categories to concrete actions (e.g. 'write and audit Solidity contracts', 'deploy DeFi lending protocols') to lift specificity.

Dimension	Reasoning	Score
Specificity	Names several specific build targets ('Web3 applications, smart contracts, and decentralized systems', 'DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations') but each is a high-level category rather than granular concrete actions, leaving minor gaps versus a fully comprehensive action list.	4 / 5
Completeness	The 'what' is clear (builds Web3 apps, smart contracts, DeFi/NFT/DAO/enterprise systems) but there is no explicit 'Use when...' trigger clause, so per the judging guideline 'when' is missing and completeness is capped at 3.	3 / 5
Trigger Term Quality	Covers natural terms users actually say ('Web3', 'smart contracts', 'DeFi', 'NFT', 'DAO', 'blockchain') but omits common variations a user might say ('dApp', 'crypto', 'Solidity', 'Ethereum'), so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	The blockchain/Web3 niche is mostly distinct with concrete domain triggers, but the broad umbrella ('Web3 applications', 'smart contracts') creates minor overlap risk with narrower specialized skills (e.g. a dedicated smart-contract auditor or DeFi skill).	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/blockchain-developer/SKILL.md
Commit: 782f684

Reviewed: 7 minutes 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.