blockchain-developer

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

Quality

40%

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

12%Weight 40%Scale 1-3

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

The content reads as a bloated persona/competency catalog rather than actionable guidance: it explains blockchain domains Claude already knows, offers no executable code or validation steps, and references a non-existent file. It needs to be collapsed into lean, concrete instructions with real reference files.

Suggestions

Cut the persona, "Behavioral Traits", and "Knowledge Base" sections, which restate concepts Claude already knows; keep only non-obvious, skill-specific guidance.

Replace abstract capability lists with concrete, executable examples (e.g., a Hardhat/Foundry deploy snippet, an OpenZeppelin contract skeleton, a slither check command).

Add validation/verification checkpoints to the "Response Approach" workflow (e.g., run tests, run static analysis, verify on testnet before mainnet) and create the referenced "resources/implementation-playbook.md" so the link resolves.

Dimension	Reasoning	Score
Conciseness	The body is padded with long competency lists, a persona paragraph, "Knowledge Base" of general facts, and "Behavioral Traits" that largely restate concepts Claude already knows, violating token efficiency.	1 / 3
Actionability	It describes rather than instructs: there is no executable code, no concrete commands, and the "Instructions" section is generic ("Apply relevant best practices and validate outcomes") rather than copy-paste ready.	1 / 3
Workflow Clarity	The "Response Approach" lists an 8-step sequence, but there are no validation checkpoints, feedback loops, or concrete verification commands for risky operations like contract deployment.	2 / 3
Progressive Disclosure	The body is a monolithic wall of text with most material inlined; the one referenced file ("resources/implementation-playbook.md") does not exist in the bundle, leaving a broken reference and no real offloaded detail.	1 / 3
	Total	5 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 specific and occupies a clear, distinctive niche, but it omits an explicit "Use when..." trigger clause, leaving the "when to use it" half only implied. Adding natural trigger phrasing would lift completeness and trigger-term quality.

Suggestions

Append an explicit "Use when..." clause naming user-spoken triggers (e.g., building smart contracts, DeFi protocols, NFT marketplaces, DAOs, or Web3 dApps).

Soften jargon-heavy terms with natural variations a user would actually say ("crypto app", "Ethereum contract", "token") to improve trigger-term quality.

Keep the concrete action list but ensure every capability maps to a recognizable user request.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: "Build production-ready Web3 applications, smart contracts, and decentralized systems" plus "Implements DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations."	3 / 3
Completeness	Clearly answers "what" the skill does but provides no explicit "when to use it" trigger clause, which caps completeness at 2 per the judging guidelines.	2 / 3
Trigger Term Quality	Includes relevant domain terms (Web3, smart contracts, DeFi, NFT, DAO, blockchain) but leans technical and lacks common user-spoken variations or an explicit "Use when..." trigger phrase.	2 / 3
Distinctiveness Conflict Risk	The blockchain/Web3 niche is distinct with specialized triggers (DeFi, NFT, DAO, smart contracts) that make it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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: c0bd5d6

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