CtrlK
BlogDocsLog inGet started
Tessl Logo

view-refactor

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

72

Quality

88%

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

77%

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

The content is lean, well-structured, and offers a sequenced workflow with a build-validation checkpoint, but it stays monolithic with no progressive file disclosure and would benefit from concrete before/after refactor code examples.

Suggestions

Add a short before/after Swift example under "Extract ... subview types" or "Keep selection and layout stable" to make the refactor guidance executable rather than only descriptive.

Move the detailed file-shape ordering and directory conventions into a references file (e.g. references/file-layout.md) and summarize it in the body, improving progressive disclosure for a skill over 50 lines.

Inline the "Build after each major split" validation step into the Workflow steps themselves so the feedback loop sits directly in the sequence rather than only in the checklist.

DimensionReasoningScore

Conciseness

The body is lean and bullet-driven, assumes Claude's competence (e.g. "Follow this ordering unless the file already has a stronger local convention"), and avoids explaining SwiftUI/AppKit basics Claude already knows.

3 / 3

Actionability

Guidance is concrete with specific paths ("App/<AppName>App.swift", "Views/ContentView.swift", "Services/*.swift") and an explicit property ordering, but a refactor skill lacks before/after code examples that would make it fully executable.

2 / 3

Workflow Clarity

The seven-step Workflow is clearly sequenced and paired with a Refactor Checklist that includes an explicit validation checkpoint ("Build after each major split so compile errors stay local"), providing a feedback loop for the structurally risky refactor.

3 / 3

Progressive Disclosure

Sections are well-organized (Overview, Core Guidelines, Workflow, Checklist, Smells, Notes), but the skill is a monolithic single file over 50 lines with no bundle references to offload detail; the only cross-links ("swiftui-patterns", "appkit-interop") point to sibling skills, not bundle files.

2 / 3

Total

10

/

12

Passed

Description

100%

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, third-person, and clearly answers both what the skill does and when to use it with concrete, natural trigger terms. It is highly specific to the macOS SwiftUI refactor niche with low conflict risk.

DimensionReasoningScore

Specificity

"Refactor macOS SwiftUI views and scenes into stable structure" plus "splitting large views, tightening scene state, or narrowing AppKit escapes" names the domain and multiple concrete refactor actions rather than vague language.

3 / 3

Completeness

It states what the skill does ("Refactor macOS SwiftUI views and scenes into stable structure") and explicitly when to use it via a "Use when..." clause with concrete triggers, satisfying both halves.

3 / 3

Trigger Term Quality

Phrases like "splitting large views", "tightening scene state", and "narrowing AppKit escapes" are natural terms a user would actually say when requesting this kind of refactor work.

3 / 3

Distinctiveness Conflict Risk

The macOS SwiftUI scene/view refactor niche is specific and the AppKit-escape trigger is distinctive, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.