CtrlK
BlogDocsLog inGet started
Tessl Logo

axiom-audit-resize

Use when the user mentions window resizing support, resizable-window readiness, iPhone Mirroring compatibility, scene-lifecycle migration checking, or preparing an app for the 27-cycle resizing model.

61

Quality

72%

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-resize/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 audit skill body: concrete grep patterns, exact fix APIs, explicit validation checkpoints, and a clear multi-phase workflow. Minor room remains to trim explanatory prose and to split the anti-pattern catalog into a reference file, but the content is strong overall.

DimensionReasoningScore

Conciseness

The body is dense and assumes UIKit competence (no 'what is UIScreen.main' padding); every section earns its tokens with concrete greps and fixes, though its ~170-line length carries a few explanatory 'Issue'/'Impact' sentences that could be tightened.

4 / 5

Actionability

Fully executable guidance throughout: exact runnable grep patterns (e.g. `UIScreen\.main\.bounds`), specific fix APIs (`windowScene.effectiveGeometry.coordinateSpace.bounds`), and a concrete validation command (`xcui resize sweep --sizes <breakpoints> --assert-id <id>`).

5 / 5

Workflow Clarity

A clear five-phase sequence (Map → Detect → Reason → Cross-reference → Score) with explicit validation checkpoints ('use Read to verify... grep patterns have high recall but need contextual verification', 'Require evidence from the Phase 1 map'), a False Positives checklist, and a defined output format.

5 / 5

Progressive Disclosure

Well-organized into clearly headed phases with one-level-deep, well-signaled pointers to external skills (axiom-uikit, axiom-graphics) for migration detail rather than duplicating it; no bundle files exist, and the 12 inline anti-pattern entries could arguably factor into a reference file.

4 / 5

Total

18

/

20

Passed

Description

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

This is a strong, specific trigger description with excellent 'when' guidance and good keyword coverage, but it omits an explicit statement of what the skill does, leaving the 'what' implicit. Adding a concrete capability verb would lift completeness and specificity.

Suggestions

Lead with a 'what' clause before the trigger, e.g. 'Audits UIKit code, Info.plist, and scene manifests for resize-readiness violations under the 27-cycle resizing model. Use when...'

State the concrete action (audit/detect/report) explicitly so the description answers 'what does this do' as clearly as it answers 'when'.

Add one or two natural adjacent trigger terms users may say, such as 'Split View' or 'multi-window support', to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ('window resizing support', 'iPhone Mirroring compatibility', 'scene-lifecycle migration') but states only minimal/generic actions ('checking', 'preparing an app'); the skill's core capability—auditing code for resize-readiness violations—is never stated as a concrete verb.

2 / 5

Completeness

The 'when' is explicit and concrete ('Use when the user mentions...'), but the 'what' is only weakly implied through trigger phrasing rather than stated (no 'Audits... / Detects... / Reports...'), so it falls between 'only when without what' (2) and 'both present' (4).

3 / 5

Trigger Term Quality

Good keyword coverage with natural synonyms users would say ('window resizing support' / 'resizable-window readiness', 'iPhone Mirroring compatibility', 'scene-lifecycle migration'); a few adjacent natural terms (e.g. 'Split View', 'multi-window') are absent.

4 / 5

Distinctiveness Conflict Risk

The niche is clearly distinct (27-cycle resizing, iPhone Mirroring, scene-lifecycle) with minimal conflict risk; minor overlap acknowledged in the body with the sibling swiftui-layout-auditor.

4 / 5

Total

13

/

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.