CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fuzzing-harness

Write and run a fuzzer, fuzz harnesses and property-based tests for the code that handles untrusted bytes (file and packet parsers in C, C++, Rust, Go, Python or JS, decoders, serializers, deserializers, token and header parsing, protocol state machines), then minimize, dedupe and triage the crashes into verified findings with regression tests. Covers libFuzzer, cargo-fuzz, Go native fuzzing, Atheris, Jazzer.js and Jazzer, Hypothesis, fast-check and proptest, seed corpora and dictionaries, sanitizer builds, and CI fuzzing with ClusterFuzzLite or OSS-Fuzz. Use when the user mentions 'fuzzing,' 'fuzz harness,' 'fuzz target,' 'libFuzzer,' 'cargo fuzz,' 'go test -fuzz,' 'Atheris,' 'Jazzer,' 'property-based testing,' 'Hypothesis property test,' 'fast-check,' 'proptest,' 'seed corpus,' 'fuzzing dictionary,' 'AddressSanitizer report,' 'fuzzer crash files,' 'minimize a crash input,' 'ClusterFuzzLite,' 'OSS-Fuzz,' or wants to fuzz their parser.

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

92%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 strong, expert-level skill body: an explicitly sequenced eight-step workflow with validation and feedback loops at every risky stage, copy-paste-ready commands and flags, and clean one-level-deep offloading to nine real reference files. Its only weakness is length — the cross-reference list and five worked examples could be tightened without losing substance.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no primers on what fuzzing or sanitizers are, and nearly every line is non-obvious domain judgment ("Dedupe by crash type plus the top three frames in project code", "Forty crash files are often two bugs", the Apple-clang/nightly/Windows toolchain gotchas). A few sections could be trimmed: the 10-skill cross-reference paragraph, the five worked examples (~40 lines where two would carry the patterns), and parts of "Not for" that repeat the Boundaries section; this places it at efficient-with-minor-trimmings rather than the every-token-earns-its-place top anchor.

4 / 5

Actionability

Guidance is copy-paste ready throughout: executable rg/grep inventory commands with a portable fallback, exact sanitizer and limit flags ("-fsanitize=fuzzer,address,undefined", "-rss_limit_mb=2048", "-max_total_time=600"), a per-language engine table, a fully specified ext-keys schema, and concrete validation commands ("node references/validate-findings.mjs findings.json"). The common cases are covered with specifics down to file paths and output directories; no pseudocode stands in for executable content.

5 / 5

Workflow Clarity

The eight-step workflow (Inventory → rank → harness → seeds → run → triage → verify → regression/CI) is explicitly sequenced with validation checkpoints and feedback loops throughout: reproduce each crash before minimizing, "Flaky: check for leaked state or threads before going on", harness-bug detection ("A crash caused by the harness breaking the contract is a harness bug: fix it and rerun"), the refutation pass before any verdict, "Write findings.json first and validate it", and "Verify the fix" in the report template. Because this batch/run-heavy workflow has explicit validation at every stage, the destructive/batch cap at 3 does not apply.

5 / 5

Progressive Disclosure

SKILL.md is an overview that pushes per-language templates, build commands, the triage class table, severity calibration, verification procedure, findings format, and CI setup into nine reference files, each present in references/ and each introduced with a clear signal of what it contains (e.g. "Per-language templates, structured-input helpers and build commands are in [references/harness-templates.md]"). All referenced paths resolve to real bundle files exactly one level deep with no nested reference chains, matching the clear-overview anchor.

5 / 5

Total

19

/

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.

An exemplary description: it states a concrete multi-stage capability pipeline, names the exact target shapes and engines, and closes with an explicit, exhaustive trigger list including tool names, commands, and colloquial paraphrases. Both the what and when are fully explicit, and every term is natural user phrasing rather than jargon.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Write and run a fuzzer, fuzz harnesses and property-based tests", "minimize, dedupe and triage the crashes into verified findings with regression tests" — and comprehensively scopes the target domain ("file and packet parsers in C, C++, Rust, Go, Python or JS, decoders, serializers, deserializers, token and header parsing, protocol state machines") plus the full toolchain. Coverage of what the skill does is comprehensive with no padding, matching the top anchor; a 4 would require minor gaps in the action list, which are not present.

5 / 5

Completeness

It explicitly answers both questions: the "what" is the full pipeline from harness authoring through crash triage to regression tests, and the "when" is a dedicated "Use when the user mentions" clause with concrete trigger phrases. This matches the anchor example's structure exactly; not a 4 because the when-clause is fully explicit rather than vague or under-specified.

5 / 5

Trigger Term Quality

The "Use when the user mentions" clause enumerates natural trigger phrases users would actually say: 'fuzzing,' 'fuzz harness,' 'fuzz target,' 'libFuzzer,' 'cargo fuzz,' 'go test -fuzz,' 'Atheris,' 'Jazzer,' 'property-based testing,' 'Hypothesis property test,' 'fast-check,' 'proptest,' 'seed corpus,' 'fuzzing dictionary,' 'AddressSanitizer report,' 'fuzzer crash files,' 'minimize a crash input,' 'ClusterFuzzLite,' 'OSS-Fuzz,' plus the plain-language synonym "or wants to fuzz their parser." Tool names, command-line invocations, and informal paraphrases together give comprehensive natural-term coverage; a 4 would mean a few natural terms are missing, and none are.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — fuzzing and property-based testing of untrusted-input handlers — and the triggers (libFuzzer, cargo fuzz, Atheris, Jazzer, ClusterFuzzLite, seed corpus) are distinct tool-specific terms unlikely to fire for a wrong skill. "property-based testing" and "proptest" have slight overlap with general testing skills, but the "code that handles untrusted bytes" scoping keeps conflict risk minimal, fitting the clear-niche/minimal-conflict anchor rather than the minor-overlap anchor below it.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

briiirussell/cybersecurity-skills

Path

skills/fuzzing-harness/SKILL.md

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.