スキル nft-standards
📦

nft-standards

安全

Implement NFT Smart Contracts

こちらからも入手できます: wshobson

Build secure NFT collections using ERC-721 and ERC-1155 standards with proper metadata, royalties, and marketplace integration.

対応: Claude Codex Code(CC)
🥉 75 ブロンズ
1

スキルZIPをダウンロード

2

Claudeでアップロード

設定 → 機能 → スキル → スキルをアップロードへ移動

3

オンにして利用開始

テストする

「nft-standards」を使用しています。 Create an ERC-721 contract with minting

期待される結果:

  • Complete Solidity contract using OpenZeppelin ERC721URIStorage
  • Minting function with quantity limits and payment validation
  • URI generation for IPFS metadata
  • Withdraw function for collecting payments

「nft-standards」を使用しています。 Add royalties to my NFT collection

期待される結果:

  • IERC2981 implementation for royalty standard
  • Royalty fee configuration (default 5-10%)
  • Marketplace integration notes for OpenSea, LooksRare

セキュリティ監査

安全
v1 • 2/24/2026

All 38 static findings are false positives. The skill contains educational Solidity code examples for NFT standards (ERC-721, ERC-1155). The 'require' statements are standard contract validation, 'IERC2981' references are legitimate royalty standards, and 'shell command' flags are misclassified Solidity syntax. This is a legitimate developer tool for NFT smart contract development.

1
スキャンされたファイル
398
解析された行数
0
検出結果
1
総監査数
セキュリティ問題は見つかりませんでした
監査者: claude

品質スコア

38
アーキテクチャ
100
保守性
85
コンテンツ
50
コミュニティ
100
セキュリティ
100
仕様準拠

作れるもの

Create NFT Art Collection

Build a gas-optimized NFT collection with reveal mechanism and royalty distribution

Build Gaming Item System

Implement multi-token standard for game assets with varying supply and attributes

Create Credential System

Use soulbound tokens for non-transferable credentials and achievements

これらのプロンプトを試す

Basic NFT Contract
Create an ERC-721 NFT contract with OpenZeppelin. Include minting with payment, URI storage, and withdrawal function.
Gaming Items Contract
Implement an ERC-1155 contract for game items with max supply limits, batch minting, and burn functionality.
Royalty-Enabled Marketplace NFT
Create an NFT contract with EIP-2981 royalties, configurable fee recipient, and marketplace compatibility.
Dynamic Evolving NFT
Build a dynamic NFT that changes based on external state. Include experience points and level-up mechanics.

ベストプラクティス

  • Use OpenZeppelin contracts for battle-tested security
  • Pin IPFS metadata with a pinning service for reliability
  • Implement EIP-2981 royalties for marketplace compatibility
  • Use ERC721A for gas-optimized batch minting

回避

  • Storing images directly on-chain (use IPFS or external hosting)
  • Hardcoding royalty addresses without upgradeability
  • Skipping access controls on mint and burn functions
  • Not implementing supportsInterface for full compatibility

よくある質問

What is the difference between ERC-721 and ERC-1155?
ERC-721 is for unique non-fungible tokens where each token is one-of-a-kind. ERC-1155 is a multi-token standard that supports both fungible (currency) and non-fungible tokens in a single contract, ideal for gaming.
How do I add royalties to my NFT collection?
Implement the EIP-2981 royalty standard. This allows marketplaces like OpenSea and LooksRare to automatically calculate and distribute royalties on secondary sales.
What is IPFS and why do NFTs use it?
IPFS is a distributed file storage system. NFTs store metadata (images, attributes) on IPFS because it provides permanent, decentralized storage without a single point of failure.
Can NFTs be made non-transferable?
Yes, soulbound tokens (SBTs) use the _beforeTokenTransfer override to block transfers after minting. This is useful for credentials and achievements.
What is ERC721A and why is it popular?
ERC721A is a gas-optimized implementation of ERC-721 that reduces minting costs by up to 90% when minting multiple tokens in a single transaction.
Do I need to test NFT contracts before deployment?
Yes, always test thoroughly. Use tools like Hardhat or Foundry to write comprehensive test suites covering minting, transfers, approvals, and edge cases.

開発者の詳細

ファイル構成

📄 SKILL.md