Skills nft-standards
๐Ÿ“ฆ

nft-standards

Content revision r2 Medium Risk โšก Contains scriptsโš™๏ธ External commands

Build Standards-Compliant NFT Contracts

NFT contracts require careful choices across token standards, metadata, royalties, and minting. This skill provides practical Solidity patterns and implementation guidance.

Supports: Claude Codex Code(CC)
๐Ÿ“Š 69 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "nft-standards" from https://skillstore.io/skills/sickn33-nft-standards.md and its manifest at https://skillstore.io/api/skills/sickn33-nft-standards/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "nft-standards". Which standard fits a game with fungible potions and unique swords?

Expected outcome:

Use ERC-1155 for shared item types and efficient batches. Use ERC-721 separately when every sword needs unique ownership and metadata.

Using "nft-standards". Review a soulbound achievement token design.

Expected outcome:

  • Restrict minting to approved issuers.
  • Define whether holders may burn tokens.
  • Block transfers while preserving mint and burn operations.
  • Document revocation, privacy, and recipient consent.

Security Audit

Medium Risk
v5 โ€ข 8/4/2026 Open versioned report

All static alerts are false positives caused by Solidity require statements and Markdown backticks, with no host command execution present. Two example contracts contain genuine business logic risks involving unrestricted progression and soulbound token minting.

1
Files scanned
404
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (2)

Medium
Unrestricted Dynamic NFT Progression
The token owner supplies any experience amount, allowing arbitrary level progression without an authorized game or verified update source.
The external function accepts an unbounded experience value and directly applies it after checking only token ownership.
Medium
Unrestricted Soulbound Token Issuance
Any caller can mint a non-transferable token to any address, enabling unsolicited issuance and credential spoofing if the token represents identity.
The mint function is external and has no issuer authorization or recipient consent check.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-nft-standards/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-nft-standards/security.svg)](https://skillstore.io/skills/sickn33-nft-standards?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-nft-standards?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-nft-standards/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-nft-standards.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

sickn33. (2026). nft-standards security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-nft-standards/audits/5

BibTeX citation

@techreport{sickn33-sickn33-nft-standards-2026, author = {sickn33}, title = {nft-standards security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-nft-standards/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "nft-standards security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-08-04" url: "https://skillstore.io/skills/sickn33-nft-standards/audits/5" identifiers: - type: other value: "skillstore:sickn33-nft-standards:audit:5" description: "Skillstore immutable audit report identifier"

Compare variants

2 installable variants

Each author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.

Why this variant is first

Highest Skillstore Score
wshobson Recommended

wshobson-nft-standards

Skillstore Score 78
Evidence Confidence High
Skillstore usage 11
Updated

2026-08-21

sickn33 Current

sickn33-nft-standards

Skillstore Score 69
Evidence Confidence High
Skillstore usage 8
Updated

2026-08-21

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Plan a Digital Art Collection

Compare ERC-721 designs, metadata storage, supply limits, mint pricing, and royalty support.

Model Multi-Token Game Items

Design ERC-1155 item types, batch minting, burning, supply controls, and shared metadata.

Review an NFT Architecture

Check token standards, metadata choices, transfer rules, royalties, and gas optimization before implementation.

Try These Prompts

Choose an NFT Standard
Compare ERC-721 and ERC-1155 for [project]. Consider asset uniqueness, editions, batch transfers, metadata, and marketplace compatibility.
Design Collection Metadata
Design metadata for [collection] using [IPFS or on-chain storage]. Include traits, image handling, update policy, and marketplace compatibility.
Draft a Minting Contract
Draft an educational [ERC-721 or ERC-1155] contract for [requirements]. Include supply limits, access control, payments, events, and testing notes.
Review an Advanced NFT Design
Review this NFT design: [design]. Analyze authorization, supply accounting, metadata integrity, royalties, transfer restrictions, gas costs, and upgrade risks.

Best Practices

  • Pin dependency versions and match examples to the selected library release.
  • Test authorization, supply boundaries, payment handling, metadata, and interface support.
  • Obtain an independent security review before deploying contracts that manage assets or payments.

Avoid

  • Do not deploy tutorial snippets without compilation, tests, and security review.
  • Do not allow public state updates when an authorized issuer or oracle should control them.
  • Do not rely on marketplace royalty enforcement without documenting its limitations.

Frequently Asked Questions

When should I use ERC-721?
Use ERC-721 when each token is individually owned and needs a unique identifier or metadata record.
When should I use ERC-1155?
Use ERC-1155 for multiple token types, editions, fungible items, or efficient batch transfers.
Does this skill produce deployment-ready contracts?
No. The examples require dependency alignment, compilation, tests, threat modeling, and independent security review.
Can metadata be stored on-chain?
Yes. On-chain metadata improves availability but increases gas costs and requires careful encoding.
Are EIP-2981 royalties guaranteed?
No. EIP-2981 reports royalty information, but marketplaces decide whether to pay or enforce royalties.
Can this skill audit an existing contract?
It can support structured review, but it does not replace automated tests, specialist audits, or deployed contract analysis.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

81e05e636292629114b76cbb3922fbe57672fc02

Maintenance freshness

8/5/2026

Usage

7 downloads ยท 138 views

File structure

๐Ÿ“„ SKILL.md

More from sickn33

View all
View all