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.

83

1.37x
Quality

64%

Does it follow best practices?

Impact

95%

1.37x

Average score across 6 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/blockchain-web3/skills/nft-standards/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

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

This is a strong skill description that clearly defines its scope around NFT implementation, includes specific standards and actions, and provides explicit trigger guidance via a 'Use when' clause. It uses proper third-person voice and covers natural keywords that users would employ when seeking NFT-related help. The description is concise yet comprehensive, making it easy to distinguish from other blockchain or smart contract skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: implementing NFT standards (ERC-721, ERC-1155), metadata handling, minting strategies, and marketplace integration. These are concrete, actionable capabilities.

3 / 3

Completeness

Clearly answers both 'what' (implement NFT standards with metadata handling, minting strategies, marketplace integration) and 'when' (explicit 'Use when' clause covering creating NFT contracts, building marketplaces, or implementing digital asset systems).

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'NFT', 'ERC-721', 'ERC-1155', 'minting', 'NFT marketplace', 'digital asset', 'NFT contracts'. These cover both technical and common user terminology well.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche focused specifically on NFT standards and related functionality. The mention of ERC-721, ERC-1155, and NFT-specific concepts makes it clearly distinguishable from general smart contract or blockchain skills.

3 / 3

Total

12

/

12

Passed

Implementation

29%

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

This skill is essentially a code cookbook dumping complete Solidity contract implementations inline without workflow guidance, validation steps, or progressive disclosure. While the code examples are executable and cover a good breadth of NFT patterns, the skill fails to add value beyond what Claude already knows about standard OpenZeppelin patterns. It lacks deployment workflows, testing guidance, and any structure that would help Claude navigate when to use which pattern.

Suggestions

Drastically reduce inline code to key snippets and decision points (e.g., 'use ERC721A over ERC721 for batch minting to save ~50% gas'), moving full contracts to referenced files like ERC721_EXAMPLES.md and ERC1155_EXAMPLES.md.

Add a deployment and verification workflow with explicit steps: compile → test → deploy to testnet → verify on explorer → validate metadata rendering → deploy to mainnet.

Add a decision tree or table at the top helping Claude choose between ERC-721, ERC-721A, and ERC-1155 based on use case, rather than presenting all patterns equally.

Include common pitfalls and validation checks (e.g., metadata URI returns 200, royalty percentage bounds, reentrancy considerations in mint functions) as explicit checkpoints.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~300+ lines, mostly consisting of full contract implementations that Claude already knows how to write. It explains basic patterns (ERC-721, ERC-1155) with complete boilerplate code rather than focusing on non-obvious decisions, gotchas, or project-specific conventions. Much of this is standard OpenZeppelin usage that doesn't need to be spelled out.

1 / 3

Actionability

The code examples are fully executable Solidity contracts with proper imports, complete function signatures, and realistic implementations. They are copy-paste ready and cover concrete patterns including minting, royalties, soulbound tokens, and gas optimization.

3 / 3

Workflow Clarity

There is no workflow or sequencing guidance whatsoever. The skill presents isolated contract snippets with no deployment steps, no testing instructions, no validation checkpoints, and no guidance on how to compose these patterns together. For smart contract development (a destructive/irreversible operation once deployed), the absence of verification steps is a significant gap.

1 / 3

Progressive Disclosure

The content is a monolithic wall of code with no references to external files, no layered organization, and no navigation aids. All patterns are dumped inline at the same level of detail. Content like the full ERC-1155 contract, on-chain metadata, and ERC721A examples could easily be split into referenced files.

1 / 3

Total

6

/

12

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.

Validation11 / 11 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.