2d-games

2D game development principles. Sprites, tilemaps, physics, camera.

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/game-development/2d-games/SKILL.md

Quality

Content

57%

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 tidy, well-organized reference of 2D game principles with concrete parameters, but it largely restates widely-known material and offers no executable guidance or workflow. Curating for novelty and adding actionable examples would raise the weaker dimensions.

Suggestions

Trim or condense entries that restate common knowledge (e.g. basic collision shapes, generic camera types) so remaining tokens add value Claude does not already have.

Add at least one concrete, copy-paste-ready snippet per major topic (e.g. a fixed-timestep loop, an atlas-slice table, or a coyote-time/jump-buffer implementation) to lift actionability.

For the genre patterns, convert the bullet principles into a short sequenced build/validate checklist so the workflow clarity dimension can reach 3.

Dimension	Reasoning	Score
Conciseness	The format is lean (tables and terse bullets, no padded prose), but much of the content restates general knowledge Claude already has (collision shapes, camera types, Disney animation principles), so not every token earns its place per the rubric's novelty rationale.	2 / 3
Actionability	It gives concrete numeric guidance ("16x16, 32x32, 64x64", "8-24 FPS", "50-200ms" shake) and named techniques, but as principles/recommendations rather than executable, copy-paste-ready instructions, so it is incomplete relative to a 3.	2 / 3
Workflow Clarity	Content is clearly organized into numbered topical sections and tables, but there is no sequenced multi-step process or validation checkpoint; it is a flat reference rather than a workflow, so it sits at 2 rather than 3.	2 / 3
Progressive Disclosure	It is a self-contained, well-structured overview with clear numbered sections and tables, no nested references, and no bundle files that need signaling — appropriate progressive disclosure for a principles reference of this scope.	3 / 3
	Total	9 / 12 Passed

Description

50%

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 clearly scopes a 2D game development domain but never states concrete actions or when Claude should invoke the skill. Adding verbs and an explicit trigger clause would lift every dimension.

Suggestions

Rewrite as concrete actions, e.g. "Design sprite atlases and animations, build tilemaps, tune 2D physics collision, and set up cameras and screen shake."

Add an explicit trigger clause such as "Use when building or tuning 2D games, platformers, or top-down games involving sprites, tilemaps, physics, or camera work."

Include natural user variations (e.g. platformer, top-down, scrolling, animation) to improve trigger term coverage and reduce overlap with 3D-games skills.

Dimension	Reasoning	Score
Specificity	It names a clear domain ("2D game development") and lists subsystems ("Sprites, tilemaps, physics, camera") but describes topics rather than concrete actions, so it is not the comprehensive action-listing of a 3 nor the vague abstraction of a 1.	2 / 3
Completeness	It states what the skill covers but provides no "Use when..." clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Terms like "2D game", "sprites", "tilemaps", "physics", and "camera" are natural things a user would say, but the list is terse and omits common variations (e.g. platformer, animation, scrolling), landing between the sparse and the well-covered anchors.	2 / 3
Distinctiveness Conflict Risk	"2D game development" is a recognizable niche, but bare terms like "physics" and "camera" could overlap with a 3D-games or general game-development skill, so it is not the conflict-free 3.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/game-development/2d-games/SKILL.md
Commit: 04514f0

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.