nft-standards

Implement ERC-721 and ERC-1155 NFT contracts with metadata and royalty hooks.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/ekremmkasap/jarvis --skill nft-standards-ekremmkasap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nft-standards
Source: https://github.com/ekremmkasap/jarvis/tree/main/server/agent_prompts/wshobson/plugins/blockchain-web3/skills/nft-standards
Command: npx skills add https://github.com/ekremmkasap/jarvis --skill nft-standards-ekremmkasap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Developers often struggle to implement NFT standards (ERC-721 and ERC-1155) with robust metadata handling, reliable minting flows, and seamless marketplace integration across platforms.

Core Features & Use Cases

  • ERC-721 and ERC-1155 templates with OpenZeppelin-backed security and compatibility
  • Metadata strategies: on-chain and off-chain, with royalty-ready hooks (EIP-2981) and royalty configuration
  • Use cases: creating collectible series, in-game assets, and multi-token marketplaces with standardized interfaces
  • Optional advanced capabilities: soulbound tokens, dynamic NFTs, and lazy minting support

Quick Start

Deploy the provided NFT templates to bootstrap a compliant ERC-721/ERC-1155 project.

Frequently Asked Questions about nft-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement ERC-721 and ERC-1155 contracts with proper metadata and minting?

ERC-721 and ERC-1155 implementation uses OpenZeppelin-backed templates to handle minting and metadata. You can deploy these standardized interfaces to bootstrap compliant NFT collections with reliable token URIs.

What is the difference between on-chain and off-chain NFT metadata?

On-chain NFT metadata stores token attributes directly in the contract, while off-chain metadata uses external URIs. This skill provides strategies for both approaches, including royalty-ready hooks for marketplace compatibility.

How do I configure NFT royalties for marketplace compatibility in Solidity?

NFT royalty configuration uses EIP-2981 standard hooks integrated into the Solidity contract. This ensures marketplace compatibility by providing standardized interfaces that platforms can query to enforce creator payouts.

Can I use OpenZeppelin templates to create multi-token marketplaces?

Yes, OpenZeppelin templates support creating multi-token marketplaces using ERC-1155 standardized interfaces. This allows you to manage in-game assets and collectible series within a single contract architecture.

Does this support advanced NFT use cases like soulbound tokens and lazy minting?

Yes, the implementation supports optional advanced capabilities including soulbound tokens, dynamic NFTs, and lazy minting. These features extend the base ERC-721 and ERC-1155 templates for specialized decentralized applications.

What's the best way to handle token URIs for collectible series?

Handling token URIs for collectible series requires standardized interfaces mapping to on-chain or off-chain metadata. This skill provides royalty-ready hooks and URI strategies ensuring broad platform compatibility.