CtrlK
BlogDocsLog inGet started
Tessl Logo

game-art

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

54

Quality

61%

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-claude/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.

A well-organized, lean reference of decision matrices and pipelines that is concrete and actionable, held back mainly by absent explicit validation checkpoints in its workflows.

Suggestions

Add explicit validation/checklist steps to the asset pipelines (e.g., 'Verify silhouette readability at gameplay distance before export', 'Test palette on target display').

Consider splitting the large style-comparison and pipeline tables into a references file and linking from the overview to improve progressive disclosure.

Tighten the Color Principles and Animation Principles prose into table rows to match the rest of the body's token efficiency.

DimensionReasoningScore

Conciseness

The body is mostly tight reference tables and a decision tree that assume Claude's domain competence, with only minor explanatory lines (e.g., "Important elements should pop") that could be trimmed.

4 / 5

Actionability

Provides concrete, actionable guidance — a style decision tree, tool-by-phase pipeline tables, naming convention examples (spr_player_idle_01.png), frame-count ranges, and a folder structure — with only minor gaps.

4 / 5

Workflow Clarity

The 2D/3D pipelines present a clear phase sequence (Concept → Modeling → Retopology → ... → Export), but there are no explicit validation checkpoints or feedback loops beyond scattered anti-pattern 'Do' items like testing at gameplay distance.

3 / 5

Progressive Disclosure

Content is well-structured into seven numbered sections with clear headers and is self-contained with no bundle files; over the 50-line simple-skill threshold, so it lands just below a 5.

4 / 5

Total

15

/

20

Passed

Description

53%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 conveys a clear domain and several capability areas but lacks an explicit trigger clause and natural-term synonyms, keeping most dimensions at the midpoint.

Suggestions

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

Broaden trigger terms with synonyms users actually say, such as 'pixel art', 'sprites', '3D modeling', 'texturing', and 'rigging'.

Reframe topical areas as concrete actions (e.g., 'Select art styles', 'structure asset pipelines', 'plan animation timing') to lift specificity.

DimensionReasoningScore

Specificity

Names the domain ("Game art principles") and three sub-areas ("Visual style selection, asset pipeline, animation workflow"), but these are topical capabilities rather than concrete actions like 'extract' or 'fill', and coverage is not comprehensive.

3 / 5

Completeness

Clearly states what the skill covers but provides no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes relevant natural terms ("game art", "visual style", "asset pipeline", "animation workflow") a user might say, but misses common synonyms and variations such as 'sprites', 'pixel art', or '3D modeling'.

3 / 5

Distinctiveness Conflict Risk

"Game art principles" carves a clear niche distinct from generic skills, with only minor overlap risk against broader art/design skills.

4 / 5

Total

13

/

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.