CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/sanitiser-integration-reference

Pure-reference catalog of compiler sanitisers used with fuzz testing - AddressSanitizer (ASan), UndefinedBehaviorSanitizer (UBSan), MemorySanitizer (MSan), ThreadSanitizer (TSan), and LeakSanitizer (LSan). Explains what each detects, compatibility (can ASan + UBSan combine? - yes; ASan + MSan? - no), build flags, runtime options (ASAN_OPTIONS / UBSAN_OPTIONS env vars), and the typical ~2x slowdown per ASan. Use to pick the right sanitiser per fuzz target, configure the build, and interpret crash reports.

75

Quality

94%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured reference catalog that is highly actionable, clearly sequenced, and properly split across one real reference file. The only weakness is redundancy: the canonical build command and compatibility guidance are repeated across sections.

Suggestions

Show the full `clang -fsanitize=fuzzer,address,undefined` build command once (e.g. in the composition section) and reference it from the summary table and worked example instead of repeating it verbatim.

Replace the prose restatement of the compatibility matrix ('The standard fuzzing pair is ASan + UBSan...') with a one-line pointer to the matrix above, since the table already conveys the same information.

Consider trimming the worked example to only the parts not already covered by the composition section (the report-reading narrative) to reduce token cost.

DimensionReasoningScore

Conciseness

Mostly efficient and dense, but the `clang -g -O1 -fsanitize=fuzzer,address,undefined` build command is repeated three times (summary, composition, worked example) and the compatibility matrix is restated in prose, which could be tightened.

2 / 3

Actionability

Provides fully executable, copy-paste-ready build commands, concrete runtime env-var settings, and a worked ASan report example with real flag values.

3 / 3

Workflow Clarity

The 'How to use' section lays out a clear 7-step sequence with conditional branching (split incompatible sanitisers into separate binaries); this is not a destructive/batch operation requiring validation feedback loops.

3 / 3

Progressive Disclosure

SKILL.md is a clear overview with a single well-signaled one-level reference to references/sanitiser-catalog.md (a real file), with per-sanitiser detail appropriately split out.

3 / 3

Total

11

/

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.

A strong third-person description that pairs a concrete statement of contents with an explicit 'Use to' trigger clause and domain-natural keywords. It clearly communicates both capability and activation conditions with no over-claiming or fluff.

DimensionReasoningScore

Specificity

Names multiple concrete actions and content areas - 'pick the right sanitiser per fuzz target, configure the build, and interpret crash reports' alongside 'build flags, runtime options (ASAN_OPTIONS / UBSAN_OPTIONS env vars)'.

3 / 3

Completeness

Explicitly answers both what ('Pure-reference catalog of compiler sanitisers...') and when via an explicit 'Use to pick the right sanitiser per fuzz target...' trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms a fuzzing user would say - 'fuzz testing', 'sanitisers', 'ASan', 'crash reports', 'build flags' - rather than abstract jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (compiler sanitisers for fuzz testing) with distinct, specific triggers unlikely to fire for unrelated skills.

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