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

81%

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

78%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 tightly organized, instruction-only skill that names exact SwiftUI window/scene APIs for each scenario and offloads executable examples to a single well-signaled reference file. Its workflow includes a build-and-verify checkpoint and a review checklist, with only minor redundancy and missing error-recovery feedback.

DimensionReasoningScore

Conciseness

The body is directive and assumes SwiftUI/window competence without explaining basics, but the Guardrails section restates several rules already covered in the topical sections (e.g. drag affordance, restoration), which is minor redundancy that could be trimmed.

4 / 5

Actionability

It names exact, copy-ready API signatures per situation (e.g. '.toolbarBackgroundVisibility(.hidden, for: .windowToolbar)', '.defaultWindowPlacement { content, context in ... }', 'content.sizeThatFits(.unspecified)') and routes to references/api-snippets.md for full executable examples; the only gap is that complete code lives one hop away in the reference rather than inline.

4 / 5

Workflow Clarity

A clear 7-step workflow is sequenced with an explicit verify checkpoint (build and launch with macos-build-run-debug) plus a Review Checklist, but there is no explicit if-fails-then-fix feedback loop, leaving a minor validation gap below the 5 anchor.

4 / 5

Progressive Disclosure

SKILL.md is a lean, well-sectioned overview and the single concrete-example bundle is split out behind one clearly signaled one-level-deep reference ('For concrete window modifier examples, read references/api-snippets.md'), which exists and is well organized, matching the 5 anchor.

5 / 5

Total

17

/

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 well-constructed description that clearly states both capability and explicit trigger conditions with concrete, domain-specific keywords. It is mostly distinct from sibling macOS skills with only minor overlap risk.

DimensionReasoningScore

Specificity

Names the domain ('macOS SwiftUI windows and scene behavior') and the 'Use when' clause enumerates six concrete sub-actions (chrome, drag regions, placement, restoration, launch behavior, borderless), but the primary verb is the generic 'Customize' rather than multiple distinct action verbs, so it stops short of the comprehensive 5 anchor.

4 / 5

Completeness

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

5 / 5

Trigger Term Quality

Natural developer-facing terms like 'window chrome', 'drag regions', 'placement', 'restoration', 'launch behavior', and 'borderless windows' give good keyword coverage; a few common synonyms users might say (e.g. 'title bar', 'toolbar', 'window controls') are folded under 'chrome' rather than stated, leaving minor gaps.

4 / 5

Distinctiveness Conflict Risk

The macOS SwiftUI window/scene niche is clearly scoped with distinct triggers, but the body itself notes overlap with sibling skills (macos-swiftui-patterns, macos-liquid-glass, macos-appkit-interop), indicating minor overlap risk with closely related skills rather than minimal conflict.

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.

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