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

83%

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

75%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, command-dense simulator-testing skill with clear workflows and good cross-skill navigation. Its main weakness is length: dense prose and an inlined command catalog push against the token budget where some material belongs in separate reference files.

Suggestions

Move the long status-bar-override and devicectl prose/quirk details into a reference file (e.g., device-control-ref.md) and keep only the one-command preset inline, trimming the body substantially.

Tighten or remove the duplicated 'Comprehensive Diagnostics (simctl diagnose)' section, which overlaps with capability #11 and the Error Quick Reference.

Promote implicit workflow checkpoints (e.g., 'verify the screenshot is not black before reporting PASS') into explicit validation steps in the Test Workflow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-reference material with little conceptual padding, but the ~480-line body includes dense prose blocks (status-bar override quirks, devicectl explanations) and duplicated diagnostics material that could be tightened or moved to references.	3 / 5
Actionability	Abundant copy-paste-ready, executable bash commands across all 16 capabilities, with specific examples covering the common cases (screenshots, location, push, permissions, biometrics, UI automation).	5 / 5
Workflow Clarity	A clear 7-step Test Workflow plus a crash-detection feedback loop and checkpoints (wait 2s for render, check .ips files, log inspection), but some steps remain high-level and a few validation checkpoints are implicit rather than explicit.	4 / 5
Progressive Disclosure	Well-signaled, one-level-deep references to external axiom-tools skills ('skills/device-control-ref.md', 'skills/xcui-ref.md'), but the large inlined command catalog (16 numbered capabilities) is content that could itself be split into reference files.	4 / 5
	Total	16 / 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 with concrete capabilities and excellent natural-language keywords anchored to a distinctive simulator-testing niche. The only weakness is that capability is conveyed entirely through the 'Use when' trigger clause rather than an explicit 'what this does' statement.

Suggestions

Lead with a short third-person 'what' clause (e.g., 'Drives the iOS Simulator for automated testing with visual verification.') before the 'Use when ...' trigger to make both what and when explicit.

Verify the description stays in third person — it currently does, but keep it that way if editing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete, distinct actions — 'simulator testing, visual verification, push notification testing, location simulation, screenshot capture ... live accessibility validation (VoiceOver announcements, Dynamic Type, ADA checks)' — giving comprehensive coverage of capabilities.	5 / 5
Completeness	A highly explicit 'Use when the user mentions ...' clause answers 'when' concretely, but the 'what' is only implied through the trigger list rather than stated as actions the skill itself performs, so it falls just short of the anchor that requires both explicitly.	4 / 5
Trigger Term Quality	Comprehensive natural-language terms a user would actually say, including synonyms and specific accessibility vocabulary ('push notification testing', 'VoiceOver announcements', 'Dynamic Type', 'ADA checks', 'screenshot capture').	5 / 5
Distinctiveness Conflict Risk	A clearly bounded iOS-Simulator niche with distinctive triggers (VoiceOver, Dynamic Type, ADA, push-notification testing) that minimize overlap with other skills.	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: 9cbcd2d

Reviewed: 6 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.