native-sdk

Discovery skill for the Native SDK, the complete toolkit for building native desktop applications. Apps are authored in TypeScript + declarative Native markup (.native) by default and compiled to native code with no JS runtime in the binary; Zig cores are an explicit alternative, and WebViews are the optional web-content path. Use when the user asks what the Native SDK is, how to build a Native SDK app, author native UI, scaffold an app, configure app.json or legacy app.zon, add bridge commands, embed web content, package an app, test a running app, or automate a Native SDK app.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%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 content is a well-structured discovery stub that routes to deeper skills via concrete commands, with excellent actionability and clean progressive disclosure. Its main weakness is mild over-explanation of SDK architecture/rationale that Claude could infer, and the absence of explicit verification steps.

Suggestions

Trim the architectural rationale in the opening paragraph (e.g., 'Zig is how the toolkit itself works and is a first-class...') to the one routing rule that matters: Zig is non-default and requires --template zig-core.

Add one explicit verification checkpoint after scaffolding, e.g. confirm the generated three-file tree (app.json, src/app.native, src/core.ts) exists before editing.

Collapse the duplicated install snippet — 'npx skills add native-sdk' appears in prose and 'npm install -g @native-sdk/cli' in Quick orientation; state the install path once to avoid token overlap.

Dimension	Reasoning	Score
Conciseness	The body is dense and largely earns its tokens with concrete commands and routing rules, but sentences like the opening paragraph and the Zig/toolkit rationale ('Zig is how the toolkit itself works...') explain background Claude could largely infer.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands ('native skills list', 'native skills get core', 'npm install -g @native-sdk/cli', 'native init my_app', 'native dev') covering the common discovery and scaffold cases.	5 / 5
Workflow Clarity	Clear sequencing for discovery (load core, then both native-ui and ts-core before implementing) with conditional routing by tree contents, but there are no explicit validation/verification checkpoints; since the core operations are non-destructive discovery/scaffold steps, the destructive-cap does not apply.	4 / 5
Progressive Disclosure	The stub is a pure overview that defers all detail to one-level-deep CLI-loaded skills ('native skills get core/native-ui/ts-core/...') with clear, signaled routing by task type; no bundle files are present, and none are needed for this discovery pattern.	5 / 5
	Total	18 / 20 Passed

Description

91%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 comprehensive and explicit, clearly answering both what the skill does and when to use it with a strong list of concrete actions and trigger phrases. Its only mild weakness is density — the long compound sentence bundles so many triggers that a couple of natural synonyms are crowded out.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'author native UI, scaffold an app, configure app.json or legacy app.zon, add bridge commands, embed web content, package an app, test a running app' — with comprehensive coverage of the SDK's surface.	5 / 5
Completeness	Explicitly answers both 'what' ('complete toolkit for building native desktop applications... authored in TypeScript + declarative Native markup') and 'when' ('Use when the user asks what the Native SDK is, how to build...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural trigger coverage ('scaffold an app', 'package an app', 'add bridge commands', 'embed web content') plus file extensions (app.json, app.zon, .native), but the phrasing is installer/SDK-oriented rather than the most common synonyms a casual user would say.	4 / 5
Distinctiveness Conflict Risk	A clear niche ('Native SDK', '.native markup', 'app.json/app.zon', 'Zig cores', 'WebView path') with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: vercel-labs/native
Path: skills/native-sdk/SKILL.md
Commit: 80d1c46

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.