nft-standards
Implement NFT standards with ERC-721 and ERC-1155
NFT builders need clear guidance on standards, metadata, and minting. This skill gives practical patterns for ERC-721, ERC-1155, and marketplace readiness.
Download the skill ZIP
Upload in Claude
Go to Settings → Capabilities → Skills → Upload skill
Toggle on and start using
Test it
Using "nft-standards". Help me design an ERC-1155 game item set with three item types and supply limits.
Expected outcome:
- Use fixed token IDs per item type to enable batch minting.
- Set max supply per ID and enforce it in mint functions.
- Host metadata at ipfs://.../{id}.json with clear attributes for rarity and power.
Using "nft-standards". What is the difference between ERC-721 and ERC-1155 for a gamingNFT project?
Expected outcome:
- ERC-721 treats each token as unique, ideal for one-of-one collectibles.
- ERC-1155 supports multiple quantities of the same item type, efficient for gaming.
- ERC-1155 reduces gas costs for batch transfers of multiple item types.
Using "nft-standards". How do I implement royalties that marketplaces will respect?
Expected outcome:
- Implement EIP-2981 royalty interface for marketplace compliance.
- Set royalty fee between 2.5% and 10% for standard marketplace support.
- Use OpenZeppelin ERC2981RoyaltyUI for frontend royalty display.
Security Audit
SafeThis skill contains only markdown documentation (SKILL.md) and JSON configuration files (skill-report.json). No executable code, scripts, network calls, filesystem access beyond its own files, or environment variable reads are present. All 50 static findings are false positives triggered by example Solidity code blocks in documentation. The flagged patterns (C2 keywords, weak crypto, dynamic require, shell backticks) are standard blockchain terminology and documentation formatting, not security threats. Users are not exposed to any data theft, code execution, or privacy risks.
Risk Factors
🌐 Network access (1)
📁 Filesystem access (1)
⚡ Contains scripts (12)
Quality Score
What You Can Build
Select a token standard
Compare ERC-721 and ERC-1155 for a new collection and choose the right model.
Design metadata schema
Define fields that display correctly across major NFT marketplaces and wallets.
Plan multi-token items
Set ERC-1155 item IDs, supplies, and mint rules for game assets.
Try These Prompts
Recommend ERC-721 or ERC-1155 for a 5,000 item art drop and explain tradeoffs.
List required and optional metadata fields for NFT JSON and note best practices for images and attributes.
Explain how to implement EIP-2981 royalties and suggest a safe fee cap.
Outline a dynamic NFT approach that updates metadata based on on-chain state changes.
Best Practices
- Use OpenZeppelin base contracts for standards compliance
- Keep metadata consistent and pinned on IPFS
- Document mint limits and royalty settings
Avoid
- Mixing ERC-721 and ERC-1155 without a clear need
- Changing metadata without a disclosure policy
- Storing large assets fully on-chain without cost justification
Frequently Asked Questions
Is this compatible with Claude, Codex, and Claude Code?
What are the limits of this skill?
Does it integrate with marketplace APIs?
Does it access my files or keys?
How do I troubleshoot missing metadata display?
How does it compare to a full audit tool?
Developer Details
Author
wshobsonLicense
MIT
Repository
https://github.com/wshobson/agents/tree/main/plugins/blockchain-web3/skills/nft-standardsRef
main
File structure
📄 SKILL.md