axiom-test-simulator

Use when the user mentions simulator testing, visual verification, push notification testing, location simulation, screenshot capture, OR live accessibility validation (VoiceOver announcements, Dynamic Type, ADA checks) on the simulator.

Quality

86%

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

Quality

Content

82%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 highly actionable, well-structured simulator-testing reference with copy-paste commands, a clear workflow, and a crash-detection feedback loop. Its main drawbacks are minor redundancy (diagnose covered twice) and a long single-file capability catalog that could lean more on the referenced sibling-skill files.

Suggestions

Consolidate the `simctl diagnose` coverage: section 11 and the 'Comprehensive Diagnostics' section overlap — merge or have one defer to the other to remove redundancy.

Trim orientation/filler such as the 'Your Mission' list, which restates the workflow that follows in more actionable form.

Move the longer capability catalogs (e.g., full devicectl primitive list, status-bar flag detail) more aggressively into the already-referenced sibling-skill files so the main body stays a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly dense, command-driven reference that earns its tokens with domain-specific tooling (xcui, AXe, devicectl biometrics, status-bar quirks), but it carries minor redundancy — e.g., `simctl diagnose` appears in section 11 and again in a full 'Comprehensive Diagnostics' section — and light filler like the 'Your Mission' list.	4 / 5
Actionability	Packed with copy-paste-ready bash commands across all 16 capability sections, with concrete flags, example payloads, and named coordinates; placeholders like $UDID and com.example.YourApp are clearly standard substitution points.	5 / 5
Workflow Clarity	A clear 7-step Test Workflow plus Mandatory First Steps and a Crash Detection feedback loop (check .ips, distinguish hang vs crash via xcsym) provide real checkpoints; minor gaps remain in explicit per-step validation within the main workflow.	4 / 5
Progressive Disclosure	Well-organized into numbered sections with one-level-deep, clearly signaled references to sibling skill files (e.g., 'axiom-tools (skills/device-control-ref.md)'), offloading deep catalogs; the inlined 16-section capability catalog is long and the Comprehensive Diagnostics section duplicates earlier content.	4 / 5
	Total	17 / 20 Passed

Description

91%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 strong, trigger-rich description that names concrete simulator-testing capabilities and explicit user-mention triggers, with minimal conflict risk. Its only weakness is the absence of a separate declarative 'what this does' statement, leaving the capability list embedded inside the 'when' clause.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'simulator testing, visual verification, push notification testing, location simulation, screenshot capture' plus 'VoiceOver announcements, Dynamic Type, ADA checks' — giving comprehensive coverage of the simulator-testing domain rather than vague abstraction.	5 / 5
Completeness	The 'when' is explicit and concrete ('Use when the user mentions …'), and the enumerated capabilities convey the 'what', but there is no standalone declarative statement of what the skill does, so it falls just below the clearly-explicit-on-both anchor.	4 / 5
Trigger Term Quality	Natural user-facing terms dominate ('simulator testing', 'screenshot capture', 'push notification testing', 'VoiceOver announcements', 'Dynamic Type', 'ADA checks'), covering synonyms and specific accessibility vocabulary a user would actually say.	5 / 5
Distinctiveness Conflict Risk	The niche is narrow and specific to the iOS Simulator with distinctive triggers (VoiceOver, Dynamic Type, push-on-simulator), making conflict with unrelated skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: CharlesWiltgen/Axiom
Path: axiom-codex/skills/axiom-test-simulator/SKILL.md
Commit: 69ffef6

Reviewed: 3 days 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.