Index, search and browse your game asset library: a local web UI and CLI that keeps licenses and AI provenance in plain files.
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
# Add to your Claude Code skills
git clone https://github.com/digitalhobbit/assetcatGuides for using cli tools skills like assetcat.
See how assetcat compares with popular alternatives.
If you've collected game assets for a while (Humble bundles, Kenney's all-in-1, itch.io and store packs), you probably have hundreds of packs and hundreds of thousands of files, and no good answer to "do I own a pixel-art dungeon tileset, may I use it commercially, and is it AI-generated?"
assetcat indexes a library like that and lets you browse it in a local web UI or search it
from the command line. What you know about the library (each bundle's license, whether a pack
is human-made and why you believe so, notes, tags, shortlists) lives in plain TOML files next
to the library, so it syncs with it, diffs cleanly and survives any rebuild of the index.
To see it in action, watch the video walkthrough. The story behind it (why I built it and how it works with local AI) is in this GammaVibe post.
item_37.png and pack pages list what a pack contains.style:pixel-art, perspective:top-down), so you can filter by them.
You can remove or add tags with one click, and your changes survive any re-run.
Expectations: AssetCat was built for one real library first (bundles, store packs and Kenney) and is generalized as other libraries show up. Yours will probably need a few corrections to how folders become packs, which the browse UI lets you make. If something doesn't work for your library, please open an issue.
Contributing: I'm not taking pull requests for now, so the code stays consistent as it evolves. Feature requests are very welcome: open an issue describing what you need, ideally with a draft prompt for a coding agent that would build it.
With uv (it fetches Python 3.12+ if you don't have it):
uv tool install assetcat
or try it without installing: uvx assetcat --help. pipx install assetcat and pip install assetcat (Python 3.12+) work too. The latest unreleased version:
uv tool install git+https://github.com/digitalhobbit/assetcat. Runs on macOS, Windows and Linux.
assetcat init ~/Assets # 1. the folder that holds your asset folders
assetcat index # 2. read the library (the first run takes a few minutes on a big one)
assetcat serve --open # 3. browse it at http://127.0.0.1:8765/
init looks at your top-level folders, guesses a layout, and writes a profile folder in
<library>/assetcat/. It prints what it guessed; read it, and adjust catalog.toml in the
profile if a section looks wrong (see How folders become packs).index reads every file's header (sizes, frames, durations, fonts, readme text), finds
sprite sheet grids and duplicates across bundles, and renders a contact sheet per pack.
Later runs only read what changed, so re-run it whenever you add assets.assetcat doctor to see what's left to do. Each problem comes with how to fix it.A pack page shows the pack's tags, previews, readme and license, where its license and AI status come from, what its images show, and its files by folder:

The viewer scales pixel art by whole numbers, overlays the sheet's grid (read from Tiled, atlas or Kenney files or a size in the file name, or set by you) and plays a row as an animation:

Asset search covers the whole library, filtered by type, media, bundle and AI status. Search by words, or by meaning to find images by what they show:

Sound and music show as waveforms. Click one to play it in the player bar, which can go on to the next one by itself (auto-next):

3D models (glTF/GLB, OBJ, and FBX on a best-effort basis) show as rendered tiles. The viewer lets you turn a model around, switch between its formats and play its animation clips. Search can narrow 3D models to animated or rigged ones:

Star packs, folders or single assets to collect them in shortlists (plain TOML in the profile), for example to hand a set of candidates to Claude in a game project.
The profile's catalog.toml lists sections, one per top-level folder:
[[sections]]
name = "bundles"
folder = "Bundles"
layout = "groups" # each folder inside is a group (a bundle or a store) holding packs
[[sections]]
name = "kenney"
folder = "Kenney Game Assets All-in-1"
layout = "single-group" # the whole section is one group...
pack_depth = 2 # ...with packs at <category>/<pack>
Inside a group, every folder gets a role:
Graphics/, Audio/); its sub-folders are looked at for packs.AssetCat guesses roles from folder names and contents (previews, readmes and licenses mark a pack). When it guesses wrong, the Layout page in the browse UI shows each group's folders with their roles; change one and the tree below shows the result before you save. Roles are saved in the group's curation file, and the page re-indexes to apply them.

index creates one curation file per group in the profile's curation/ folder. Edit it in the
browse UI (which keeps your comments and formatting) or by hand:
store = "Example Store"
purchased = 2020
license = "cc-by-4" # a key in licenses.toml
ai_generated = "no" # yes | no | unknown
ai_reason = "Released in 2017, before generative art tools"
[packs."graphics/forest-tiles"] # per-pack overrides, keyed by folder (the Layout page shows keys)
license = "cc0"
tags = ["forest", "pixel-art"]
cover = "Preview/cover.png"
grid = { "tiles/forest.png" = [16, 16] }
Values inherit: a pack takes its group's license and AI status unless it sets its own, and the
packs inside a collection inherit from the collection. licenses.toml holds your license table
(CC0, CC BY and a few common store licenses to start with); add one entry per license you own
assets under. Its summaries are reminders, not legal advice: check the terms that came with your
purchase before you ship.
ai_generated = "no" is the claim "a human made this", and ai_reason is why you believe it:
the release date, the artist, the store's policy. With storefronts asking about AI content and
players caring, that reason is worth writing down while you still remember it.
assetcat classify shows each pack to a vision-language model running on your machine and
stores the tags it answers with in the profile. For each pack, the model gets the cover and
contact sheet, plus what the index knows: the pack's name, folders, file formats and image sizes,
and an excerpt of its readme. It answers only with values from the profile's tags.toml, which
you can extend. With the recommended model, a pack takes about 4 seconds on an M4 Pro Mac (850
packs in about an hour), and later runs only tag packs that are new or changed.
It
assetcat is an open-source cli tools skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by digitalhobbit. Index, search and browse your game asset library: a local web UI and CLI that keeps licenses and AI provenance in plain files. It has 50 GitHub stars.
assetcat's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/digitalhobbit/assetcat" and add it to your Claude Code skills directory (see the Installation section above).
assetcat is primarily written in Python. It is open-source under digitalhobbit on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other CLI Tools skills you can browse and compare side by side. Open the CLI Tools category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh assetcat against similar tools.
No comments yet. Be the first to share your thoughts!
Top skills in this category by stars