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.

71

Quality

86%

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

86%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 tight, well-organized decision skill that assumes competence, splits detail into clearly signaled one-level references (all verified to exist), and provides a sequenced workflow with a validation checkpoint. Actionability and workflow_clarity land at 4 due to the absence of executable code and an explicit feedback loop.

DimensionReasoningScore

Conciseness

Lean and efficient throughout; never explains what SwiftUI/AppKit are, assumes Claude's competence, and every section (Quick Start, Choose The Smallest Bridge, Workflow, Guardrails, Output Expectations) earns its place.

5 / 5

Actionability

Concrete, specific decision guidance with named types (NSViewRepresentable, NSViewControllerRepresentable, NSWindow) and clear when-to-use criteria; score 4 not 5 because, as an instruction-only skill, it provides decision rules rather than copy-paste executable code, though the guidance is actionable.

4 / 5

Workflow Clarity

A clear five-step sequence (name the gap, pick the smallest boundary, keep ownership explicit, expose a narrow interface, validate lifecycle) with an explicit validation step (step 5) and an Output Expectations checklist; score 4 not 5 because there is no validate→fix→retry feedback loop, though the skill is design-oriented rather than destructive/batch.

4 / 5

Progressive Disclosure

Well-structured overview with one-level-deep references that are clearly signaled and described; all four referenced files (representables.md, window-panels.md, responder-menus.md, drag-drop-pasteboard.md) exist, and detail is appropriately split out of the body.

5 / 5

Total

18

/

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 concise, third-person description that explicitly covers both what the skill does and when to use it, with concrete domain-specific triggers and low conflict risk. Minor keyword-coverage gaps keep specificity and trigger_term_quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Names the domain ("Bridge macOS SwiftUI into AppKit narrowly") plus several concrete actions ("implementing representables, reaching NSWindow or panels, handling menus, or using the responder chain"); falls at score 4 rather than 5 because coverage is good but not exhaustive of the full interop surface.

4 / 5

Completeness

Explicitly answers both what ("Bridge macOS SwiftUI into AppKit narrowly") and when ("Use when implementing representables, reaching NSWindow or panels, handling menus, or using the responder chain") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong domain keywords a macOS developer would naturally say (representables, NSWindow, panels, menus, responder chain); score 4 not 5 because some natural synonyms/variants (NSViewControllerRepresentable, coordinator, pasteboard, first responder) are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche (SwiftUI→AppKit interop) with distinct, specific triggers and minimal overlap risk with sibling SwiftUI skills.

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.

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.