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.

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.

The body is a well-organized, token-efficient overview that gives concrete decision guidance, a sequenced workflow with a validation checkpoint, and properly signals one-level-deep reference files. It avoids concept padding and monolithic structure.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: no padding about what SwiftUI or AppKit are, just tight bullets and decision rules where every line earns its place.

3 / 3

Actionability

Although it is instruction-only with no code, the per-bridge-type decision rules and ownership boundary guidance are concrete and actionable, which the rubric's instruction-only carve-out rewards rather than penalizes.

3 / 3

Workflow Clarity

A clear five-step sequence (name gap, pick boundary, keep ownership, expose interface, validate lifecycle) with an explicit validation checkpoint in step 5 (SwiftUI may recreate representables; coordinators are glue, not architecture).

3 / 3

Progressive Disclosure

A concise overview with four clearly-signaled one-level-deep references, each annotated with its scope and verified to be real files in ./references/, matching the well-structured reference example.

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.

The description is concise, third-person, and clearly states both the capability and explicit use-when triggers with concrete domain terms. It carves out a distinct niche with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'implementing representables', 'reaching NSWindow or panels', 'handling menus', 'using the responder chain' — matching the anchor for listing several specific concrete actions, not just naming a domain.

3 / 3

Completeness

Explicitly answers both what ('Bridge macOS SwiftUI into AppKit narrowly') and when via a 'Use when...' clause with concrete triggers, rather than leaving the trigger implied.

3 / 3

Trigger Term Quality

Uses natural domain terms a macOS developer would actually say ('representables', 'NSWindow', 'panels', 'menus', 'responder chain'); these are precisely the trigger words that locate this niche, not generic jargon.

3 / 3

Distinctiveness Conflict Risk

The SwiftUI↔AppKit interop niche is tight and clearly distinct from a general macOS or SwiftUI skill; 'narrowly' plus specific triggers (responder chain, NSWindow) make it unlikely to fire for the wrong 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
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.