2.6k
GitHub Stars
3
Bundled Files
6 months ago
Catalog Refreshed
7 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill aavegotchi-renderer-bypass- _meta.json311 B
- README.md1.0 KB
- SKILL.md2.2 KB
Overview
This skill renders Aavegotchi assets by deriving renderer hashes from Goldsky Base core data and calling the Aavegotchi renderer batch API. It extracts a tokenId from direct input or an inventory URL, produces the deterministic renderer hash, posts to /api/renderer/batch, and saves returned image and model artifacts to disk.
How this skill works
The skill queries the Goldsky Base core subgraph for token metadata, builds the renderer-formatted hash from wearable and trait fields (Collateral-EyeShape-EyeColor-Body-Face-Eyes-Head-LeftHand-RightHand-Pet), then posts a batch render request to https://www.aavegotchi.com/api/renderer/batch with verify:true and desired render types. It records the HTTP status and raw JSON, downloads proxy PNGs when present, and reports GLB availability and URL when provided.
When to use it
- You have a tokenId or an inventory URL and need deterministic renderer hashes and image artifacts.
- You need to reproduce or archive Aavegotchi visuals outside the standard UI.
- You require PNG_Full, PNG_Headshot, or GLB_3DModel outputs for automation or backups.
- You want to verify wearable ordering or eye mappings by checking renderer hash results.
Best practices
- Supply tokenId or full inventory URL (with id=<tokenId>) to ensure correct extraction.
- Target Base chainId 8453 by default; confirm chain context if Goldsky returns no result.
- Save raw batch JSON alongside images to help debug mapping or ordering issues.
- If availability.exists is false, rerun batch and poll until the render completes.
- Validate eye mapping and left/right wearable order when encountering hash-format 400 errors.
Example use cases
- Archiving all Aavegotchi image artifacts for a given tokenId to a local backup directory.
- Batch-generating full and headshot PNGs for a collection of tokenIds for a gallery.
- Verifying deterministic renderer hashes when debugging wearable mapping changes.
- Triggering and polling 3D model (GLB) renders, then storing GLB URLs for downstream processing.
FAQ
Provide a tokenId or an inventory URL containing id=<tokenId>. The skill extracts the tokenId automatically.
What does the skill return?
It returns tokenId, derived renderer hash, the /api/renderer/batch status and raw JSON, paths to PNG_Full and PNG_Headshot (or a missing reason), and GLB_3DModel availability/URL.
Why would the batch return a 400 for hash-format?
Usually due to incorrect eye mappings or incorrect left/right wearable ordering; verify mappings and retry.