CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-games

Use when building ANY 2D or 3D game with SpriteKit, SceneKit, or RealityKit, or adding touch controls or game controller support. Covers scene graphs, ECS, physics, actions, game loops, rendering, TouchController, GCController.

72

Quality

89%

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

78%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-structured router/index skill: lean, concrete routing with a clear decision tree and well-signaled one-level-deep references into the broader skill suite. The only soft spot is the length of the Anti-Rationalization table.

Suggestions

Trim the Anti-Rationalization table to the 5–6 highest-value rows; the rest restate guidance already pointed to by the references and add tokens without new routing signal.

Consider folding the duplicated routing entries between the Quick Reference table and the numbered Decision Tree list into a single source of truth to reduce maintenance drift and token cost.

The body references sibling-suite files (skills/spritekit.md, axiom-graphics/*) that are not present as bundle files here; add a one-line note clarifying these live in sibling skill suites so navigation expectations are unambiguous.

DimensionReasoningScore

Conciseness

The body is a lean router of tables, a decision tree, and pointer lists with no padding explaining what SpriteKit or physics are; the 11-row Anti-Rationalization table is the one section that could be trimmed, keeping it just below a 5.

4 / 5

Actionability

Routing guidance is concrete and executable — specific file paths (skills/spritekit-diag.md), an agent launch ("Launch `spritekit-auditor` agent or `/axiom:audit spritekit`") and concrete gotchas ("bitmasks default to 0xFFFFFFFF"); no inline code, but that is appropriate for a router skill.

4 / 5

Workflow Clarity

A graphviz decision tree plus a 15-item numbered routing list give a clear, sequenced decision flow; no validation checkpoints are needed because the body performs routing rather than destructive operations.

4 / 5

Progressive Disclosure

The body is an overview pointing one level deep to well-signaled separate files via the Quick Reference table and External Routes section (skills/spritekit.md, skills/spritekit-ref.md, skills/spritekit-diag.md, plus axiom-graphics/uikit/integration routes), with content appropriately split and easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

100%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 tightly written, third-person description that clearly states both what the skill covers and when to use it, with concrete framework names and natural trigger phrases. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Enumerates multiple concrete capability areas — "scene graphs, ECS, physics, actions, game loops, rendering, TouchController, GCController" — alongside the three named frameworks, giving comprehensive coverage of concrete actions rather than vague language.

5 / 5

Completeness

Explicitly answers both: "what" ("Covers scene graphs, ECS, physics, actions, game loops, rendering, TouchController, GCController") and "when" ("Use when building ANY 2D or 3D game with SpriteKit, SceneKit, or Realitykit, or adding touch controls or game controller support").

5 / 5

Trigger Term Quality

Uses natural user phrasing — "building ANY 2D or 3D game", "touch controls", "game controller support" — plus the framework names (SpriteKit, SceneKit, RealityKit) users actually say, giving comprehensive coverage of natural trigger terms.

5 / 5

Distinctiveness Conflict Risk

The Apple game-framework niche (SpriteKit/SceneKit/RealityKit + TouchController/GCController) is highly specific with distinct triggers and minimal overlap risk against non-game skills.

5 / 5

Total

20

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
CharlesWiltgen/Axiom
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.