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.

76

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A well-structured, actionable pattern library of executable NFT contracts with appropriately offloaded reference material. Its main gap is the absence of an explicit deployment/validation workflow with checkpoints.

Suggestions

Add a short deployment-and-verification workflow (e.g., compile → deploy → verify on explorer → test mint) with explicit validation checkpoints to lift workflow_clarity.

Tighten the opening 'Master ERC-721 and ERC-1155...' line or fold the 'When to Use This Skill' list into the description to reduce redundancy with the frontmatter.

Consider noting testing/verification commands (e.g., forge test) alongside the minting examples so the validation loop is concrete rather than implicit.

DimensionReasoningScore

Conciseness

The body is lean and almost entirely executable Solidity with minimal prose, assuming Claude's competence; the only mild redundancy is the one-line 'Master ERC-721 and ERC-1155...' summary and a 'When to Use' list that restates triggers, but neither is padded. Not a 2 because there is no concept explanation Claude lacks.

3 / 3

Actionability

Provides full, copy-paste-ready contracts with concrete constants (MAX_SUPPLY, MINT_PRICE), mint/burn/royalty functions, and a JSON metadata example; not a 2 because the code is executable rather than pseudocode.

3 / 3

Workflow Clarity

The skill is a pattern library of independent code examples rather than a sequenced workflow, with no explicit deployment/testing checkpoints or validate→fix→retry loop. Not a 3 because validation checkpoints are absent; not a 1 because the examples are clearly organized and the mint logic includes inline require() guards.

2 / 3

Progressive Disclosure

SKILL.md keeps core patterns inline and offloads soulbound, dynamic, and ERC721A templates to references/details.md, which is verified to exist and is clearly signaled as one level deep ('Read that file for the full pattern library'). Not a 2 because the reference is well-signaled and content is appropriately split.

3 / 3

Total

11

/

12

Passed

Description

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.

The description is specific, third-person, and complete with an explicit 'Use when...' trigger covering natural user terms. It is clearly distinguishable as an NFT-standards skill with low conflict risk.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Implement NFT standards (ERC-721, ERC-1155)' with 'metadata handling, minting strategies, and marketplace integration' — matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Clearly answers both what (implement standards with metadata/minting/marketplace handling) and when via an explicit 'Use when...' clause, matching the top anchor; not a 2 because the when-trigger is explicit rather than implied.

3 / 3

Trigger Term Quality

'Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems' covers natural terms users would say (NFT, NFT contracts, NFT marketplaces, digital asset systems), matching good coverage.

3 / 3

Distinctiveness Conflict Risk

The ERC-721/ERC-1155 NFT niche has distinct triggers unlikely to fire for unrelated skills; not a 2 because it is clearly scoped to NFT standards rather than generically overlapping with other contract skills.

3 / 3

Total

12

/

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.

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.