nft-standards

Master ERC-721 and ERC-1155 NFT standards, metadata best practices, and advanced NFT features.

Quality

40%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/nft-standards/SKILL.md

Quality

Content

43%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides substantial, executable Solidity code covering multiple NFT standards, which is its primary strength. However, it is excessively verbose by inlining full contract implementations that should live in referenced asset files, and it completely lacks workflow guidance—there are no sequenced steps, deployment instructions, or validation checkpoints for what are irreversible on-chain operations. The content reads more like a code reference library than an actionable skill.

Suggestions

Add a clear workflow section with numbered steps: design metadata → write/customize contract → test locally (Hardhat/Foundry) → deploy to testnet → verify contract → deploy to mainnet, with validation at each step.

Move full contract implementations to the referenced asset files (assets/erc721-contract.sol, etc.) and keep only minimal inline snippets showing key patterns or differences between standards.

Add explicit validation/verification steps: compile checks, test commands, deployment verification (e.g., `npx hardhat verify`), and metadata validation against OpenSea's standards.

Remove the 'Do not use this skill when' boilerplate and trim the 'Use this skill when' section to save tokens for more actionable content.

Dimension	Reasoning	Score
Conciseness	The skill is very long (~300+ lines) with extensive inline code that could be in referenced files. Multiple full contract implementations are inlined when they should be in assets/references. The 'Do not use this skill when' and 'Use this skill when' sections add little value. Claude already knows Solidity patterns and OpenZeppelin usage.	2 / 5
Actionability	The code examples are concrete, executable Solidity contracts using real OpenZeppelin imports. They cover ERC-721, ERC-1155, royalties, soulbound tokens, dynamic NFTs, and ERC721A. Minor gaps: some functions return empty strings (generateSVG, generateMetadata) and the metadata uploader is only referenced, not shown.	4 / 5
Workflow Clarity	There is no clear workflow or sequenced process for creating and deploying an NFT collection. The content is a collection of code snippets without steps connecting them. No validation checkpoints, no deployment verification, no testing steps. For operations involving smart contract deployment (destructive/irreversible on-chain), the absence of validation and verification is a significant gap.	2 / 5
Progressive Disclosure	The Resources section references multiple external files (references/, assets/) which is good structure, but no bundle files are provided so these references are unverifiable. Meanwhile, massive code blocks that belong in those referenced asset files are inlined in the SKILL.md, defeating the purpose of the separation. The skill would benefit from keeping only a brief example inline and pushing full contracts to the referenced files.	3 / 5
	Total	11 / 20 Passed

Description

36%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies the NFT domain and names specific standards (ERC-721, ERC-1155), which is helpful, but it reads more like a course title than a skill description. It lacks concrete actions, uses imperative/instructional voice ('Master...'), and completely omits a 'Use when...' clause, making it difficult for Claude to know when to select this skill over others.

Suggestions

Replace the imperative 'Master' framing with concrete third-person actions, e.g., 'Implements ERC-721 and ERC-1155 smart contracts, generates token metadata JSON, configures royalties, and deploys NFT collections.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about NFTs, minting tokens, non-fungible tokens, token metadata, ERC-721, ERC-1155, or NFT marketplace integration.'

Include common synonyms and related terms users might say, such as 'non-fungible token,' 'minting,' 'token URI,' 'OpenSea metadata,' 'collectibles,' or 'Solidity NFT contract.'

Dimension	Reasoning	Score
Specificity	Names the domain (NFT standards ERC-721, ERC-1155) and mentions 'metadata best practices' and 'advanced NFT features,' but these are vague categories rather than concrete actions. No specific actions like 'deploy,' 'mint,' 'generate metadata JSON,' or 'implement royalties' are listed.	2 / 5
Completeness	The 'what' is vaguely stated as mastering standards and best practices, but there is no 'when' clause at all. The description lacks any explicit trigger guidance for when Claude should select this skill, which per the rubric should cap completeness at 3 maximum, and the weak 'what' brings it to 2.	2 / 5
Trigger Term Quality	Includes relevant keywords like 'ERC-721,' 'ERC-1155,' 'NFT,' and 'metadata,' which users might naturally mention. However, it misses common variations and synonyms such as 'non-fungible token,' 'minting,' 'token URI,' 'OpenSea,' 'collectibles,' or 'Solidity.'	3 / 5
Distinctiveness Conflict Risk	The mention of ERC-721 and ERC-1155 provides some specificity to the NFT domain, but 'advanced NFT features' is broad enough to overlap with general Solidity/smart contract skills or broader blockchain skills. It's somewhat specific but not clearly carved out.	3 / 5
	Total	10 / 20 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/nft-standards/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.