CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

swift-testing

API reference: Swift Testing framework. @Test, @Suite, #expect, #require, traits, parameterized tests, migrating from XCTest.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/swift-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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-organized, token-efficient index whose written structure and lookup workflow are sound, but whose substance is hollow: every reference file it points to is missing from the bundle, so the skill delivers almost no reference content as shipped. The lookup fallback chain partially compensates by routing to other installed skills and an external mirror.

Suggestions

Ship the seven referenced .md files in the skill bundle, or inline the essential API details into SKILL.md so the index has actual targets.

Remove or relocate the "iOS 26+" version claim to a compatibility/deprecated section so it does not age the skill's main body.

Trim the justification sentence in step 2 ("This is faster and uses less context...") to keep the body maximally lean.

DimensionReasoningScore

Conciseness

The ~20-line body is lean: a one-line intro, a minimal index table, and a three-step lookup sequence that assumes Claude's competence. It is not 5 because of the time-sensitive "iOS 26+" version claim outside any deprecated/compatibility section and the trimmable justification sentence "This is faster and uses less context than fetching new docs from the internet."

4 / 5

Actionability

The lookup guidance is concrete and executable: "Search this skill's local `.md` files first", "grep their local files", and an explicit URL mapping ("/documentation/testing/test" → "https://sosumi.ai/documentation/testing/test"). It is not 5 because the primary lookup target — the seven referenced reference files — is absent from the bundle, leaving the main action (consulting local reference docs) with nothing to act on.

4 / 5

Workflow Clarity

"Fetching More Docs" is a clearly numbered three-step fallback sequence (local files → other installed skills → the sosumi.ai mirror) with an explicit escalation rule; as a read-only lookup there is no destructive step requiring validation, and the simple-skill allowance would permit a 5. It drops to 4 because step 1 directs Claude to search local .md files that do not exist in the bundle, dead-ending the sequence's premise.

4 / 5

Progressive Disclosure

Structurally the body is a textbook index — a table of seven one-level-deep, clearly signaled references — but per the judging guidelines it must be scored against the actual bundle: none of the seven referenced files (testing-overview.md, defining-tests.md, organizing-tests.md, expectations.md, parameterized-testing.md, traits.md, migrating-from-xctest.md) exist in the skill directory. The entire detail layer is missing, so navigation to any content is broken in practice. Not 1 because the written structure itself is clean and the remaining instruction (the external URL mapping) still resolves.

2 / 5

Total

14

/

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.

A concise, highly specific description that enumerates the framework's distinctive API symbols and topics. Its main weakness is the complete absence of explicit 'when to use' trigger guidance, which caps completeness, and its reliance on topic nouns rather than stated actions.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing or debugging Swift tests, or when the user mentions @Test, #expect, or migrating XCTest suites."

Phrase capabilities as actions (e.g., "Look up @Test, @Suite, and #expect syntax...") rather than presenting a bare topic list.

Include natural user variations such as "Swift unit tests" or "swift-testing" to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("API reference: Swift Testing framework") and lists seven concrete items ("@Test, @Suite, #expect, #require, traits, parameterized tests, migrating from XCTest"), matching the 'lists several specific items with minor gaps' anchor. It falls short of 5 because the items are topics/symbols rather than actions, and there is no statement of what the skill actually does with them.

4 / 5

Completeness

The 'what' is clear ("API reference: Swift Testing framework" plus its topic coverage), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3. It is not 2 because the 'what' half is concrete and specific, not vague.

3 / 5

Trigger Term Quality

Phrases like "@Test", "#expect", "#require", "parameterized tests", and "migrating from XCTest" are exactly what a Swift developer would say when they need this skill, giving good keyword coverage. It is not 5 because common natural variations such as "Swift unit tests", "swift-testing", or "test suites" are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — Apple's Swift Testing framework with distinctive symbols like "@Test" and "#expect" — but "migrating from XCTest" and "parameterized tests" could also plausibly trigger a general XCTest or Swift-testing skill, giving minor overlap risk with closely related skills. Not 5 because of that shared-trigger overlap; not 3 because the framework-specific symbols are unambiguous.

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: 7 missing

Warning

Total

14

/

16

Passed

Repository

Prisma-Labs-Dev/apple-skills

Path

skills/swift-testing/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.