convez.ai
SkillDesenvolvimento WebIntermediário
kofujimura

Skill de Metadados NFT para GitHub Pages

kofujimura/nft-metadata-pages-skill

Hospede metadados NFT no GitHub Pages com comandos em linguagem natural

Ver no GitHub
InicialPluginScore · de 0 a 100

Skill para agentes de IA codificadores (Claude Code, Codex) que permite hospedar metadados e imagens de NFTs no GitHub Pages, sem custos IPFS e com atualizações instantâneas via git push. Inclui templates prontos para tokens com diferentes papéis (MINTER, BURNER, MEMBER, HOLDER) e suporta atributos como Soulbound via linguagem natural.

Instalação

$npx convez-ai kofujimura/nft-metadata-pages-skill

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
1
Acompanhando
0
Saúde
28%
Último commit
há 1 mês
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Prototipagem rápida de coleções NFT sem infraestrutura custosa
  • Gerenciamento de metadados de tokens com atributos dinâmicos (Soulbound, papéis)
  • Integração end-to-end com nft-developer-skill para deploy completo de NFTs

Veredito

Ferramenta prática e bem-documentada que reduz fricção no desenvolvimento NFT ao usar GitHub Pages como CDN gratuito. Bom para prototipagem; depende do ecossistema Claude Code/Codex e requer configuração manual inicial de GitHub Pages.

README

A tradução para o português deste README ainda está na fila.

nft-metadata-pages-skill

An NFT metadata skill for AI coding agents (Claude Code, Codex, and compatible tools).

Host NFT metadata and images on GitHub Pages — no IPFS fees, no infrastructure, instant updates via git push. Designed for development and prototyping, and pairs with nft-developer-skill for end-to-end NFT deployment.


Features

  • Ready-to-use sample metadata for common token roles (MINTER, BURNER, MEMBER, HOLDER, SHOP, color tokens)
  • MINTER and BURNER include "Soulbound": "Yes" attribute
  • Current OpenSea/ERC1155/ERC721 metadata schema with attributes
  • .nojekyll configured so extension-less asset files are served correctly
  • Natural language workflow: ask Claude to add tokens, update metadata, or generate token URIs

Quick start

1. Fork this repository

Click Fork on GitHub, then clone your fork:

git clone https://github.com/<your-username>/nft-metadata-pages-skill.git
cd nft-metadata-pages-skill

2. Enable GitHub Pages

Go to your repository Settings → Pages, set:

  • Source: Deploy from a branch
  • Branch: main / (root)

Your metadata will be published at:

https://<your-username>.github.io/nft-metadata-pages-skill/

3. Replace kofujimura with your GitHub username

All metadata files reference kofujimura as the GitHub username. Replace it with your own:

find assets/ -type f | xargs sed -i '' 's|kofujimura|<your-username>|g'
git add assets/
git commit -m "Replace username with <your-username>"
git push

4. Open in Claude Code or Codex

claude nft-metadata-pages-skill/

CLAUDE.md is automatically loaded. You can then give natural language instructions such as:

  • "Add a new token called ADMIN with the admin.png image, not soulbound"
  • "What is the token URI for MINTER?"
  • "Update the description of MEMBER"

Token URI pattern

Once GitHub Pages is enabled, token URIs follow this pattern:

https://<your-username>.github.io/nft-metadata-pages-skill/assets/<TOKEN_NAME>

Examples:

https://your-username.github.io/nft-metadata-pages-skill/assets/MINTER
https://your-username.github.io/nft-metadata-pages-skill/assets/1

Included sample tokens

AssetNameSoulboundImage
MINTERMinter Certificate✅ Yesminter.png
BURNERBurner Certificate✅ Yesburner.png
MEMBERCertificate of MembershipNoMemberCert.png
HOLDERHolder CertificateNoholder.png
SHOPShop CertificateNoShopCert.png
BLUEToken BlueNoTokenBlue.png
GREENToken GreenNoTokenGreen.png
REDToken RedNoTokenRed.png
MyToken / 0MyTokenNomytoken.png
1Control Token 1Nominter.png
2Control Token 2Noburner.png

Adding a new token

  1. Add your image to img/
  2. Create a metadata file in assets/ (no file extension):
{
  "name": "Token Name",
  "description": "Description of the token.",
  "image": "https://kofujimura.github.io/nft-metadata-pages-skill/img/<file>.png",
  "external_url": "https://kofujimura.github.io/nft-metadata-pages-skill/",
  "attributes": [
    { "trait_type": "Role", "value": "YourRole" },
    { "trait_type": "Soulbound", "value": "No" }
  ]
}

Replace kofujimura with your own GitHub username.

  1. Commit and push:
git add assets/<TOKEN_NAME> img/<file>.png
git commit -m "Add <TOKEN_NAME> token"
git push

GitHub Pages deploys automatically within ~1 minute.


Workflow with nft-developer-skill

nft-metadata-pages-skill          nft-developer-skill
─────────────────────             ─────────────────────
Add metadata + image       →      setTokenURI(<id>, "<token URI>")
Get token URI              →      mint(to, id, amount)

Metadata schema reference

{
  "name": "string — display name",
  "description": "string — shown in marketplaces",
  "image": "string — absolute URL to image",
  "external_url": "string — link to project page",
  "animation_url": "string — optional: video/audio/3D file URL",
  "attributes": [
    { "trait_type": "string", "value": "string or number" }
  ]
}

Notes

  • This approach is intended for development and prototyping. For production NFTs, use IPFS (e.g. Pinata, NFT.Storage).
  • .nojekyll is required — without it, GitHub Pages' Jekyll processor ignores extension-less files.
  • File names in assets/ are case-sensitive.

License

MIT

Ver o original no GitHub

Bom para

Relacionados