CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

80%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.

A tight, executable Solidity reference for ERC-721/ERC-1155 with clean progressive disclosure to a verified details.md bundle. Its main weakness is the absence of any sequenced workflow with validation checkpoints for batch minting operations.

Suggestions

Add a short "Build & verify" workflow (e.g., compile -> run on testnet -> check max-supply and payment require() invariants -> audit) so batch minting has explicit validation checkpoints.

Resolve the on-chain metadata example's undefined helpers — either import a Base64 library and stub-note generateSVG, or move that pattern to references/details.md as a partial template.

Cross-link the soulbound, dynamic, and ERC721A patterns in details.md from the relevant body sections (e.g., "Soulbound: see references/details.md") so advanced patterns are discoverable from context.

DimensionReasoningScore

Conciseness

Lean and code-first with minimal prose; it does not explain what NFTs or ERC standards are and assumes Claude's competence, with every section earning its place.

5 / 5

Actionability

The ERC-721 and ERC-1155 contracts are copy-paste ready and cover common cases, but the on-chain metadata example relies on undefined helpers (Base64.encode, generateSVG, generateMetadata returning ""), leaving minor gaps.

4 / 5

Workflow Clarity

Content is organized as a pattern library by standard rather than a sequenced workflow, and batch/destructive operations like mintBatch and the mint loop have no workflow-level validation or verification checkpoints, capping this dimension at 3.

3 / 5

Progressive Disclosure

The body is a well-sectioned overview of core standards that clearly signals a single one-level-deep reference ("More detailed templates and worked examples live in references/details.md"), and that file exists with appropriately split advanced patterns.

5 / 5

Total

17

/

20

Passed

Description

87%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.

A strong, third-person description that states concrete capabilities and an explicit Use-when trigger clause with natural keywords. It is comprehensive on what/when, with only minor gaps in action and keyword coverage.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions — "proper metadata handling, minting strategies, and marketplace integration" — but omits adjacent capabilities like royalties, soulbound, or dynamic NFTs, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both what ("Implement NFT standards ... with proper metadata handling, minting strategies, and marketplace integration") and when ("Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems") with concrete triggers.

5 / 5

Trigger Term Quality

Natural trigger phrases ("creating NFT contracts", "building NFT marketplaces", "implementing digital asset systems") plus the ERC-721/ERC-1155 tokens users actually name, though common variants like "NFT collection" or "minting an NFT" are absent.

4 / 5

Distinctiveness Conflict Risk

The ERC-721/ERC-1155 niche with NFT-marketplace triggers is a clear, distinct lane with minimal overlap risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wshobson/agents
Reviewed

Table of Contents

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.