zig

Zig 0.16 idioms for Native SDK code, indexed by compile error. Load when `zig build` fails on std APIs with errors like "struct 'fs' has no member named 'cwd'", "struct 'array_list.Aligned(u8,null)' has no member named 'init'", "struct 'std' has no member named 'io'", "no member named 'GeneralPurposeAllocator'", "no member named 'getEnvMap'", or "invalid format string" - the signature of code written for Zig 0.15 or earlier. Covers main(std.process.Init), std.Io file IO and writers, ArrayList, process spawning, environment, clocks and sleep, sockets, custom formatting, and build.zig module shapes, each as this SDK writes them.

Quality

91%

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

82%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 dense, executable migration reference organized by compile error, with complete code samples and an explicit build-test validation step. It is lean and actionable, with only minor conciseness and structure tightening opportunities.

Suggestions

Break the long UiApp effects paragraph (line 15) into a bulleted list of the fx.* verbs so each capability is scannable instead of buried in a run-on sentence.

Add a short numbered 'how to use this skill' sequence at the top (1. run `zig build` 2. match the error text to a section 3. apply the fix 4. re-run `zig build` and `zig build test`) to make the workflow loop explicit.

Consider moving the per-API 'live reference' file paths into a short consolidated reference table so the inline prose stays focused on the idiom change.

Dimension	Reasoning	Score
Conciseness	Error-indexed structure assumes Zig competence and avoids basic-concept padding, but the run-on UiApp effects paragraph (line 15) packs many API names into one sentence and could be tightened into a list.	4 / 5
Actionability	Every section provides complete, copy-paste-ready Zig code with argument orders called out and live codebase references, covering the common migration cases exhaustively.	5 / 5
Workflow Clarity	Two governing rules plus an explicit validation checkpoint ('run BOTH `zig build` and `zig build test` before calling a change done') give a clear error→fix→rebuild loop, though it is a lookup reference rather than a numbered checklist.	4 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md is well-organized with searchable, error-headed sections and inline codebase pointers, providing easy navigation without needing external splits.	4 / 5
	Total	17 / 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, highly specific description that names concrete capabilities, uses real compiler errors as natural triggers, and explicitly covers both what the skill does and when to load it. It is dense but every clause carries information rather than padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete API areas (main(std.process.Init), std.Io file IO and writers, ArrayList, process spawning, environment, clocks/sleep, sockets, custom formatting, build.zig module shapes), giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both 'what' (Zig 0.16 idioms for Native SDK code, indexed by compile error, with a coverage list) and 'when' ('Load when `zig build` fails on std APIs with errors like...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Triggers are exact compiler error strings users actually see ('struct 'fs' has no member named 'cwd'', 'no member named 'GeneralPurposeAllocator'', 'invalid format string'), plus the natural 'zig build fails on std APIs' framing.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Zig 0.15→0.16 migration for this specific SDK) with distinctive compile-error triggers, making conflict with other skills minimal.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: vercel-labs/native
Path: skill-data/zig/SKILL.md
Commit: 80d1c46

Reviewed: 6 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.