CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-audit-spritekit

Use when the user wants to audit SpriteKit game code for common issues.

66

Quality

79%

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 ./axiom-codex/skills/axiom-audit-spritekit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a high-quality, highly actionable auditor prompt with excellent workflow sequencing and validation checkpoints. Its main weakness is progressive disclosure: it is a single large monolithic file where the pattern catalog and reference tables could be split into bundle files to reduce context cost when only part of the audit is needed.

Suggestions

Move the 8 detection patterns (Issue/Impact/Search/Verify/Fix) into a references/ file (e.g. PATTERNS.md) and keep SKILL.md as an overview that points to it, reducing baseline token load.

Consider splitting the Phase 3 completeness table and Phase 4 compound matrix into a separate references/ file so the core workflow stays lean.

If splitting is not desired, add an explicit 'When to read the full pattern catalog' note so Claude can defer loading detailed patterns until Phase 2.

DimensionReasoningScore

Conciseness

The body is dense and action-oriented, assuming Claude's competence with grep and Swift rather than explaining basics; the per-pattern Issue/Impact/Search/Verify/Fix structure is mostly earning its tokens, with only minor over-explanation in the Impact lines that could be trimmed, matching the efficient score-4 anchor rather than the lean score-5.

4 / 5

Actionability

Guidance is fully executable: concrete grep regexes per pattern, explicit Read-verification steps, and copy-paste-ready fix code (e.g. `node.run(action, withKey: "spawnLoop")`), matching the score-5 anchor of copy-paste ready commands covering common cases.

5 / 5

Workflow Clarity

Five phases are clearly sequenced (Map → Detect → Reason → Cross-Reference → Score) with an explicit validation checkpoint ("For every grep match, use Read to verify the surrounding context before reporting"), defined output format, false-positive list, and output limits, matching the score-5 anchor of clear sequence with explicit validation and feedback loops.

5 / 5

Progressive Disclosure

No bundle files exist (references/scripts/assets absent) and the entire 300-line body — all 8 detection patterns, the completeness table, and the compound-finding matrix — is inlined monolithically in SKILL.md with only external cross-skill pointers in Related, matching the score-3 anchor of having structure but keeping content that should be separate inline.

3 / 5

Total

17

/

20

Passed

Description

73%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 well-targeted to a distinct niche with a clear Use-when trigger, but it is light on enumerated capabilities — it states one action (audit for common issues) without listing the specific issue categories the skill actually covers. Tightening the "what" with a few concrete issue types would lift completeness and specificity.

Suggestions

Expand the 'what' to name 2-3 concrete issue categories the auditor detects, e.g. 'physics bitmask issues, frame drops, memory leaks, and scene-transition crashes'.

Add natural synonyms users might say such as 'review' or 'check' alongside 'audit' to broaden trigger coverage.

Optionally reference SpriteKit file types (e.g. .swift, .sks) to improve trigger-term distinctiveness for users who mention files.

DimensionReasoningScore

Specificity

The description names the domain ("SpriteKit game code") and one concrete action ("audit ... for common issues"), but stops at a single verb rather than listing several specific actions, matching the score-3 anchor of naming the domain with 1-2 actions but not comprehensive coverage.

3 / 5

Completeness

It has both a "what" ("audit SpriteKit game code for common issues") and an explicit "when" ("Use when the user wants to audit SpriteKit game code for common issues"), but the "what" is thin and does not enumerate the kinds of issues, so it matches score 4 rather than the fully enumerated score-5 anchor.

4 / 5

Trigger Term Quality

Natural terms a user would say are present ("audit", "SpriteKit", "game code", "common issues"), giving good keyword coverage; a few natural synonyms ("review", "check", performance) and file extensions are missing, so it sits above score 3 but below the comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

"SpriteKit game code" is a narrow, specific niche with distinct triggers and minimal overlap risk with other skills, matching the clear-niche score-5 anchor.

5 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.