CtrlK
BlogDocsLog inGet started
Tessl Logo

swiftui-view-refactor

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

60

Quality

70%

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

75%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 an efficient, opinionated, and actionable guide with concrete Swift examples for every guideline and a clearly sequenced workflow. Its main gaps are minor: one truncated code example, no explicit post-refactor verification step, and some inline example bulk that could be moved to the existing reference file.

DimensionReasoningScore

Conciseness

The body is bullet-driven with no padding and no explanations of concepts Claude already knows; each of the three Swift examples earns its place, though the "header/filters" example is a truncated fragment that could be trimmed to one representative section.

4 / 5

Actionability

Concrete executable Swift snippets (the init(dependency:) pattern, HeaderSection extraction, subview split) cover the common cases, and the ordering rules are precise; one example is cut off mid-structure (the filters snippet), keeping it just below fully copy-paste ready.

4 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced with a confirmation checkpoint ("Confirm Observation usage") and a behavior-preservation guardrail ("do not change layout or business logic unless requested"); an explicit post-refactor verification step (e.g., re-checking behavior is intact) is the minor missing checkpoint.

4 / 5

Progressive Disclosure

Sections are well organized and the single reference (references/mv-patterns.md, which exists) is one level deep and clearly signaled; however, the three lengthy inline code examples and the two split-section guidelines could partly live in that reference, leaving minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

65%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 is concise and clearly scoped to a distinct SwiftUI niche, but it lacks any 'when to use' trigger guidance and only names two generic actions (refactor/review) supported by topic keywords. Adding an explicit 'Use when...' clause with natural trigger phrases would raise both completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. "Use when refactoring or reviewing SwiftUI views, or when the user mentions SwiftUI, view models, @Observable, or MV pattern."

Expand the action list beyond "refactor/review" to concrete capabilities such as "reorders view properties, splits large bodies into subviews, converts optional view models to non-optional @State initialized in init".

Include natural synonyms users might say ("MV pattern", "Observable", "SwiftUI code review") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"refactor/review" names two actions in the SwiftUI domain with topic keywords ("layout, DI, Observation, view models"), but no further concrete actions are listed, matching the '1-2 concrete actions, not comprehensive' anchor rather than the several-specific-actions anchor above.

3 / 5

Completeness

The 'what' is clear (refactor/review SwiftUI views for layout, DI, Observation, view models), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"SwiftUI", "view", "refactor", "view models", and "Observation" are natural phrases a SwiftUI user would say; a few natural variations (e.g., "MV", "SwiftUI view model extraction", "Observable") are missing, so it falls just below the comprehensive-coverage anchor.

4 / 5

Distinctiveness Conflict Risk

"SwiftUI view refactor/review" with "Observation" and "view models" is a clear niche with distinct triggers; virtually no overlap risk with non-SwiftUI skills, matching the minimal-conflict anchor.

5 / 5

Total

15

/

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