CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

swift-code-review

Reviews Swift and SwiftUI pull requests, diffs, and changed code for evidence-backed correctness, concurrency, ownership, errors, Observation state, and lifecycle risks. Use when the requested deliverable is a code review, then route deep fixes to specialist skills.

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%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-engineered review skill: ordered workflow with explicit verification gates, a concrete output contract, and clean one-level-deep progressive disclosure to real reference files. The only improvement space is trimming minor duplication (TOC vs. headers, repeated SwiftLint and [weak self] guidance).

DimensionReasoningScore

Conciseness

The body is dense and assumes competence ("Review code as an evidence-backed diff review, not as a style sweep") with no re-teaching of known concepts, but the Contents TOC duplicates the section headers and a few rules appear twice ("[weak self]" guidance in both Common Mistakes and the checklist; SwiftLint deduplication in both Scope and Common Mistakes).

4 / 5

Actionability

Fully executable for an instruction-only skill: a copy-paste-ready output template with exact [FILE:LINE] proof requirements, a concrete command ("swiftlint lint --quiet"), explicit severity calibration ("Critical only for security, data corruption, happy-path crashes, or breaking public API changes"), and a named routing list of specialist skills.

5 / 5

Workflow Clarity

A six-step ordered workflow with explicit verification gates ("Verify each finding. Re-read the exact line and surrounding control flow", "Verify syntax and availability against current primary docs"), false-positive removal feedback, a review checklist, and a dedicated verification-protocol reference. Checkpoints are explicit rather than implicit, so it exceeds anchor 4.

5 / 5

Progressive Disclosure

The SKILL.md body is a concise overview and all five topic-labeled references (concurrency, observation, error-handling, common-mistakes, verification-protocol) exist as real files exactly one level deep with no nested .md chains, matching the well-signaled anchor-5 structure.

5 / 5

Total

19

/

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 description that states concrete capabilities, an explicit use-when trigger, and clear boundaries against specialist skills. The only gap is limited action-verb variety and missing common trigger synonyms like "PR" and ".swift".

DimensionReasoningScore

Specificity

Names concrete review inputs ("pull requests, diffs, and changed code") and six specific risk areas ("correctness, concurrency, ownership, errors, Observation state, and lifecycle risks"), but relies on only two action verbs ("Reviews", "route") rather than the multiple distinct actions of the anchor-5 example.

4 / 5

Completeness

Explicitly answers both what ("Reviews Swift and SwiftUI pull requests, diffs, and changed code for evidence-backed correctness, concurrency, ownership, errors, Observation state, and lifecycle risks") and when ("Use when the requested deliverable is a code review") with a concrete trigger phrase, matching the anchor-5 example rather than the merely-adequate anchor 4.

5 / 5

Trigger Term Quality

"Swift", "SwiftUI", "pull requests", "diffs", and "code review" are terms users would naturally say when requesting this skill. Common synonyms and file extensions ("PR", ".swift") are missing, so it falls short of comprehensive anchor-5 coverage but sits well above the partial keyword coverage of anchor 3.

4 / 5

Distinctiveness Conflict Risk

It carves a clear Swift/SwiftUI code-review niche and the clause "then route deep fixes to specialist skills" explicitly bounds it against adjacent specialist skills, giving minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

thienqo/ios-skills

Path

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