CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

generate2dsprite

Make game-ready 2D characters, creatures, props, icons and FX as master stills, sprite sheets or animation clips. Plan size, motion and finish; generate the art (image generation is the default, through generate2dmedia route_media.py - the API when a key is configured, else the local Codex or Grok CLI); approve one master still per character; then key, slice, register, scale, palette, QA and export frames for a game engine (Aseprite JSON, Godot SpriteFrames or Sprite3D). HD finish by default, pixel finish on request. Character animation is one image-to-video clip per action from the master (video2dsprite); sheets are for FX, icons and props. Use for sprites, masters, sheets, frame-by-frame animation and packaging frames from any source. Not for maps, tiles or backgrounds (generate2dmap), video clips (video2dsprite), code-drawn art (codeart2d, only on request) or calling an image or video API by itself (generate2dmedia).

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally operational skill body: exact commands, an ordered and validated pipeline with named error-recovery actions, and a clean overview-to-references split with all referenced files real. The only notable weakness is mild verbosity from repeated rules and one overloaded Commands paragraph.

DimensionReasoningScore

Conciseness

The body is dense and telegraphic with essentially no explanation of concepts Claude already knows — every line carries skill-specific routes, flags, exit codes, or rules. It falls just short of the lean/anchor-5 bar because the master-still handoff rule and the "sheets are for FX, icons and props" rule are each restated about three times across sections, and the Commands section is a single ~400-word paragraph that could be split or trimmed.

4 / 5

Actionability

Fully executable guidance throughout: complete command lines with flags ("master_still.py generate --spec <json> --takes 3 --output-dir <new>"), a need-to-route pipeline table mapping every task to a specific tool invocation, documented exit codes (1/2/3/4) and env vars. This matches the anchor for copy-paste-ready commands covering the common cases.

5 / 5

Workflow Clarity

The master-still workflow is a numbered 6-step sequence (spec, generate, choose, fix-by-edit, approve, motion handoff) and the processing pipeline is given as an explicit ordered chain. Validation is pervasive for these batch operations — --strict-qc publishes nothing on failure, QA envelopes with named checks, exit 4 on QA fail — and feedback loops are concrete (key_ring_spill -> "add --despill-radius 1 or --key-quality soft"; duplicated half-cycle -> regenerate the second half), plus an acceptance checklist. This matches the anchor for explicit validation steps with error-recovery loops.

5 / 5

Progressive Disclosure

The body is an overview that pushes all deep detail to one-level-deep references (all 12 referenced .md files and the schema files exist in the bundle, including the hibit.md FX-route anchor), each labeled with its scope in the References section, and an inline need-to-route table for navigation. This matches the anchor for a clear overview with well-signaled one-level-deep references and easy navigation.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, complete, and well-bounded description: it states concrete capabilities end-to-end, gives explicit positive and negative triggers, and cleanly separates itself from four sibling skills. Its main weakness is verbosity — implementation routing detail (route_media.py, Codex/Grok CLI, key configuration) pads the trigger-relevant content and would fit better in the body.

DimensionReasoningScore

Specificity

The description lists comprehensive concrete actions across the whole pipeline — "key, slice, register, scale, palette, QA and export frames for a game engine (Aseprite JSON, Godot SpriteFrames or Sprite3D)", "approve one master still per character", "Plan size, motion and finish" — with named output formats. This matches the anchor for multiple specific concrete actions with comprehensive coverage, not the score-4 anchor with 'minor gaps in coverage', since make/plan/generate/approve/process/export are all explicitly covered.

5 / 5

Completeness

It explicitly answers both what ("Make game-ready 2D characters, creatures, props, icons and FX as master stills, sprite sheets or animation clips") and when ("Use for sprites, masters, sheets, frame-by-frame animation and packaging frames from any source"), plus explicit when-not boundaries ("Not for maps, tiles or backgrounds..."). This clearly matches the anchor for concrete trigger phrases covering both what and when.

5 / 5

Trigger Term Quality

"Use for sprites, masters, sheets, frame-by-frame animation and packaging frames from any source" gives good natural keyword coverage, but common user variations like "game art", "character art" or "texture atlas" are absent, and the middle of the description is dense with internal jargon ("route_media.py", "key, slice, register") rather than user vocabulary. It is above anchor 3 ('some relevant keywords but missing common variations') because a dedicated Use-for clause plus negative triggers is present, but below anchor 5's synonym-and-extension-level comprehensiveness.

4 / 5

Distinctiveness Conflict Risk

A clear 2D game-sprite niche with explicit disambiguation against every neighboring skill — generate2dmap for maps/tiles/backgrounds, video2dsprite for video clips, codeart2d for code-drawn art, generate2dmedia for bare API calls — so it is unlikely to trigger for the wrong skill. This matches the anchor for a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 suspicious

Warning

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

0x0funky/agent-sprite-forge

Path

skills/generate2dsprite/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.