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, includes specific standards and actions, and provides explicit trigger guidance via a 'Use when' clause. It uses proper third-person voice and covers natural keywords that users would employ when seeking NFT-related help. 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.
The skill provides comprehensive, executable Solidity code examples covering the major NFT standards and patterns, which is its primary strength. However, it is excessively verbose for a skill file—most of these are standard OpenZeppelin patterns Claude already knows—and critically lacks any workflow guidance for deploying, testing, or validating these contracts. The content reads more like a code cookbook than an actionable skill with clear processes.
Suggestions
Add a deployment and testing workflow with explicit steps: compile, test with Hardhat/Foundry, deploy to testnet, verify, then deploy to mainnet—with validation checkpoints at each stage.
Move the large contract code blocks into the referenced asset files (assets/erc721-contract.sol, etc.) and keep only concise patterns, key decisions, and gotchas in the main SKILL.md.
Remove content Claude already knows well, such as standard OpenZeppelin override boilerplate and basic ERC-1155 patterns, and focus on project-specific decisions and non-obvious pitfalls.
Add validation guidance: how to verify metadata renders correctly on OpenSea, how to test royalty enforcement, and how to audit before mainnet deployment.
| 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 with concrete, working code. | 3 / 3 |
Workflow Clarity | There is no workflow or sequencing guidance whatsoever. The skill presents code blocks without explaining how to deploy, test, or validate contracts. 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 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 be both an overview and a complete reference, resulting in a monolithic document. | 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
6e3d68c
- 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.