Name: guide-swift-testing
Rating: 69.6 (1 reviews)
Author: Prisma-Labs-Dev

guide-swift-testing

Swift Testing patterns — structs over classes, async confirmations, parameterized tests, exit tests, attachments, common agent mistakes. Use when writing, reviewing, or migrating Swift Testing code.

Quality

85%

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

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

The body is a well-structured, token-efficient guide that routes Claude through a clear review process to five appropriately split reference files. Its main weakness is actionability: the SKILL.md body itself contains little executable pattern guidance, delegating nearly all concrete detail to the references.

Suggestions

Inline 1–2 short, representative code patterns (e.g., a parameterized test or async confirmation snippet) so the body is actionable without forcing a reference load for common cases.

Add a brief 'what to report / how to report findings' note so the review workflow has an explicit output checkpoint rather than an implicit one.

State the expected output format or severity levels for reported problems to give the review process a concrete validation step.

Dimension	Reasoning	Score
Conciseness	The body is lean — three core-instruction bullets, a five-step review process, and a reference table — and assumes Claude's competence without explaining what Swift Testing is or how libraries work.	5 / 5
Actionability	The core directives ('Target Swift 6.2 or later', 'Do not rewrite existing XCTest') are concrete, but the body mostly routes Claude to reference files for the actual assertion patterns and code-level guidance, leaving the standalone body incomplete as actionable instruction.	3 / 5
Workflow Clarity	The Review Process is a clear numbered 1–5 sequence with a conditional migration step and partial-work guidance; validation checkpoints are only implicit, but review is non-destructive so the destructive/batch cap does not apply.	4 / 5
Progressive Disclosure	SKILL.md is a concise overview pointing one level deep to five real reference files (all present in references/), with a well-signaled topic-to-file table making navigation easy.	5 / 5
	Total	17 / 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.

The description is specific, complete, and well-targeted: it enumerates concrete Swift Testing patterns and gives an explicit 'Use when' trigger tied to writing, reviewing, or migrating. Its only gap is trigger-term breadth — it omits synonyms like 'XCTest' and file extensions that users might naturally say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'structs over classes, async confirmations, parameterized tests, exit tests, attachments, common agent mistakes' — giving comprehensive coverage of the skill's scope rather than vague abstraction.	5 / 5
Completeness	Explicitly states what it covers (the pattern list) and when to use it ('Use when writing, reviewing, or migrating Swift Testing code'), matching the anchor for clear what-and-when with concrete triggers.	5 / 5
Trigger Term Quality	'writing, reviewing, or migrating Swift Testing code' are natural user phrases, but coverage is missing common synonyms (e.g., 'XCTest', 'unit tests') and any file extensions, so it stops just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	'Swift Testing' is a well-defined niche with distinct triggers and minimal overlap risk; the body even carves out XCTest UI tests as out of scope.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Prisma-Labs-Dev/apple-skills
Path: skills/guide-swift-testing/SKILL.md
Commit: 4986260

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.