CtrlK
BlogDocsLog inGet started
Tessl Logo

appkit-interop

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

70

Quality

85%

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 well-organized instruction-only skill body: efficient, actionable decision guidance with a clear workflow and exemplary one-level-deep reference structure. Main room for improvement is making the lifecycle validation step more concretely checkable and trimming minor overlap with the description.

Suggestions

Make the validation step concretely checkable, e.g. a short checklist for verifying coordinator wiring or lifecycle recreation on each reference pattern.

Remove the Quick Start sentence that restates the description to save tokens.

Inline a minimal coordinator skeleton pointer earlier (e.g. one line linking step 5 to references/representables.md) so the ownership rules have an immediate concrete referent.

DimensionReasoningScore

Conciseness

The body is lean bullet-based guidance with no concept padding (it never explains what SwiftUI or AppKit is), though the Quick Start section ('Use this skill when SwiftUI is close but not quite enough') partially restates the frontmatter description. Not 5 because a few lines could still be trimmed; not 3 because there is no unnecessary explanation.

4 / 5

Actionability

Concrete decision rules name exact types ('Use `NSViewRepresentable` when...', 'Use `NSViewControllerRepresentable` when...') and the references hold executable skeletons, making the guidance actionable despite no inline code. Not 5 because some steps like 'Keep ownership explicit' and 'Expose a narrow interface' remain advisory rather than concrete.

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 assumptions) with an explicit validation step and anti-pattern guardrails. Not 5 because the 'Validate lifecycle assumptions' step is conceptual rather than a runnable or checkable checkpoint.

4 / 5

Progressive Disclosure

The SKILL.md is a concise overview with four well-signaled, one-line-annotated references (representables.md, window-panels.md, responder-menus.md, drag-drop-pasteboard.md) that all exist, are one level deep, and contain self-contained content. Not 4 because the split and navigation are exemplary with no organization gaps.

5 / 5

Total

17

/

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.

A tight, well-structured description that states the what and when explicitly with concrete AppKit trigger terms in third person. The only minor gap is a few missing natural synonyms that users might phrase differently.

Suggestions

Add one or two common user phrasings such as 'NSViewRepresentable' or 'menu validation' to the Use-when clause for broader trigger coverage.

DimensionReasoningScore

Specificity

The description lists multiple concrete named actions — 'implementing representables, reaching NSWindow or panels, handling menus, or using the responder chain' — which comprehensively covers the skill's domain in third-person voice. Not 4 because coverage of the bridging capability is complete rather than having minor gaps.

5 / 5

Completeness

It 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. Not 4 because the 'when' clause is fully explicit with enumerated triggers, not merely present.

5 / 5

Trigger Term Quality

Natural macOS-development terms like 'representables', 'NSWindow', 'panels', 'menus', and 'responder chain' match what users would actually say when needing this skill. Not 5 because common variations such as 'NSViewRepresentable', 'menu validation', or 'SwiftUI to AppKit' are absent.

4 / 5

Distinctiveness Conflict Risk

The AppKit-specific triggers (NSWindow, responder chain, representables) establish a clear niche with minimal overlap risk against general SwiftUI skills. Not 4 because the triggers are technical and unambiguous enough that mis-triggering for the wrong skill is unlikely.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.