CtrlK
BlogDocsLog inGet started
Tessl Logo

game-art

Game art principles. Visual style selection, asset pipeline, animation workflow.

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/game-development/game-art/SKILL.md

The canonical home for this skill is game-art in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

68%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.

The body is a well-structured, dense reference of decision aids and conventions that respects Claude's competence, but its pipelines lack explicit validation checkpoints and it carries no external references to offload detail.

Suggestions

Add explicit validation/feedback steps to the asset pipelines (e.g., 'Verify spritesheet packing before engine import; fix and re-export on failure').

Consider moving the larger comparison matrices (style matrix, pipeline tables) into a references file to slim the SKILL.md overview.

Add a short 'When to use' / scope note at the top so the body's purpose is signaled as clearly as its sections.

DimensionReasoningScore

Conciseness

Content is delivered through dense tables, decision trees, and compact lists with no padding or re-explanation of concepts Claude already knows; minor instances (e.g., the closing 'Remember' line) could be trimmed, keeping it just below a 5.

4 / 5

Actionability

Provides concrete, usable artifacts — a style decision tree, a copy-paste naming convention with examples, a folder structure, and frame-count specs — but as instruction-only guidance it lacks executable code, leaving minor gaps versus a 5.

4 / 5

Workflow Clarity

Asset pipelines are clearly sequenced (Concept → Creation → Atlas → Animation → Integration), but there are no explicit validation checkpoints or feedback loops, and the Anti-Patterns section is guidance rather than a verify-then-proceed step.

3 / 5

Progressive Disclosure

The body is well-organized into seven numbered sections with no nested or buried references; since no bundle files exist, the all-inline structure is appropriate, though some detailed matrices could conceivably live in separate reference files.

4 / 5

Total

15

/

20

Passed

Description

66%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.

The description is specific and distinct, naming the game-art domain alongside three concrete activity areas, but it omits any explicit 'Use when…' trigger guidance, which limits its completeness.

Suggestions

Add an explicit 'Use when…' clause naming concrete trigger phrases (e.g., 'Use when choosing an art style, planning an asset pipeline, or directing game visuals').

Broaden trigger-term coverage with synonyms users actually say ('sprites', 'pixel art', 'character art', 'texturing').

Tighten the 'what' from category-level areas to a few more granular actions to push specificity toward 5.

DimensionReasoningScore

Specificity

Names the domain ('Game art principles') plus several concrete action areas ('Visual style selection, asset pipeline, animation workflow'), with only minor coverage gaps; not a full 5 because the actions stay at a category level rather than enumerating granular tasks.

4 / 5

Completeness

Gives a clear 'what' but lacks any 'Use when…' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('game art', 'visual style', 'animation'), but misses common synonyms and has no file-extension-style triggers; good coverage with a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

'Game art' is a clear niche distinct from most skills, with only minor overlap risk against general design/art skills; not a 5 because the phrasing is somewhat broad.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.