CtrlK
BlogDocsLog inGet started
Tessl Logo

macos-window-management

Customize macOS SwiftUI windows and scene behavior. Use when tuning window chrome, drag regions, placement, restoration, launch behavior, or borderless windows.

67

Quality

80%

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

73%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 well-structured, role-driven, and grounded in real macOS 15+ SwiftUI APIs, with a workflow that includes explicit verification and a fallback path. Its main weakness is redundancy: the Review Checklist and Guardrails sections largely restate the per-topic bullets, which inflates token cost without adding new guidance.

Suggestions

Cut the Review Checklist and Guardrails overlap: merge them into a single short checklist of items not already stated in the section bullets, or delete the checklist and keep only the Guardrails' unique 'do not' items, saving ~25 lines.

Promote the reference to a clearly signposted line (e.g. a '## API Examples' section or a pointer in the Workflow): "For concrete window modifier examples, read `references/api-snippets.md`" is currently buried at the end of the Borderless section.

Tighten prose bullets like the placement section, where "Treat default placement and ideal placement as separate policies" restates what the preceding two bullets already demonstrate.

DimensionReasoningScore

Conciseness

The body avoids beginner-concept padding, but the Review Checklist ("Windows with hidden or removed toolbars still have a reliable drag region...") and Guardrails ("Do not hide the toolbar background or the whole toolbar without replacing the lost drag affordance") substantially restate the section content. More than minor tightening is needed, so it sits at 3 rather than 4.

3 / 5

Actionability

Concrete real APIs appear throughout (`.toolbar(removing: .title)`, `WindowDragGesture()`, `.containerBackground(.thickMaterial, for: .window)`, `.defaultWindowPlacement` with `content.sizeThatFits(.unspecified)` and `context.defaultDisplay.visibleRect`). Not a 5 because no copy-paste-ready code is inline; the executable examples live in the reference file.

4 / 5

Workflow Clarity

The 7-step Workflow has a clear sequence, an explicit verification step ("Build and launch the app with `macos-build-run-debug` to verify the result"), a Review Checklist, and an error-recovery fallback ("switch to `macos-appkit-interop` for a narrow `NSWindow` bridge"). No destructive/batch operation is involved, so no cap applies.

5 / 5

Progressive Disclosure

A single, real, one-level-deep reference (`references/api-snippets.md`, verified to exist with concrete examples) keeps code out of the overview. However, it is signaled by one sentence at the end of the Borderless section rather than a clearly signposted navigation point, a minor organization gap that keeps it at 4.

4 / 5

Total

16

/

20

Passed

Description

87%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: it names a specific platform/framework niche, states what the skill does, and gives an explicit 'Use when' clause with concrete trigger areas. Trigger synonyms could be slightly broadened (title bar, toolbar, zoom), but it is concise, third-person, and highly distinguishable from related skills.

DimensionReasoningScore

Specificity

"Customize macOS SwiftUI windows and scene behavior" names the domain, and the trigger list enumerates several concrete sub-actions ("window chrome, drag regions, placement, restoration, launch behavior, or borderless windows"). Not a 5 because the headline 'what' is a single generic verb rather than multiple distinct named actions.

4 / 5

Completeness

Explicitly answers both "what" (customize macOS SwiftUI windows and scene behavior) and "when" ("Use when tuning window chrome, drag regions, placement, restoration, launch behavior, or borderless windows") with concrete trigger phrases, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

"window chrome", "drag regions", "placement", "restoration", and "borderless windows" are natural user phrasings. A few common synonyms are missing (e.g. "title bar", "toolbar", "zoom", "window position"), keeping it below the comprehensive 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (macOS SwiftUI scene/window APIs) with distinct triggers and minimal conflict risk against sibling skills covering broader SwiftUI architecture, visual materials, or AppKit interop.

5 / 5

Total

18

/

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
robinebers/openusage
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.