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.

81

1.24x
Quality

74%

Does it follow best practices?

Impact

93%

1.24x

Average score across 3 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/blockchain-web3/skills/nft-standards/SKILL.md

The canonical home for this skill is nft-standards in wshobson/agents

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 body is a dense, largely executable reference of NFT patterns with good section structure, but it behaves as a monolith: long contracts are inlined and the referenced bundle files are missing, undermining progressive disclosure, and no sequenced workflow with validation is provided.

Suggestions

Create the referenced references/ and assets/ files (or remove the Resources list), and move the full ERC-721/ERC-1155 contract listings into assets/ so the body becomes a true overview pointing one level deep.

Add an explicit workflow with validation checkpoints for risky operations such as minting (e.g. verify supply/limits, test on a fork, confirm metadata renders before mainnet deploy).

Replace or clearly flag the placeholder stubs (generateSVG, generateMetadata) so examples remain executable, or mark them as intentionally illustrative.

DimensionReasoningScore

Conciseness

Prose is lean and assumes competence ('Master ERC-721 and ERC-1155 NFT standards...'), with content dominated by dense code rather than padded explanation; a few intro lines and inlined full contracts could still be trimmed or externalized.

4 / 5

Actionability

Mostly copy-paste-ready Solidity across ERC-721, ERC-1155, royalties, soulbound, dynamic, and ERC721A, but stubs like generateSVG returning '...' and generateMetadata returning '' leave minor gaps.

4 / 5

Workflow Clarity

Organized as a per-topic pattern catalog rather than a sequenced workflow; the code contains require()-based guards but there are no explicit validation checkpoints or feedback loops at the process level.

3 / 5

Progressive Disclosure

Section headers provide structure, but full production contracts are inlined in the body while the Resources section points to references/ and assets/ files that do not exist, so the disclosure hierarchy is not actually realized.

2 / 5

Total

13

/

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, well-targeted description that explicitly states both capabilities and use-when triggers in third person. Minor tightening of the slightly abstract terms ('proper', 'strategies') would push specificity to full marks.

DimensionReasoningScore

Specificity

Names the concrete standards (ERC-721, ERC-1155) and lists several actions ('metadata handling, minting strategies, and marketplace integration'), but 'proper' and 'strategies' introduce mild abstraction that keeps it just below comprehensive.

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 trigger phrases.

5 / 5

Trigger Term Quality

Natural triggers like 'creating NFT contracts, building NFT marketplaces, or implementing digital asset systems' cover the main user phrasings, though synonyms/extensions (e.g. ERC-1155 tokens, .sol) are not enumerated.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear NFT-specific niche with distinct triggers (ERC-721/1155, NFT marketplaces, digital asset systems) and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 8 missing

Warning

Total

15

/

16

Passed

Repository
Dicklesworthstone/pi_agent_rust
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.