CtrlK
BlogDocsLog inGet started
Tessl Logo

swiftui-view-refactor

Refactor SwiftUI view files into stable, testable structure. Use when splitting large views, tightening data flow, or cleaning Observation ownership.

66

Quality

78%

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 ./plugins/build-ios-apps/skills/swiftui-view-refactor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable and well-structured with concrete, executable Swift examples and a single well-signaled reference file. The main weaknesses are mild redundancy between the Core Guidelines and Workflow sections and the absence of an explicit build/test validation checkpoint in the refactor workflow.

Suggestions

Add an explicit validation checkpoint to the Workflow, e.g. a build/test step to confirm behavior is unchanged after refactoring.

Tighten redundancy by having the Workflow reference Core Guidelines by number rather than restating each guideline in different words.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes SwiftUI competence without explaining basics, but the Workflow section largely restates Core Guidelines 1–6 and Notes repeats earlier points, so not every token earns its place.

2 / 3

Actionability

Provides multiple executable Prefer/Avoid Swift code blocks, an explicit top-to-bottom property ordering, and concrete API guidance (@State, @Environment, @Query, .task(id:), init patterns).

3 / 3

Workflow Clarity

A 7-step Workflow is clearly sequenced, but it lacks explicit validation checkpoints (e.g., build/test to confirm behavior intact); step 7 states a constraint rather than a verify step, capping clarity at 2 for a code-modifying task.

2 / 3

Progressive Disclosure

A well-organized overview with one clearly signaled one-level-deep reference ('see references/mv-patterns.md', verified to exist) plus a web-search note for time-sensitive Apple docs.

3 / 3

Total

10

/

12

Passed

Description

85%Weight 40%Scale 1-3

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 tight, third-person description that pairs a concrete capability statement with an explicit 'Use when' trigger, covering both what and when. Trigger terms are mostly natural, though a couple lean toward jargon and some common phrasings are absent.

Suggestions

Broaden trigger terms with more common user phrasings such as 'break up' or 'extract subviews' alongside 'splitting large views'.

Soften jargon like 'cleaning Observation ownership' toward language a user would naturally say, e.g. 'fixing state/observable ownership'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Refactor SwiftUI view files into stable, testable structure', 'splitting large views', 'tightening data flow', 'cleaning Observation ownership' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Refactor SwiftUI view files into stable, testable structure') and when via an explicit 'Use when ...' trigger clause.

3 / 3

Trigger Term Quality

'SwiftUI' and 'splitting large views' are natural user terms, but 'tightening data flow' and 'cleaning Observation ownership' lean technical and common variations like 'break up a view' or 'extract subviews' are missing.

2 / 3

Distinctiveness Conflict Risk

The SwiftUI-specific niche ('SwiftUI view files', 'Observation ownership') gives it distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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
openai/plugins
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.