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.
78
68%
Does it follow best practices?
Impact
93%
1.24xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/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 with specific standards, concrete actions, and an explicit 'Use when' clause. It uses appropriate trigger terms that users would naturally use and occupies a distinct niche that minimizes conflict with other skills. The description is concise yet comprehensive.
| 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 niche focused specifically on NFT standards and marketplace integration. The mention of specific standards (ERC-721, ERC-1155) and NFT-specific concepts makes it very unlikely to conflict with general smart contract or other blockchain skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, executable Solidity code examples covering the major NFT standards and patterns, which is its primary strength. However, it is excessively verbose with boilerplate code that Claude already knows, lacks any workflow guidance for the multi-step process of developing and deploying NFT contracts, and references bundle files that don't exist. The content reads more like a reference catalog than an actionable skill guide.
Suggestions
Add a clear workflow section covering the development lifecycle: setup → implement → test → deploy → verify, with explicit validation checkpoints (e.g., run tests before deployment, verify on block explorer after deployment).
Drastically reduce code verbosity by moving full contract implementations to referenced asset files and keeping only the non-obvious patterns, gotchas, and key decision points inline (e.g., the soulbound transfer hook, the ERC721A gas optimization rationale).
Provide the referenced bundle files (references/*.md, assets/*.sol) or remove the references to avoid dead links.
Replace the generic 'Best Practices' bullet list with specific, actionable guidance—e.g., show the Merkle tree whitelist pattern or the placeholder-to-reveal mechanism rather than just naming them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, mostly consisting of large code blocks that cover multiple NFT patterns. Much of this is boilerplate that Claude already knows (OpenZeppelin patterns, standard ERC-721/1155 implementations). The 'When to Use This Skill' section and marketplace bullet points add little value. The content could be reduced significantly by focusing on non-obvious patterns and gotchas. | 1 / 3 |
Actionability | The code examples are concrete, executable Solidity contracts with proper imports, constructors, and function implementations. They are copy-paste ready and cover ERC-721, ERC-1155, royalties, soulbound tokens, dynamic NFTs, and ERC721A with specific, working patterns. | 3 / 3 |
Workflow Clarity | There is no workflow or sequencing guidance whatsoever. The skill presents isolated code snippets without explaining how to go from project setup to deployment, how to test contracts, how to validate metadata, or how to handle the reveal mechanism mentioned in best practices. For contract development involving irreversible on-chain deployments, the absence of testing/validation steps is a significant gap. | 1 / 3 |
Progressive Disclosure | The Resources section references multiple files (references/*.md, assets/*.sol, assets/*.json, assets/*.py) suggesting good structure, but no bundle files are provided, making these references non-functional. The main file itself is monolithic with all code inline rather than appropriately split into referenced files, yet the references section shows intent for proper organization. | 2 / 3 |
Total | 7 / 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
- Dicklesworthstone/pi_agent_rust
- Commit
99da384
- 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.