CtrlK
BlogDocsLog inGet started
Tessl Logo

macos-appkit-interop

Bridge macOS SwiftUI into AppKit narrowly. Use when implementing representables, reaching NSWindow or panels, handling menus, or using the responder chain.

80

Quality

100%

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

100%

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

A well-organized, instruction-style skill that gives concrete type-selection guidance, a sequenced workflow with an explicit validation checkpoint, and clean one-level-deep references that all resolve to real bundle files. It earns its tokens without padding and stays actionable without requiring code snippets.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what SwiftUI/AppKit are and jumps straight to decision guidance; the only mild redundancy is the "smallest bridge" motif echoed across the bridge section and workflow step 2.

3 / 3

Actionability

Concrete and specific throughout: it names exact bridge types (NSViewRepresentable, NSViewControllerRepresentable), exact AppKit surfaces (NSWindow, responder-chain, panels, pasteboard), and a capability-gap taxonomy that maps each gap to a concrete type and ownership boundary.

3 / 3

Workflow Clarity

A clearly sequenced 5-step workflow with checklist sub-bullets and an explicit validation step ("Validate lifecycle assumptions") enumerating concrete risks like representable recreation.

3 / 3

Progressive Disclosure

The body is an overview with a well-signaled References section pointing one level deep to four real files, each with a one-line description; verified the referenced files exist and contain no further nested references.

3 / 3

Total

12

/

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.

A tight, third-person description that names concrete capabilities and pairs them with an explicit "Use when" trigger clause. It cleanly answers both what the skill does and when to invoke it, with low conflict risk against adjacent SwiftUI skills.

DimensionReasoningScore

Specificity

Multiple concrete capabilities are named — "implementing representables, reaching NSWindow or panels, handling menus, or using the responder chain" — alongside the core action "Bridge macOS SwiftUI into AppKit narrowly".

3 / 3

Completeness

It states what ("Bridge macOS SwiftUI into AppKit narrowly") and gives an explicit "Use when ..." trigger clause enumerating the situations, satisfying both what and when.

3 / 3

Trigger Term Quality

Terms a macOS developer would naturally say (representables, NSWindow, panels, menus, responder chain, SwiftUI, AppKit) are well covered across the trigger clause.

3 / 3

Distinctiveness Conflict Risk

The SwiftUI↔AppKit interop niche is sharply bounded by distinct triggers (representables, NSWindow, responder chain, panels) that are unlikely to fire for a general SwiftUI skill.

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