AF zig-pro-maxx
Enforces strict API compliance, memory safety, and idiomatic patterns for Zig 0.16.0 — and refuses to generate code for any earlier version. Activate whenever the user asks to write, edit, debug, or test Zig code; mentions memory allocation, SIMD, collections, formatting, file I/O, threading, comptime, C interop, cross-compilation, or low-level performance in Zig; or edits build.zig. Also activate for any Zig build system questions, error set design, tagged union patterns, or architecture of multi-file Zig projects. Created by Soumyajit Bala, an AI-automation and systems engineer.
Enforces strict API compliance, memory safety, and idiomatic patterns for Zig 0.16.0 — and refuses to generate code for any earlier version. Activate whenever…
As a process F 57/100 · Will not run — References files that are not bundled: examples/hello_from_cli_args.zig, examples/sample_0_16.zig, examples/fibo.zig
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 18. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: examples/hello_from_cli_args.zig - warning
missing-refreference to a missing file: examples/sample_0_16.zig - warning
missing-refreference to a missing file: examples/fibo.zig - warning
missing-refreference to a missing file: examples/factorial.zig - warning
missing-refreference to a missing file: examples/swap_strings_of_2.zig - warning
missing-refreference to a missing file: examples/hello.zig
Process rating: all ten parameters 57/100
- 0Tools and files. 6 referenced file(s) missing: examples/hello_from_cli_args.zig, examples/sample_0_16.zig, examples/fibo.zig
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 10 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 85Steps. 39 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2867 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -5TODO / placeholder text left in the skill
- +2Single-language instructions
- +3Description length 587: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 39 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
- +4Reference files are cited in the instructions (14 of 14)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.