CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/xctest-mac-desktop

Authors and runs XCTest UI + unit tests for macOS desktop apps - the Apple-first-party test framework that ships with Xcode. Covers the `XCTestCase` subclass + `test*` method-naming convention, `XCUIApplication` / `XCUIElement` / `XCUIElementQuery` for UI tests, accessibility-identifier-based locators (the stable replacement for label-based queries), `XCTAssert*` macros, `measureBlock:` for performance regressions, and `xcodebuild test` for CI execution. Use when the macOS app is built with Xcode and the test target is in-tree alongside the app - for cross-OS sharing see Appium Mac2 driver as a separate path.

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Overview
Quality
Evals
Security
Files

Quality

Content

72%

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 XCTest skill with executable code and clean progressive disclosure to a real reference file. Weaker on conciseness (some repeated prose) and workflow_clarity (no explicit validate-retry checkpoint in the author-run-parse cycle).

Suggestions

Add an explicit validate-retry checkpoint between running tests and parsing results (e.g. 'if xcodebuild exits non-zero, parse the .xcresult failures, fix, re-run') to raise workflow_clarity.

Dedupe the inline Apple quotes that restate the same canonical pattern across Steps 1, 3, and 6, and trim the Anti-patterns table cross-references, to tighten conciseness.

Condense the Limitations section to the non-obvious caveats (per-device baselines, GPU-rendered content, sandbox restrictions) and drop restated strategic-frame pointers.

DimensionReasoningScore

Conciseness

Mostly lean with executable code and minimal concept-explanation, but Apple prose quotes are repeated inline, the Anti-patterns table reiterates Step cross-references, and the Limitations section is fairly long - it could be tightened without losing clarity. Not level 3 because some tokens do not earn their place; not level 2-below because it does not explain concepts Claude already knows.

2 / 3

Actionability

Provides copy-paste-ready executable Swift test code and concrete `xcodebuild test` commands with real flags (`-destination 'platform=macOS'`, `-only-testing:`, `-resultBundlePath`), plus specific `xcrun xcresulttool` usage. Fully actionable rather than descriptive.

3 / 3

Workflow Clarity

Steps 1-9 are clearly sequenced and the Anti-patterns table provides guardrails, but there is no explicit validation/checkpoint feedback loop (e.g. parse results -> diagnose failure -> re-run) for the author-run-parse cycle; the riskiest path defers to a referenced file. Not level 1 because the sequence is unambiguous; not level 3 because checkpoints are implicit rather than explicit.

2 / 3

Progressive Disclosure

SKILL.md is a well-organized overview spine that points one level deep to a verified real file (`references/ci-and-results.md`) via clearly signaled inline links, and content is appropriately split - results parsing and CI detail live in the reference, not the spine.

3 / 3

Total

10

/

12

Passed

Description

100%

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 precise, well-scoped description that names concrete capabilities, natural trigger terms, explicit use-when guidance, and a clear OS boundary. It is third-person and avoids fluff. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - authoring and running XCTest UI/unit/performance tests - and enumerates specific surfaces (`XCTestCase` subclass + `test*` convention, `XCUIApplication`/`XCUIElement`/`XCUIElementQuery`, accessibility-identifier locators, `XCTAssert*` macros, `measureBlock:`, `xcodebuild test`).

3 / 3

Completeness

Explicitly answers both what ('Authors and runs XCTest UI + unit tests for macOS desktop apps') and when ('Use when the macOS app is built with Xcode and the test target is in-tree alongside the app').

3 / 3

Trigger Term Quality

Covers natural terms a user would say - 'XCTest', 'macOS', 'UI tests', 'unit tests', 'xcodebuild', 'accessibility-identifier', 'Xcode' - with good coverage and no reliance on opaque jargon.

3 / 3

Distinctiveness Conflict Risk

Clear niche - Apple first-party XCTest for macOS desktop - and explicitly distinguishes the cross-OS path ('for cross-OS sharing see Appium Mac2 driver as a separate path'), making conflict with sibling skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents