CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/xcuitest-suite

Authors XCUIest UI tests for iOS / iPadOS / tvOS and macOS desktop apps - uses the three-class XCUIApplication / XCUIElement / XCUIElementQuery pattern, sets accessibility identifiers on production code, runs via `xcodebuild test` with destination, parses the `xcresult` bundle. The macOS desktop delta (platform=macOS destination flags, TCC privacy-permission resets, per-device performance baselines) is in references/macos.md. Use when an iOS or macOS app needs UI tests in Apple's first-party framework (no external runtime; native to Xcode).

72

Quality

91%

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

Overview
Quality
Evals
Security
Files

Quality

Content

86%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 well-structured, highly actionable skill body with copy-paste-ready code across every step and clean progressive disclosure that offloads the macOS delta to a real reference file. Minor room to tighten the blockquotes and add an explicit retry/recovery loop for failed runs.

Suggestions

Replace or trim the repeated Apple-documentation blockquotes; one cited statement of the three-class pattern and the continueAfterFailure default is enough.

Add a short 'if a test fails' recovery note in Step 7/8 (re-run with -only-testing, inspect xcresult attachments) to close the feedback loop.

DimensionReasoningScore

Conciseness

Mostly efficient body built around tight code blocks with only minimal framing and no padding of concepts Claude already knows, but the repeated Apple-doc blockquotes and a few explanatory asides could be trimmed slightly.

4 / 5

Actionability

Fully executable, copy-paste-ready Swift code for query/synthesize/assert steps, bash commands for xcodebuild destinations, an xcresulttool command, and a CI yaml workflow - all covering the common cases concretely.

5 / 5

Workflow Clarity

An explicit Step 1-8 sequence with a dedicated assert/verify step (Step 5) and an Anti-patterns table acting as a checklist, but it lacks an explicit if-fail-then-retry feedback loop; the destructive/batch cap does not apply since UI testing is neither.

4 / 5

Progressive Disclosure

Clear overview with a well-signaled, one-level-deep reference to the real references/macos.md for the macOS delta, the rest appropriately kept inline, and a References section listing sibling skills for easy navigation.

5 / 5

Total

18

/

20

Passed

Description

92%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, concrete description that answers both what and when with specific actions and an explicit trigger clause; distinctiveness is well-handled by contrasting with external-runtime alternatives. The main weakness is a missing/misspelled framework name ('XCUIest') that slightly weakens trigger-term coverage.

Suggestions

Fix the typo 'XCUIest' to 'XCUITest' so the framework name itself acts as a natural trigger keyword.

Add common user phrasings like 'Xcode UI testing' or 'simulator UI tests' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - 'Authors XCUIest UI tests', 'uses the three-class XCUIApplication / XCUIElement / XCUIElementQuery pattern', 'sets accessibility identifiers', 'runs via xcodebuild test', 'parses the xcresult bundle' - giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what (authors tests using the three-class pattern, sets identifiers, runs xcodebuild, parses xcresult) and when ('Use when an iOS or macOS app needs UI tests in Apple's first-party framework'), with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Good natural-term coverage ('UI tests', 'iOS or macOS app', 'Apple's first-party framework', 'native to Xcode') but missing common synonyms users would say such as 'XCUITest' (the framework name itself, also misspelled as 'XCUIest'), 'Xcode UI testing', or 'simulator tests'.

4 / 5

Distinctiveness Conflict Risk

Clear niche - Apple's first-party XCUITest framework distinguished from alternatives via 'no external runtime; native to Xcode', with the macOS-specific delta offloaded to references/macos.md, giving minimal conflict risk with sibling skills like appium-testing or detox-testing.

5 / 5

Total

19

/

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.

Reviewed

Table of Contents