CtrlK
BlogDocsLog inGet started
Tessl Logo

window-management

Customize macOS 15+ SwiftUI windows and scene behavior using Window, WindowGroup, and macOS window modifiers. Use when styling or hiding window toolbars and titles, extending drag regions with WindowDragGesture, replacing window backgrounds with materials, disabling minimize or restoration for utility windows, setting default or ideal window placement from content/display size, creating borderless windows, or tuning default launch behavior.

69

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.

The body is well-structured, actionable, and concise, with concrete Swift snippets and a sensible workflow. Fleshing out the placement helper functions and tightening checklist/guardrail overlap would lift it further.

Suggestions

Replace the clampToDisplay/zoomToFit/centeredPosition placeholders in the placement snippet with real implementations or a brief inline definition so the example is fully copy-paste runnable.

Consolidate overlapping items between the Review Checklist and Guardrails (e.g., drag-region and restoration guidance) to reduce redundancy and tighten token use.

Add an explicit validate-fix-retry note after the build-run-debug step so the verification loop is unambiguous even though the operation is non-destructive.

DimensionReasoningScore

Conciseness

Lean, competence-assuming prose with no padding about basic SwiftUI/window concepts; minor redundancy between Guardrails and Review Checklist could be trimmed.

4 / 5

Actionability

Concrete, copy-paste Swift snippets cover the common cases per section, but helper placeholders like clampToDisplay/zoomToFit in the placement example are not fully executable.

4 / 5

Workflow Clarity

A clear numbered workflow includes a build-run-debug verification step and a Review Checklist; this is not a destructive/batch operation, so the missing explicit validate-fix-retry loop is a minor gap rather than a cap.

4 / 5

Progressive Disclosure

Well-organized sections with clear headers and a 'When To Use Other Skills' navigation block; no bundle files exist, so appropriately inline content is well-structured with only minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

92%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.

The description is specific, complete, and well-targeted, clearly stating both capabilities and trigger scenarios. It could add a couple more plain-language synonyms to push trigger-term quality to full marks.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—styling/hiding toolbars, WindowDragGesture drag regions, material backgrounds, disabling minimize/restoration, default/ideal placement, borderless windows, launch behavior—giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers what ('Customize macOS 15+ SwiftUI windows and scene behavior...') and when (an explicit 'Use when...' clause enumerating concrete trigger phrases).

5 / 5

Trigger Term Quality

Natural scenario triggers like 'styling or hiding window toolbars and titles', 'utility windows', and 'borderless windows' read well, though coverage leans on API names over plain-language synonyms.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow macOS 15+ SwiftUI window/scene API niche with distinct triggers, minimizing overlap with adjacent skills.

5 / 5

Total

19

/

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.