CtrlK
BlogDocsLog inGet started
Tessl Logo

game-art

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

56

Quality

64%

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 ./.agents/skills/game-development/game-art/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 content is a well-structured, lean reference of decision matrices, pipeline tables, and concrete guidelines that assumes competence and stays actionable throughout. It scores consistently strong across all dimensions with only minor room for tightening or splitting.

DimensionReasoningScore

Conciseness

The body is table- and decision-tree-driven, assumes Claude's competence (no explanations of what PBR, UV, or pixel art are), and is dense; a few sections could be trimmed but it is broadly efficient.

4 / 5

Actionability

Provides concrete, ready-to-apply guidance: specific tool lists per pipeline phase, frame-count ranges (e.g., 'Walk cycle 6-12'), a copy-paste naming template with examples, and a folder structure, with only minor gaps.

4 / 5

Workflow Clarity

Pipelines (2D and 3D) are clearly sequenced phase-by-phase and the style decision tree gives an explicit decision flow; no validation checkpoints are present, but none are required for this non-destructive art-direction reference.

4 / 5

Progressive Disclosure

No bundle files exist, but the single SKILL.md is well-organized into seven clearly headed sections with navigable tables; content is appropriately placed for a reference overview, with minor room to split detailed matrices into separate files.

4 / 5

Total

16

/

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 names a clear niche and several sub-topics but stops short of concrete actions and omits any 'Use when' trigger guidance, leaving it at mid-range across most dimensions. It is distinctive but not yet activation-ready.

Suggestions

Rewrite the description using concrete verb-led actions (e.g., 'Select art styles, plan 2D/3D asset pipelines, and define animation frame budgets') instead of noun-phrase topic labels.

Add an explicit 'Use when...' clause naming natural user triggers, e.g., 'Use when choosing a game's visual style, planning an asset pipeline, or directing art for a game project'.

Broaden trigger-term coverage with synonyms users actually say (e.g., 'game graphics', 'sprites', 'pixel art', 'art direction').

DimensionReasoningScore

Specificity

Names the domain ('Game art principles') and three sub-topics ('Visual style selection, asset pipeline, animation workflow'), but these are noun-phrase topic areas rather than concrete actions, and coverage is not comprehensive (color theory, resolution, organization from the body are omitted).

3 / 5

Completeness

Provides a clear 'what' (game art principles across three sub-areas) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes relevant terms a user might say ('game art', 'visual style', 'asset pipeline', 'animation'), but misses common variations and synonyms; no natural trigger phrasing beyond the topic labels.

3 / 5

Distinctiveness Conflict Risk

'Game art' is a clear niche with distinct triggers and minimal conflict risk, with only minor overlap against general design or art 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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
vudovn/ag-kit
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.