CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

view-refactor

Refactor macOS SwiftUI views and scenes into stable structure. Use when splitting large views, tightening scene state, or narrowing AppKit escapes.

66

Quality

83%

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

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.

A well-organized, dense instructional skill: every rule is a specific directive rather than background explanation, and the workflow is clearly sequenced with a build-validation habit. The body would be slightly stronger if the Checklist and Common Smells sections were consolidated and the build checkpoint were made an explicit workflow step with a fix-and-retry loop.

Suggestions

Embed the validation loop directly in the Workflow (e.g., 'Build after each major split; if errors appear, fix locally before continuing') rather than leaving it only in the Refactor Checklist.

Merge or trim the overlapping 'Refactor Checklist' and 'Common Smells' sections, which largely restate the Core Guidelines, to reduce redundancy.

Add one short before/after code sketch of a bloated root view versus the split result to ground guidelines 2b and 3 concretely.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence (never explains what SwiftUI or AppKit is), and every guideline is actionable prose, but "Common Smells" and "Refactor Checklist" partially restate the Core Guidelines, leaving minor tightening opportunities.

4 / 5

Actionability

Guidance is concrete and executable: an exact member-ordering list, specific file paths (App/<AppName>App.swift, Views/SidebarView.swift, Stores/, Services/), a numeric threshold ("roughly under 50 lines"), and named property wrappers. Minor gaps remain — e.g., no illustrative before/after snippet for the worst smells.

4 / 5

Workflow Clarity

The 7-step Workflow is clearly sequenced and includes a behavior-preservation guard (step 7), and the Checklist contains a validation checkpoint ("Build after each major split so compile errors stay local"), but that build-verify loop is not embedded as an explicit workflow step, so it falls short of anchor 5's feedback-loop structure.

4 / 5

Progressive Disclosure

No bundle files exist and the single-file body is well-sectioned (Overview, Core Guidelines, Workflow, Checklist, Smells, Notes), so nothing that belongs in a separate file is inlined. It misses anchor 5 because at ~105 lines it exceeds the simple-skill exception and carries minor redundancy across sections.

4 / 5

Total

16

/

20

Passed

Description

83%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: third-person voice, concise, with an explicit 'Use when...' clause carrying three concrete trigger phrases. The main improvement opportunity is tightening the slightly abstract headline ("into stable structure") and adding a couple of natural synonyms.

DimensionReasoningScore

Specificity

The description names the domain ("Refactor macOS SwiftUI views and scenes") and lists several concrete actions ("splitting large views, tightening scene state, or narrowing AppKit escapes"), but the headline action "into stable structure" is slightly abstract, keeping it below the comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers both what ("Refactor macOS SwiftUI views and scenes into stable structure") and when ("Use when splitting large views, tightening scene state, or narrowing AppKit escapes") with concrete trigger phrases, matching the top anchor. It is not a 4 because the 'when' clause is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ("refactor", "splitting large views", "AppKit", "scene state", "macOS SwiftUI"), but common synonyms and file extensions (e.g., ".swift", "SwiftUI view refactor") are missing, so it does not reach comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

The macOS SwiftUI/AppKit refactoring niche is clearly distinct, but "splitting large views" and scene work overlap with closely related skills the body itself defers to (swiftui-patterns, appkit-interop), so minor overlap risk remains.

4 / 5

Total

17

/

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

openai/plugins

Path

plugins/build-macos-apps/skills/view-refactor/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.