CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-audit-spritekit

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

64

Quality

76%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-sequenced with strong verification checkpoints, but it is a long single-file prompt whose detailed pattern catalog and tables could benefit from offloading into reference files.

Suggestions

Move the eight detection patterns (Phase 2) and the Phase 3/4 tables into a references/ file (e.g. PATTERNS.md), keeping SKILL.md as an overview with signaled links, to improve progressive disclosure.

Trim repetitive impact sentences in Phase 2 patterns to lift conciseness, since the fix examples already convey the stakes.

DimensionReasoningScore

Conciseness

Mostly efficient — grep patterns, fix snippets, and severity tables earn their place rather than restating basic concepts — but the ~300-line body is lengthy and several impact explanations could be trimmed, so it sits at 'mostly efficient but could be tightened'.

2 / 3

Actionability

It gives exact grep regexes, per-match Read verification steps, and copy-paste-ready fixes (e.g. 'SKAction.run { [weak self] in self?.doThing() }'), matching the fully-executable anchor.

3 / 3

Workflow Clarity

Phases 1–5 are explicitly sequenced with mandatory tool-use instructions, verify-before-report checkpoints ('use Read to verify the surrounding context before reporting'), a false-positive checklist, and a structured output format, matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

No bundle files exist and the eight detection patterns plus the completeness/cross-reference tables all live inline in one large file that could reasonably be split into reference files, fitting 'some structure but content that should be separate is inline'.

2 / 3

Total

10

/

12

Passed

Description

75%

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 a clean, third-person what-plus-when statement scoped to a distinct SpriteKit niche, but its action vocabulary is narrow ('audit ... for common issues') and trigger-term coverage is limited.

Suggestions

List a few concrete audit actions to lift specificity toward level 3, e.g. 'detect physics bitmask bugs, node leaks, action retain cycles, and frame-drop anti-patterns in SpriteKit game code'.

Broaden trigger terms to user-natural variations like 'review', 'find bugs', 'frame drops', 'physics glitches', or 'SpriteKit performance'.

DimensionReasoningScore

Specificity

It names the domain ('SpriteKit game code') and one action ('audit ... for common issues'), but does not enumerate multiple concrete audit actions the way the top anchor expects, so it lands at 'names domain and some actions, not comprehensive'.

2 / 3

Completeness

It states both what ('audit SpriteKit game code for common issues') and when ('Use when the user wants to audit ...'), matching the level-3 anchor's explicit what-and-when-with-trigger pattern.

3 / 3

Trigger Term Quality

Natural terms like 'SpriteKit', 'game code', and 'audit' appear, but coverage is thin compared to the level-3 anchor's spread of variations; common phrasings such as 'review', 'find bugs', or 'frame drops' are absent.

2 / 3

Distinctiveness Conflict Risk

'SpriteKit game code' is a sharply defined niche with a distinct trigger unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

10

/

12

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.