CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/go-native-fuzzing

Author and run Go's native fuzzing (Go 1.18+) - coverage-guided fuzzing built into the standard testing package via FuzzXxx functions. Covers f.Add seed-corpus declaration, f.Fuzz callback signature with typed parameters, testdata/fuzz/{FuzzXxx}/ directory layout for seeds + regression cases, the -fuzz flag for `go test`, and CI integration via short smoke runs. Use for fuzz testing Go libraries - Go's native approach integrates seamlessly with standard `go test` rather than requiring a separate toolchain like AFL++.

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

Overview
Quality
Evals
Security
Files

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 content is lean, highly actionable, and well-structured: executable code throughout, an explicit failure-recovery workflow, and clean self-contained sections. It avoids explaining concepts Claude already knows and delivers copy-paste-ready guidance.

DimensionReasoningScore

Conciseness

The body is code-forward and largely assumes Claude's competence (no explanation of what fuzzing is), with each section earning its place; only minor editorial flair ("unique strength of Go's approach") prevents it from being perfectly lean.

3 / 3

Actionability

Provides fully executable Go fuzz targets, exact `go test -fuzz=...` commands, the literal seed-file format, and a copy-paste CI YAML block—copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

Sequences Authoring → Running → Parsing results → CI with an explicit failure-recovery loop (saved input path, reproduce via `-run=`, commit fixtures) and an always-on CI commit step.

3 / 3

Progressive Disclosure

No bundle files exist, so per the simple-skill note this self-contained, well-sectioned body qualifies; cross-references to sibling skills are clearly signaled and one level deep with no nesting.

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 specific, complete, and well-scoped: it enumerates concrete capabilities, provides an explicit "Use for" trigger, and clearly distinguishes Go's native fuzzing from external toolchains. It is a strong, low-conflict trigger description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—"Author and run Go's native fuzzing", "f.Add seed-corpus declaration", "f.Fuzz callback signature", "the -fuzz flag", "CI integration"—matching the comprehensive-action anchor rather than the partial anchor.

3 / 3

Completeness

Explicitly states what (author/run, FuzzXxx, f.Add, -fuzz flag, CI integration) and when ("Use for fuzz testing Go libraries"), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Covers natural terms a Go user would say—"fuzz testing Go libraries", "Go's native fuzzing", "go test", "seed-corpus", "-fuzz flag"—giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Clear niche (Go-native FuzzXxx functions in the standard testing package) and explicit contrast with AFL++/libFuzzer make it unlikely to trigger 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.

Reviewed

Table of Contents