CtrlK
BlogDocsLog inGet started
Tessl Logo

swift-concurrency-pro

Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls. Use when reading, writing, or reviewing Swift concurrency code.

81

1.23x
Quality

83%

Does it follow best practices?

Impact

94%

1.23x

Average score across 2 eval scenarios

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.

A well-structured, instruction-oriented review skill that delegates detail to a real, clearly-signaled reference bundle and provides concrete rules plus an output example. It is efficient and assumes Claude's intelligence, with only minor trimming and checkpoint opportunities.

Suggestions

Tighten the Output Format example: one condensed before/after block instead of two full code listings would preserve clarity while saving tokens.

Add a brief validation checkpoint in the review process (e.g. 'Re-confirm each flagged issue is genuine before writing it up') to reinforce the 'report only genuine problems' rule.

Consider folding one or two most-common concrete checks (e.g. the actor reentrancy pattern) inline so the body is actionable without loading a reference for routine reviews.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it does not explain Swift concurrency concepts — though the multi-block output example is somewhat lengthy and could be trimmed.

4 / 5

Actionability

Concrete, specific rules (e.g. 'Do not suggest @unchecked Sendable... Prefer actors, value types, or sending parameters') and a full output example give mostly executable guidance, but the per-step checks defer detail to reference files.

4 / 5

Workflow Clarity

The 12-step review process is clearly sequenced with conditional branches and a prioritized summary; this is a non-destructive review task so the validation-cap exception does not apply, leaving only minor checkpoint gaps.

4 / 5

Progressive Disclosure

The body is a well-organized overview that signals one-level-deep references (all 12 referenced files exist) with per-file descriptions, making navigation easy and keeping detail out of the main file.

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 concise, well-targeted description that clearly states both capability and trigger conditions with concrete, natural language. It is specific to Swift concurrency review and unlikely to fire for unrelated skills.

DimensionReasoningScore

Specificity

The description lists several specific review actions — 'concurrency correctness, modern API usage, and common async/await pitfalls' — giving concrete scope rather than vague language, with only minor coverage gaps.

4 / 5

Completeness

It explicitly answers both what ('Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls') and when ('Use when reading, writing, or reviewing Swift concurrency code') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural keywords users would say are well covered ('Swift code', 'concurrency', 'async/await', 'reading, writing, or reviewing'), though a few synonyms (e.g. actors, Task groups) are absent.

4 / 5

Distinctiveness Conflict Risk

The Swift concurrency review niche is distinct with specific triggers, creating minimal overlap risk with other 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.