CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

xcuitest

API reference: XCUITest. Query for element queries, waiting patterns, Swift 6 @MainActor, assertions, screenshots, launch arguments.

Quality

75%

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

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 well-structured reference skill: lean body, a copy-paste-ready Quick Reference, clearly labeled one-level-deep reference tables, and a sensible lookup escalation workflow. The main gaps are a trimmable Sources section, no inline snippets for the most common patterns beyond the basic test, and referenced bundle files that were not present to verify in the evaluated bundle.

Suggestions

Trim or condense the Sources section; the Apple documentation links duplicate the locally downloaded XCTest/XCUIAutomation indexes.

Add one or two inline snippet lines for the highest-frequency patterns (e.g. a non-existence wait or a launch-argument setup) so the most common queries don't require opening a referenced file.

Ensure all referenced topic-guide and downloaded-reference .md files ship with the skill bundle so every link in the tables resolves.

DimensionReasoningScore

Conciseness

The body is lean: a compact Quick Reference snippet, two efficient file/content tables, and a short escalation workflow, with no explanation of concepts Claude already knows. The ~28-line Sources section of external links (many redundant with the downloaded indexes) is trimmable, keeping it at anchor 4 rather than the every-token-earns-its-place 5.

4 / 5

Actionability

The Quick Reference is a complete, executable Swift test class ('@MainActor final class MyUITests... XCTAssertTrue(button.waitForExistence(timeout: 5))') and the 'Fetching More Apple Docs' section gives a concrete example path mapping. It stops short of 5 because the common cases beyond basic structure/wait/tap (waiting patterns, launch arguments, permissions) are delegated entirely to referenced files with no inline snippets.

4 / 5

Workflow Clarity

The 'Fetching More Apple Docs' section lays out a clearly sequenced three-step escalation (local .md files, then other installed skills, then the sosumi.ai mirror with an example mapping), which matches 'clear sequence with most checkpoints present'. It is not 5 because there are no validation or error-recovery steps (e.g. what to do when a mirrored page is stale or missing).

4 / 5

Progressive Disclosure

The structure matches the top anchor — a concise overview with well-signaled, one-level-deep references in two tables, each with a content summary. However, none of the 19 referenced .md files (element-queries.md, xctest-index.md, etc.) exist in the skill bundle as evaluated, so navigation to them cannot be verified, which is a minor organization gap keeping it at 4.

4 / 5

Total

16

/

20

Passed

Description

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

The description is specific and distinctive, clearly scoping an XCUITest API reference with six concrete topic areas. Its main weakness is the missing 'Use when...' trigger clause, which caps completeness and leaves activation guidance implicit, and it omits common phrasings like 'UI testing' or 'UI tests'. Adding an explicit trigger sentence with those synonyms would raise it to the top band.

Suggestions

Add an explicit trigger clause, e.g. 'Use when writing or debugging XCUITest/UI tests, or when the user mentions XCUITest, waitForExistence, UI test flakiness, or XCUIApplication.'

Include common user phrasings such as 'UI tests', 'UI testing', 'XCTest', and 'flaky tests' alongside the framework jargon to broaden natural trigger coverage.

Rewrite 'Query for element queries...' as concrete actions (e.g. 'Look up element queries, waiting patterns...') to remove the redundant phrasing.

DimensionReasoningScore

Specificity

Lists six concrete topics ("element queries, waiting patterns, Swift 6 @MainActor, assertions, screenshots, launch arguments") rather than vague language, matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because these are topic labels for an API reference rather than comprehensive concrete actions, and 'Query for element queries' is awkward phrasing.

4 / 5

Completeness

The 'what' is clear ("API reference: XCUITest" plus a topic list) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the 'when' is only weakly implied by naming the framework.

3 / 5

Trigger Term Quality

Includes natural terms users say when working with this skill ("XCUITest", "Swift 6 @MainActor", "launch arguments", "screenshots"), but misses common variations like "UI tests", "UI testing", "XCTest", or "flaky tests". Good coverage with a few natural terms missing fits anchor 4, not the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

XCUITest is a specific framework with a clear niche and distinct triggers, but the skill body itself references 'other installed Apple skills', indicating minor overlap risk with closely related XCTest/Apple documentation skills. Mostly distinct with minor overlap risk fits anchor 4 rather than the minimal-conflict 5.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 19 missing

Warning

Total

14

/

16

Passed

Repository

Prisma-Labs-Dev/apple-skills

Path

skills/xcuitest/SKILL.md

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.