CtrlK
BlogDocsLog inGet started
Tessl Logo

swiftui-view-refactor

SwiftUI view refactor/review: layout, DI, Observation, view models.

58

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/swiftui-view-refactor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is lean, well-structured, and actionable with executable Swift examples and a clear workflow, deferring deeper MV rationale to a single one-level-deep reference. The main gap is the absence of explicit validation checkpoints in the workflow.

Suggestions

Add an explicit verification step to the workflow, e.g. step 6: 'Verify behavior is unchanged — build, and confirm layout/logic match the original unless a change was requested.'

Consider splitting MV/Observation rationale into a second reference or signaling the existing reference earlier in the body for better discovery.

Make the view-ordering rule (section 1) executable by showing a single before/after snippet that applies the full ordering, in addition to the scattered examples.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: numbered ordering rules, terse MV guidance, and executable Swift examples with no padding or re-explanation of concepts Claude already knows (the verbose rationale lives correctly in the reference file).

5 / 5

Actionability

Provides concrete, executable Swift code examples for splitting bodies, extracting subviews, and initializing view models, but ordering rules and some MV bullets are advisory rather than directly copy-pasteable, leaving minor gaps.

4 / 5

Workflow Clarity

The five-step Workflow section is clearly sequenced, but lacks explicit validation/checkpoint steps; per the destructive/batch cap this skill is not batch/destructive so no cap applies, yet a verify step (e.g. 'confirm behavior unchanged') is only implicit.

4 / 5

Progressive Disclosure

Well-organized sections with a clearly signaled, one-level-deep pointer to the real references/mv-patterns.md file; minor gap is that only one reference exists and the bulk rationale lives in the reference rather than more topic-specific splits.

4 / 5

Total

17

/

20

Passed

Description

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

The description concisely names the SwiftUI domain and several concrete refactoring concerns but lacks any 'Use when...' trigger guidance, capping completeness. It is distinctive but a user may not naturally invoke it from the trigger phrases alone.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when refactoring, reviewing, or restructuring SwiftUI views — especially around layout, dependency injection, Observation, or view-model usage.'

Include natural user-facing trigger terms/synonyms such as 'SwiftUI view', 'restructure view', 'MVVM', '@Observable', and 'view model'.

Consider listing 1-2 concrete actions ('reorder view properties', 'convert optional view models to non-optional @State') to lift specificity toward 5.

DimensionReasoningScore

Specificity

Lists several concrete focus areas ('layout, DI, Observation, view models') naming the SwiftUI domain and specific refactoring concerns, though these are topics rather than distinct executable actions, leaving minor coverage gaps.

4 / 5

Completeness

It gives a clear 'what' (refactor/review SwiftUI views) but provides no 'Use when...' clause or equivalent trigger guidance, so the 'when' is entirely missing.

2 / 5

Trigger Term Quality

'SwiftUI', 'refactor/review', and 'view models' are relevant but generic to the domain; it omits natural variations users say like 'SwiftUI view', 'MVVM', 'restructure view', or '@Observable' phrasings.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly specific (SwiftUI view refactoring with named patterns), mostly distinct from other skills with only minor overlap risk against generic Swift or code-review skills.

4 / 5

Total

13

/

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
steipete/agent-scripts
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.