Skip to content
Get packs

Guide · Agent skill

How to use the Vesperfall Review Assets agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The build-vesperfall-review-assets skill is an agent skill for the Vesperfall game repository. It gives an AI agent a fixed workflow for adding one character, enemy, prop, or equipment item to the game's asset catalog, producing a transparent card image and a live Three.js preview that both match real project files. This guide explains what a skill is, how to install this one, how to ask for it, and what it needs before it is useful.

Vesperfall Review AssetsMengTo/Skills · MIT

Quick start

  1. 1Download the ZIP. Get the build-vesperfall-review-assets ZIP from the MengTo/Skills page for the game-development folder.
  2. 2Install the folder. Unzip it into ~/.claude/skills/ for personal use, or into the project's .claude/skills/ folder. You can also upload the ZIP under Settings → Capabilities → Skills.
  3. 3Confirm the prerequisites. Check that you have the Vesperfall repository, Git, Python 3 and the build, lint and test tooling.
  4. 4Make a natural request. Ask for a specific asset and outcome, such as a card PNG with an inspector model for a named enemy.
  5. 5Let the agent inspect the repo. The agent should locate the shipped PNG, FBX, GLB and texture files before choosing a model path.
  6. 6Review the validation output. Check the output of scripts/validate_pair.py, the build, lint and tests, and the browser checks listed in the report.
  7. 7Review and commit. Read the diff, confirm the final report, and use the commit SHA the agent reports.

What is an agent skill and what does this one do?

An agent skill is a folder of instructions, reference notes and sometimes scripts that an AI coding agent loads when a request matches the skill's description. The agent reads the instructions and follows them instead of improvising.

This skill applies only to the Vesperfall project. When it runs, the agent inspects the repository for the shipped PNG, FBX, GLB and texture files, then builds a 512x512 RGBA catalog PNG with transparent corners and no baked floor or shadow. It also prepares a live Three.js model preview for the inspector, adds an isolated review route with animation controls, and records where the model came from.

  • Card image: a transparent PNG with no canvas, stored under public/asset-catalog/<category>/.
  • Inspector: one live model canvas with a truthful format label.
  • Review route: restart, pause/play, action selection, drag rotation, source paths and provenance.
  • Validation: runs scripts/validate_pair.py on the PNG and model source, then build, lint, full tests and git diff --check.

Install the Vesperfall review assets skill

Download the skill ZIP from the MengTo/Skills page for agent-skills/game-development/build-vesperfall-review-assets. Unzip it so the folder contains SKILL.md, agents/openai.yaml, references/catalog-contract.md and scripts/validate_pair.py.

For a personal install, place the folder in ~/.claude/skills/. For a single project, place it in that project's .claude/skills/ folder. Alternatively, in the Claude apps, open Settings, go to Capabilities, and upload the skill under Skills.

  • Personal: ~/.claude/skills/build-vesperfall-review-assets/
  • Project: .claude/skills/build-vesperfall-review-assets/ inside the Vesperfall repository
  • Claude apps: Settings → Capabilities → Skills, then upload the ZIP

Check the requirements before you start

The skill assumes the Vesperfall repository itself. It expects the Three.js, FBX and GLB assets, the build, lint and test tooling, and Git to be present. Its own validation script needs Python 3.

The browser step uses the Codex in-app browser. The skill says to use that browser only. The img2threejs skill is optional and is needed only when geometry is reconstructed from an image.

  • Python 3, to run scripts/validate_pair.py
  • The Vesperfall repository with its assets and build, lint and test tooling
  • Git
  • Codex in-app browser for browser validation
  • Optional: the img2threejs skill, for reconstructing geometry from a reference image

Trigger the skill with a natural request

Ask for the task in plain language that names the kind of asset and the outcome you want. The skill's description covers adding characters, enemies, props or equipment to the catalog, creating a card PNG with an inspector model, exposing an isolated model or moveset route, and standardizing provenance and browser checks.

Naming the asset and the repository files helps the agent find the real source before it chooses a model path.

  • Add the goblin scout enemy to the Vesperfall catalog as a card PNG with a live inspector model.
  • Create a review pair for the iron shield equipment item and expose it on an isolated preview route.
  • Add a moveset review route for the knight character and list which actions have real clips.
  • Check that the new prop's PNG is 512x512 with transparent corners and that its model file exists.

What the workflow checks before it commits

The skill tells the agent to inspect repository truth first. It should prefer a shipped FBX or GLB when that is the actual runtime source, and it must not claim a model exists just because code declares a future URL. Imported geometry must never be labelled as img2threejs.

Grounding is measured from the foot or contact geometry rather than the lowest weapon tip. Tests should cover exact paths, RGBA dimensions, preview kind and route. Each motion is tested deterministically when animation changes grounding.

  • Provenance labels: imported-fbx, procedural-three, img2threejs review, static-raster, or declared, not shipped.
  • Card surface: transparent PNG only, no WebGL.
  • Final report: PNG path and dimensions, alpha status, model source, preview route, actions, test proof and commit SHA.
python3 scripts/validate_pair.py <png> <model-source>

Safety notes: scripts and network

The skill runs scripts. Its bundled scripts/validate_pair.py checks the PNG's size and transparency and confirms that the model file exists. Read the script before you run the skill on a repository you care about.

The source states that the skill does not use the network. It works on files in your repository, so review any changes it makes to catalog files and commit history before pushing.

  • Runs scripts: yes, scripts/validate_pair.py
  • Uses network: no, according to the skill's listing
  • Changes are made to project files, and the workflow ends with a commit, so check the diff first

What people use it for

  • Adding a new enemy to the Vesperfall catalog with a transparent card image and a live inspector model.
  • Exposing an equipment item such as a shield or sword on an isolated preview route with named sockets.
  • Building a moveset review page that lists the real animation clips from an FBX file.
  • Checking an existing catalog asset for correct PNG dimensions, transparency and a present model file.

Frequently asked questions

Is the build-vesperfall-review-assets skill free?

The skill is published under the MIT licence on the MengTo/Skills repository. The source does not list pricing for it, so check the licence file in the repository for the terms.

What do I need to install this agent skill?

You need the ZIP from the MengTo/Skills page, a place to put it (~/.claude/skills/ or a project's .claude/skills/ folder, or the Claude apps' Settings → Capabilities → Skills), and the Vesperfall repository. Python 3 is needed for its validation script.

Can I use this skill on a project other than Vesperfall?

The skill is not suited to other projects. It assumes the Vesperfall folder layout, contracts and routes, so it is tied to that codebase.

Does this skill generate new 3D art?

No. It reviews and wires existing assets, such as shipped FBX or GLB files, and builds the catalog card and preview around them. For general 3D asset creation you need a different tool.

Why does the validation script fail?

The script checks that the PNG is the expected size with transparency and that the model file exists. Check the PNG dimensions and alpha, and confirm the model path in the repository, since the skill does not claim a file exists when it is only declared in code.

How does this compare with other ways of adding assets?

This skill follows a fixed checklist for provenance, grounding, tests and browser validation. Doing the same work by hand or with an unstructured prompt gives less consistency, but the skill only fits the Vesperfall codebase.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

This skill suits developers working on the Vesperfall game who add catalog assets and want a repeatable, verifiable card-plus-preview process. It is a poor fit for anyone outside that project or for anyone who needs new 3D art generated from scratch.

Download the skill