CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

76

Quality

96%

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

93%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.

An exemplary discovery stub: it defers detail to CLI-loaded sub-skills with explicit load-order guidance, provides copy-paste-ready commands for discovery and scaffolding, and stays lean. The only trims available are in the slightly dense opening paragraph, and an explicit install-verification step would round out the workflow.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, but the opening paragraph ('Zig is how the toolkit itself works and is a first-class, explicitly chosen app-core alternative...; it is not the default inferred from the SDK's implementation') partially restates the frontmatter description and could be tightened. Not 3: there is no padding or explanation of concepts Claude already knows.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout — 'native skills list', 'native skills get core', 'npm install -g @native-sdk/cli', 'native init my_app', 'native dev' — plus concrete file layout ('app.json, src/app.native, and src/core.ts'). Specific commands cover the common cases.

5 / 5

Workflow Clarity

A clear sequence is present: discover ('Before implementing or explaining Native SDK app work, use the installed CLI...'), load the right sub-skills ('load **both** native-ui ... and ts-core ... before implementing'), then scaffold — with a checkpoint ('Inspect the tree before editing an existing app and preserve the core language'). Not 5: no explicit validation step (e.g., verifying the CLI is installed); not 3: checkpoints and load-order decision guidance are explicit and the skill involves no destructive or batch operations.

4 / 5

Progressive Disclosure

The SKILL.md is a concise, well-organized overview with clearly signaled one-level-deep references ('Use native skills get core --full when work reaches lower-level runtime wiring, WebViews, bridge/security...'), and each sub-skill's purpose is stated so navigation is easy. At under 50 lines with no bundle files, the simple-skill organization applies cleanly.

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.

A strong description: explicit what-and-when structure, extensive concrete action coverage, natural trigger terms including file names and extensions, and a distinct niche. The only nit is mild marketing flavor ('the complete toolkit'), which does not obscure any capability claims.

DimensionReasoningScore

Specificity

The description lists many 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, or automate' — with comprehensive coverage of the SDK's surface, matching the top anchor rather than the 'minor gaps' of a 4.

5 / 5

Completeness

It explicitly answers what ('Discovery skill for the Native SDK, the 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 a Native SDK app...'), with a concrete, well-formed trigger clause.

5 / 5

Trigger Term Quality

It covers natural user phrasing ('build a Native SDK app', 'scaffold an app', 'package an app') plus concrete file extensions and names ('.native', 'app.json', 'app.zon'), giving comprehensive natural-term coverage; no common variation is obviously missing, so it exceeds the 4 anchor.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche with product-specific triggers ('Native SDK', 'app.json', 'legacy app.zon', 'bridge commands', '.native') that no generic skill would claim, minimizing conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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
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.