Name: nft-standards
Rating: 48.8 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

nft-standards

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

Quality

53%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/nft-standards/SKILL.md

The canonical home for this skill is nft-standards in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

47%Weight 40%Scale 1-5

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

The skill is a rich, actionable Solidity reference for NFT standards but functions as an inlined code dump with broken bundle references and no real workflow or validation guidance. It would benefit substantially from moving templates into the referenced (currently missing) files and adding a sequenced, validated deployment workflow.

Suggestions

Create the referenced bundle files (references/erc721.md, assets/erc721-contract.sol, etc.) and move the full contract templates out of SKILL.md, leaving concise overviews and links; this also fixes the broken references/implementation-playbook.md path.

Replace the generic "Instructions" boilerplate with a sequenced NFT deployment workflow (choose standard → implement contract → write/verify metadata → test → deploy → verify on marketplace) with explicit validation checkpoints before deploy.

Add verification steps around batch minting and fund withdrawal (e.g. test on a fork, verify max-supply guards, confirm royalty registration) since these are destructive/batch operations currently lacking feedback loops.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable Solidity with little explanatory padding, but it inlines ~390 lines of full contract implementations that belong in reference files. Not a 4 because the sheer inlined volume could be trimmed by offloading templates to bundle files.	3 / 5
Actionability	It provides concrete, copy-paste-ready contracts for ERC-721, ERC-1155, royalties, soulbound, dynamic, and ERC721A. Not a 5 because several helpers are stubs (generateSVG returns "...", generateMetadata returns "") leaving minor gaps.	4 / 5
Workflow Clarity	The "Instructions" section is generic boilerplate ("Clarify goals… Apply relevant best practices and validate outcomes") with no sequenced NFT workflow, and batch-minting code has no validation checkpoints. Not a 3 because there is no real step sequence, only vague guidance.	2 / 5
Progressive Disclosure	The body is a monolithic inlined code wall and the "Resources" section lists references/.md and assets/ files (plus resources/implementation-playbook.md) that do not exist, so references are broken. Not a 3 because content that clearly belongs in separate files is inlined and the signaled references are absent.	2 / 5
	Total	11 / 20 Passed

Description

60%Weight 40%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 a clear, distinctive niche but relies on generic verbs ("Master") and omits any explicit "Use when…" trigger guidance. It reads as a topic statement rather than a trigger-rich capability description.

Suggestions

Replace the generic verb "Master" with concrete actions, e.g. "Implement ERC-721/ERC-1155 contracts, design on-chain/off-chain metadata, and add royalties, soulbound, and dynamic-NFT features."

Add an explicit trigger clause: "Use when creating NFT collections, building marketplaces, or implementing ERC-721/ERC-1155 smart contracts."

Include natural synonyms such as "non-fungible token" and "smart contract" to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("ERC-721 and ERC-1155 NFT standards, metadata best practices, and advanced NFT features") but the only actions are generic ("Master", "best practices", "features") with no concrete verbs. Not a 3 because it lists no concrete actions like the "extracts/fills" anchor.	2 / 5
Completeness	It clearly states what the skill covers but has no "Use when…" clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines. Not a 4 because the "when" is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	"ERC-721", "ERC-1155", "NFT", and "metadata" are natural terms users say in this domain, giving good keyword coverage. Not a 5 because synonyms like "non-fungible token" and "smart contract" are missing.	4 / 5
Distinctiveness Conflict Risk	The NFT-standards niche with ERC-721/ERC-1155 triggers is clearly distinguishable from other skills with minimal conflict risk. Not below 5 because the triggers are specific and unlikely to fire for unrelated skills.	5 / 5
	Total	14 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 8 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/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.