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 is essentially a code cookbook of NFT contract patterns dumped into a single file. While the code examples are high-quality and executable, the skill fails to add value beyond what Claude already knows about these well-documented standards. It lacks any workflow guidance for deployment/testing, is extremely verbose, and has no progressive disclosure structure.
Suggestions
Drastically reduce content to project-specific conventions, gotchas, and patterns Claude wouldn't already know—move full contract implementations to separate reference files linked from a concise overview.
Add a deployment/testing workflow with explicit validation steps (e.g., compile → test → deploy to testnet → verify → deploy to mainnet) including verification checkpoints.
Structure as a quick-reference overview with links to detailed files: e.g., [ERC721_PATTERNS.md], [ERC1155_PATTERNS.md], [METADATA.md], [DEPLOYMENT.md].
Focus on decision guidance (when to use ERC-721 vs ERC-1155 vs ERC721A) and common pitfalls rather than reproducing standard OpenZeppelin patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, mostly consisting of full contract implementations that Claude already knows how to write. It explains standard patterns (ERC-721, ERC-1155, EIP-2981) that are well-documented and within Claude's training data. Much of this could be condensed to key patterns, gotchas, and project-specific conventions. | 1 / 3 |
Actionability | The code examples are fully executable Solidity contracts with proper imports, complete function implementations, and realistic patterns. They are copy-paste ready and cover concrete use cases like minting, royalties, soulbound tokens, and dynamic NFTs. | 3 / 3 |
Workflow Clarity | There is no workflow or sequencing guidance whatsoever. The skill presents isolated contract snippets without explaining how to deploy, test, validate, or integrate them. For operations involving smart contract deployment (which are destructive/irreversible on mainnet), the complete absence of validation steps, testing guidance, or deployment workflows is a significant gap. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of code with no references to external files, no layered organization, and no navigation aids. All contract implementations are inline when they could be split into separate reference files, with the SKILL.md providing a concise overview and links. | 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
70444e5
- 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.