nft-standards

Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

65%Weight 40%Scale 1-3

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

The content is strong on actionability with complete, executable contract examples, but it is held back by a missing real workflow with validation checkpoints and a broken/over-claimed bundle structure where referenced files do not exist and heavy templates are inlined. Tightening these would lift the weaker dimensions.

Suggestions

Provide an explicit multi-step workflow with validation checkpoints (e.g., compile → test → verify on testnet → deploy) for the destructive/batch operations like minting, batch minting, and fund withdrawal, replacing the generic 'Instructions' bullets.

Create the eight referenced bundle files (references/*.md and assets/*) so the 'Resources' links resolve, or remove the dead references; move the full production contract templates into assets/*.sol and keep only concise snippets in SKILL.md.

Add a brief validation/feedback-loop note for irreversible operations (e.g., 'test mint and royaltyInfo locally before mainnet deployment; revert and fix on failure') to satisfy the workflow-clarity checkpoint requirement.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code with minimal concept-padding, but six full inline contracts (~390 lines) could be tightened by offloading templates to the claimed bundle assets, so it is mostly efficient rather than uniformly lean.	2 / 3
Actionability	Provides several complete, executable Solidity contracts (ERC-721, ERC-1155, on-chain metadata, EIP-2981 royalties, soulbound, dynamic, ERC721A) with real imports, require checks, and function bodies that are copy-paste ready.	3 / 3
Workflow Clarity	The 'Instructions' steps are generic and lack explicit validation checkpoints, and the destructive/batch operations (minting, batch mint, withdraw) have no validate→fix→retry feedback loops, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	A 'Resources' section signals one-level-deep references, but none of the eight referenced bundle files actually exist, and full contract templates that should be external are inline, fitting the could-be-better-organized anchor.	2 / 3
	Total	9 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 is concise, third-person, and clearly states both capabilities and explicit use-when triggers for a well-scoped NFT domain. It hits all four anchors at the top level with no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions including 'Implement NFT standards (ERC-721, ERC-1155)', 'metadata handling', 'minting strategies', and 'marketplace integration', matching the multiple-specific-actions anchor rather than the partial naming of a 2.	3 / 3
Completeness	Explicitly answers both what (implement NFT standards, metadata, minting, marketplace integration) and when via the 'Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems' trigger clause, satisfying the explicit-trigger anchor.	3 / 3
Trigger Term Quality	Covers natural phrasings users would say ('NFT contracts', 'NFT marketplaces', 'digital asset systems', 'ERC-721', 'ERC-1155'), giving good coverage rather than the sparse keyword set of a 2.	3 / 3
Distinctiveness Conflict Risk	Scoped to a distinct NFT/ERC-721/ERC-1155 niche with triggers unlikely to collide with other skills, fitting the clear-niche anchor rather than the overlap-prone 2.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 8 missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/nft-standards/SKILL.md
Commit: e63f7dd

Reviewed: 13 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.