CtrlK
BlogDocsLog inGet started
Tessl Logo

appkit-interop

Decide when and how to bridge a macOS app from SwiftUI into AppKit. Use when implementing NSViewRepresentable or NSViewControllerRepresentable, accessing NSWindow or the responder chain, presenting panels, customizing menus, or handling desktop behaviors that SwiftUI does not model cleanly.

75

Quality

93%

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

The canonical home for this skill is appkit-interop in openai/plugins

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.

The body is concise, well-structured, and uses progressive disclosure effectively with real, scope-labeled reference files. Actionability and workflow clarity are strong but stop just short of full marks due to the absence of executable examples and a hard validation feedback loop.

Suggestions

Add one short executable Swift snippet showing a minimal NSViewRepresentable bridge to lift actionability to fully copy-paste-ready guidance.

Turn the 'Validate lifecycle assumptions' step into an explicit validate→fix→retry feedback loop with a concrete check (e.g., confirm the representable survives view recreation) to strengthen workflow_clarity.

DimensionReasoningScore

Conciseness

Lean and efficient throughout; assumes Claude's competence about SwiftUI and AppKit without explaining basics, and every line earns its place.

5 / 5

Actionability

Provides concrete, specific decision guidance (which bridge type for which scenario, ownership rules, narrow-interface steps) but contains no executable code examples, leaving a minor gap for an instruction-only skill.

4 / 5

Workflow Clarity

A clear five-step sequenced workflow with guardrails and a lifecycle-validation step, though the validation is advisory rather than a hard validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references; all four referenced files exist and are described by scope, and the body is appropriately split as an overview.

5 / 5

Total

18

/

20

Passed

Description

100%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 distinctive, with concrete trigger terms and a clear what/when structure. It uses appropriate third-person voice and avoids fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—implementing NSViewRepresentable/NSViewControllerRepresentable, accessing NSWindow and the responder chain, presenting panels, customizing menus—covering the AppKit-interop domain comprehensively.

5 / 5

Completeness

Explicitly answers both 'what' ('Decide when and how to bridge a macOS app from SwiftUI into AppKit') and 'when' with a concrete 'Use when...' clause enumerating specific triggers.

5 / 5

Trigger Term Quality

Includes natural, domain-appropriate trigger terms a user would say (NSViewRepresentable, NSWindow, responder chain, panels, menus) plus synonyms like 'bridge a macOS app from SwiftUI into AppKit'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (SwiftUI↔AppKit bridging) with distinct, specialized triggers and minimal overlap with other skills.

5 / 5

Total

20

/

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.