CtrlK
BlogDocsLog inGet started
Tessl Logo

swift-testing-pro

Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

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.

Well-structured content that uses progressive disclosure effectively, with a clear review workflow and concrete output examples. Slight conciseness padding and the delegation of actionable detail to reference files keep three dimensions at 4.

Suggestions

Trim the meta-commentary about release cadence and training-data staleness in 'Core Instructions' — Claude already knows its training data lags, so these tokens add little actionable value.

Inline one or two of the highest-frequency rules (e.g. struct-over-class, #expect vs #require) directly in the body so the most common actions do not require loading a reference file.

Add an explicit verification checkpoint to the review process (e.g. 'Re-check that suggested APIs compile against the user's installed toolchain before reporting') to close the validation gap in the workflow.

DimensionReasoningScore

Conciseness

The body is mostly lean and delegates detail to references, but meta-commentary such as 'expect three to four releases each year' and 'existing training data you have will naturally be outdated' over-explains concepts Claude already knows, leaving minor trimmable padding.

4 / 5

Actionability

The review process maps each task to a specific reference file and the output format provides copy-paste before/after code (struct vs class, #expect, #require), but most technical depth lives in the bundled references rather than inline, leaving minor gaps.

4 / 5

Workflow Clarity

A clear numbered review sequence (1-5) with per-task reference loading and a sequenced output format ending in a prioritized summary; this is a review/writing task rather than a destructive batch operation, so the missing explicit validation feedback loop is a minor gap rather than a cap.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview pointing to five one-level-deep reference files, each cited inline in the review process and listed with descriptions in a References section; all referenced files exist in references/, giving clear navigation.

5 / 5

Total

17

/

20

Passed

Description

87%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, third-person description that clearly states capabilities and provides an explicit 'Use when' trigger tied to a specific framework niche. Minor specificity and synonym-coverage gaps keep it just short of perfect on two dimensions.

DimensionReasoningScore

Specificity

Names the domain (Swift Testing) and three concrete actions — 'Writes, reviews, and improves' — but 'improves' is slightly generic and coverage is not exhaustive, so it sits at anchor 4 rather than 5.

4 / 5

Completeness

Explicitly answers both what ('Writes, reviews, and improves Swift Testing code using modern APIs and best practices') and when ('Use when reading, writing, or reviewing projects that use Swift Testing') with concrete trigger phrases, matching the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Natural phrases like 'reading, writing, or reviewing projects that use Swift Testing' map well to what a user would say, but synonyms (e.g. 'unit tests', 'XCTest migration') are missing, keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

'Swift Testing' is a clearly delineated framework niche with distinct triggers, and the 'Use when ... projects that use Swift Testing' clause minimizes overlap with general Swift or XCTest skills.

5 / 5

Total

18

/

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.

Repository
jacklandrin/OnlySwitch
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.