- Home
- Skills
- Web3 & Crypto
- nft metadata provenance
nft metadata provenance
Generate and audit NFT metadata, validate asset references, and build provenance manifests for collection launches.
$8.99
Works with the AI tools you already use
nft metadata provenance
Example session with this skill installed
Audit these 3 metadata files for a collection named 'Neon Runners'. Ensure the trait 'Background' is consistent and check for missing fields. Files: 0.json, 1.json, 2.json (all provided below).
- Read your context and instructions
- Compiled the nft metadata provenance
- Generated the document
I have audited the metadata for the 'Neon Runners' collection. I identified a trait naming inconsistency in token #2 and a missing description field across the set.
Metadata Audit Report
| Token ID | Status | Issues Found | Recommendations |
|---|---|---|---|
| 0.json | Pass | None | Valid ERC-721 structure. |
| 1.json | Warning | Missing description | Add collection-wide description string. |
| 2.json | Fail | Trait Mismatch: Bg vs Background | Rename Bg to Background for schema parity. |
Provenance Manifest Draft
[
{
"token_id": 0,
"asset": "0.png",
"metadata": "0.json",
"attributes_count": 4
},
{
"token_id": 1,
"asset": "1.png",
"metadata": "1.json",
"attributes_count": 4
},
{
"token_id": 2,
"asset": "2.png",
"metadata": "2.json",
"attributes_count": 4
}
]
Next steps
- Standardize the
Backgroundtrait key across all JSON files to ensure marketplace filters work correctly. - Populate the
descriptionfield in all files before uploading the directory to IPFS. - Verify the image CID once the assets are pinned to update the
imageURI prefix.
nft-metadata-provenance.pdf
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
The problem
Broken NFT metadata leads to failed marketplace listings and loss of holder trust. Small errors like trait typos or CID mismatches can ruin a collection launch after the contract is already deployed.
What it does
- Generates standardized JSON metadata following OpenSea and ERC-721/1155 standards.
- Audits existing metadata folders for duplicate attributes, missing image references, and schema violations.
- Constructs deterministic provenance manifests to link token IDs to specific asset hashes.
- Validates reveal states to ensure smooth transitions from placeholder to final metadata.
- Identifies release blockers like broken URIs or impossible trait combinations.
Why this beats prompting it yourself
General LLMs often hallucinate attribute structures or fail to maintain strict consistency across 10,000 items. This skill uses a systematic audit framework to catch edge cases like filename-token ID offsets and hidden trait collisions that manual prompting overlooks.
Use cases
- Generating 10k metadata files from a provided trait spreadsheet.
- Auditing a folder of JSON files before pinning to IPFS.
- Creating a provenance hash list for smart contract deployment.
- Validating pre-reveal metadata against post-reveal asset lists.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean today
- Passed all security checks, Safe to install