syz-extract-constants

Define and extract kernel constants for syzkaller syzlang descriptions.

4|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/GeneralReasoning/env-skillsbench --skill syz-extract-constants-generalreasoning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: syz-extract-constants
Source: https://github.com/GeneralReasoning/env-skillsbench/tree/main/syzkaller-ppdev-syzlang/environment/skills/syz-extract-constants
Command: npx skills add https://github.com/GeneralReasoning/env-skillsbench --skill syz-extract-constants-generalreasoning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Syzkaller users need accurate definitions of kernel constants (ioctls, flags, etc.) to generate valid fuzzing programs. This Skill defines and extracts those constants for syzlang descriptions, ensuring consistency across descriptions and test cases.

Core Features & Use Cases

  • Manual constants workflow for environments without kernel source.
  • syz-extract workflow when kernel headers are available.
  • Clear guidance for validating constants and integrating them into syzlang descriptions.

Quick Start

Create a manual constants file alongside your syzlang description and run the extraction workflow when kernel headers are unavailable.

Frequently Asked Questions about syz-extract-constants

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract kernel constants for syzkaller syzlang descriptions?

Kernel constants for syzlang are extracted by running the syz-extract workflow when kernel headers are available, or by manually creating a .const file when headers are inaccessible.

What is a .const file in syzkaller and when do I need it?

A .const file in syzkaller is a companion file to syzlang descriptions that defines kernel constants like ioctls and flags, required when kernel headers are unavailable or when using manual constant files.

Can I define syzkaller constants without kernel source headers?

Yes, you can define syzkaller constants without kernel source headers by using the manual constants workflow to create and format a companion .const file alongside your syzlang description.

How do I format and name companion constant files for syzlang?

Companion constant files for syzlang must be formatted as .const files and named alongside their corresponding syzlang descriptions to ensure consistency across test cases and valid fuzzing program generation.

Why do syzkaller descriptions need accurate kernel constants?

Syzkaller needs accurate kernel constants like ioctls and flags to generate valid fuzzing programs, ensuring that test cases interact correctly with kernel interfaces and maintain consistency across descriptions.

What is the best way to validate extracted kernel constants for syzlang?

The best way to validate extracted kernel constants for syzlang is to follow the extraction workflow's guidance for integrating them into syzlang descriptions and verifying consistency across test cases.