nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
83
64%
Does it follow best practices?
Impact
95%
1.37xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/blockchain-web3/skills/nft-standards/SKILL.mdQuality
Discovery
100%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 skill description that clearly defines its scope around NFT implementation, lists specific standards and capabilities, and includes an explicit 'Use when' clause with natural trigger terms. It effectively differentiates itself from general smart contract or blockchain skills through its NFT-specific terminology and use cases.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: implementing NFT standards (ERC-721, ERC-1155), metadata handling, minting strategies, and marketplace integration. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement NFT standards with metadata handling, minting strategies, marketplace integration) and 'when' (explicit 'Use when' clause covering creating NFT contracts, building NFT marketplaces, or implementing digital asset systems). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'NFT', 'ERC-721', 'ERC-1155', 'minting', 'NFT marketplace', 'digital asset', 'NFT contracts'. These cover both technical and common user terminology well. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around NFT-specific standards and patterns. The mention of ERC-721, ERC-1155, minting, and marketplace integration creates a well-defined scope unlikely to conflict with general Solidity or smart contract skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
29%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides extensive, executable Solidity code examples covering multiple NFT standards, which is its primary strength. However, it is severely over-long and monolithic, dumping ~300 lines of boilerplate contracts that Claude can largely generate from brief prompts. It critically lacks any workflow guidance—no deployment steps, testing procedures, or validation checkpoints for smart contract development, which involves irreversible on-chain operations.
Suggestions
Drastically reduce code examples to key patterns, gotchas, and non-obvious details (e.g., required overrides, gas optimization tips) rather than full contract implementations that Claude can generate.
Add a deployment and verification workflow with explicit steps: compile → test → deploy to testnet → verify → deploy to mainnet, with validation checkpoints at each stage.
Split detailed contract implementations into separate reference files (e.g., ERC721_PATTERNS.md, ERC1155_PATTERNS.md, ROYALTIES.md) and keep SKILL.md as a concise overview with navigation links.
Add common pitfalls and security considerations (reentrancy in minting, front-running, metadata immutability) since these are the non-obvious details Claude would benefit from most.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, mostly consisting of large code blocks that cover many different NFT patterns (ERC-721, ERC-1155, royalties, soulbound, dynamic, ERC721A). Much of this is boilerplate that Claude already knows or can generate from brief instructions. The 'When to Use' section lists obvious use cases. The content could be reduced to key patterns and gotchas rather than full contract implementations. | 1 / 3 |
Actionability | The code examples are concrete, executable Solidity contracts with proper imports, constructor definitions, and function implementations. They are copy-paste ready and cover real-world patterns including supply limits, payment validation, and required overrides. | 3 / 3 |
Workflow Clarity | There is no workflow or sequencing guidance whatsoever. The skill presents isolated code blocks with no deployment steps, no testing instructions, no validation checkpoints, and no guidance on how to verify contracts work correctly. For smart contract development (which involves destructive/irreversible operations on-chain), this is a significant gap. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of code blocks with no references to external files, no layered organization, and no navigation aids. All patterns are dumped inline at the same level of detail. Content like the full ERC-1155 or Dynamic NFT implementations could easily be split into separate reference files. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
112197c
- 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.