CtrlK
BlogDocsLog inGet started
Tessl Logo

review-swift-ios

Review a Swift change for SwiftUI body complexity, state property wrapper misuse, closure retain cycles, Swift concurrency and Core Data or SwiftData threading hazards, missing accessibility, monetary value handling, and semantic Xcode project or data model changes. Use when reviewing Swift, SwiftUI, UIKit, or iOS app code.

75

Quality

94%

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

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

An exemplary review-lens skill body: dense, expert-level, and immediately actionable, with a clear what-to-check / how-to-judge / what-to-report structure and explicit exclusions preventing noise. The only improvement would be an explicit verification step in the workflow, though for a code-review skill the current checkpoints are adequate.

DimensionReasoningScore

Conciseness

The body is lean and expert-level: every sentence carries specific diagnostic content (exact property wrappers, exact APIs like 'performAndWait', 'NSManagedObjectID', 'DispatchSemaphore.wait()', exact build settings like 'OTHER_SWIFT_FLAGS'), with zero explanation of concepts Claude already knows and no padding. Nothing to trim.

5 / 5

Actionability

Though it is an instruction-only skill with no code blocks, the guidance is fully concrete: it names exact wrong/right API pairs ('.sink { self.value = $0 } ... without [weak self]', '@ObservedObject on an object the view creates (should be @StateObject)'), the exact checks to run ('check whether the project builds with -strict-concurrency=complete or Swift 6'), and the exact fixes ('[weak self] or a stored cancellable', '@MainActor or perform', 'Decimal'). Per the rubric's scoring note, absence of code in an actionable instruction-only skill is not penalized.

5 / 5

Workflow Clarity

The Method → Threshold → Reporting sections form a coherent review sequence with decision checkpoints (verify strict-concurrency/Swift version before judging severity; read the AGENTS.md/CLAUDE.md chain for project rules), but there are no explicit validation or error-recovery steps — matching the 4 anchor ('clear sequence with most checkpoints present'). Not 5 because no explicit verify/feedback loop exists; not 3 because the sequence is well-defined and this is a non-destructive review task where the cap does not apply.

4 / 5

Progressive Disclosure

The body is under 50 lines, needs no external reference files (none exist in the bundle), and is organized into clearly labeled sections (Scope, Method, Threshold, Reporting) — meeting the rubric's simple-skill guideline for a top score.

5 / 5

Total

19

/

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.

A strong description: it lists concrete capabilities across the skill's full scope, uses third-person imperative voice, and closes with an explicit 'Use when' trigger clause naming the platform keywords. The only gap is minor — a few natural synonyms like 'Swift file' or '.swift' could be added.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — 'SwiftUI body complexity, state property wrapper misuse, closure retain cycles, Swift concurrency and Core Data or SwiftData threading hazards, missing accessibility, monetary value handling, and semantic Xcode project or data model changes' — comprehensively covering the skill's scope with specific, non-generic actions.

5 / 5

Completeness

Both parts are explicit: the 'what' is a concrete list of review capabilities, and the 'when' is a clear trigger clause — 'Use when reviewing Swift, SwiftUI, UIKit, or iOS app code.' This matches the 5 anchor exactly.

5 / 5

Trigger Term Quality

Good natural-term coverage ('Swift, SwiftUI, UIKit, or iOS app code', 'Core Data', 'SwiftData', 'Xcode project'), but a few natural phrases users would say are missing, such as 'Swift file', '.swift', or 'Swift code review'. Not 5 because synonym/extension coverage is incomplete; not 3 because the terms present are the ones users most naturally say for this niche.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Swift/iOS code review) with distinct platform-specific triggers (SwiftUI, UIKit, Core Data/SwiftData, .pbxproj/.xcdatamodeld concerns) that would not fire for unrelated skills; conflict risk is minimal.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
perihelionhq/perihelion-platform-context
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.