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 explicit trigger guidance. It uses third-person voice correctly, includes natural trigger terms covering both technical (ERC-721, ERC-1155) and common (NFT, digital asset) terminology, and has a well-structured 'Use when' clause. The description is concise yet comprehensive, making it easy for Claude to select appropriately.
| 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 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 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 is essentially a code cookbook for NFT standards—it provides many complete, executable Solidity examples but lacks any workflow guidance, deployment process, testing steps, or validation checkpoints. The content is far too verbose for a skill file, dumping ~300 lines of boilerplate Solidity that Claude largely already knows, while missing the operational guidance (how to deploy, test, verify) that would actually add value.
Suggestions
Add a clear workflow section with steps: write contract → compile → test → deploy to testnet → verify → deploy to mainnet, with validation checkpoints at each stage
Move the large contract implementations to the referenced asset files (assets/erc721-contract.sol, etc.) and keep only minimal code snippets inline showing key patterns and decision points
Remove boilerplate code Claude already knows (standard OpenZeppelin overrides, basic ERC-721 structure) and focus on the non-obvious patterns like the soulbound transfer hook, on-chain metadata encoding, and ERC721A gas optimization differences
Add concrete testing/validation commands (e.g., Hardhat/Foundry test commands, deployment scripts) to make the workflow actionable end-to-end
| 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 contract patterns, standard ERC-721/1155 implementations). The 'When to Use This Skill' section and marketplace bullet points add little value. | 1 / 3 |
Actionability | The code examples are fully 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 patterns with concrete implementations. | 3 / 3 |
Workflow Clarity | There is no workflow or sequencing guidance whatsoever. The skill presents code blocks without any deployment steps, testing instructions, validation checkpoints, or process for going from contract creation to deployment. For operations involving smart contract deployment (which are destructive/irreversible on mainnet), this is a significant gap. | 1 / 3 |
Progressive Disclosure | The Resources section references external files (references/*.md, assets/*.sol) which is good progressive disclosure, but the main body contains massive inline code blocks that could be split into separate reference files. The skill tries to cover too many patterns inline rather than providing a concise overview with links to detailed implementations. | 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
47823e3
- 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.