[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6996SBDQB83B9ACW5SPSM78":3,"skill-same:01M6996SBDQB83B9ACW5SPSM78":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M6996SBDQB83B9ACW5SPSM78","fuzzing-rust-expert",null,"Use this skill to fuzz open source Rust software projects.","google\u002Foss-fuzz","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M6996E0MR95P8E5T4FN1KBHN",12952,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Foss-fuzz\u002Fblob\u002Fmaster\u002Finfra\u002Fexperimental\u002Fagent-skills\u002Ffuzzing-rust-expert\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"rust","fuzzing","fuzzing rust expert","expert","rust expert","open source","open","projects","use","software","source","2026-11-10 10:12:30",false,"---\nname: fuzzing-rust-expert\ndescription:\n  Use this skill to fuzz open source Rust software projects.\n---\n\n# Fuzzing Rust expert\n\nThis skill provides the agent with the knowledge and tools to write, build, and\nvalidate fuzz targets for Rust projects integrated into OSS-Fuzz. Rust fuzzing\nuses cargo-fuzz with the `libfuzzer_sys` crate, which drives libFuzzer.\n\n## Fundamental Concepts\n\n### OSS-Fuzz base image\n\nRust projects must use the Rust base builder image:\n\n```dockerfile\nFROM gcr.io\u002Foss-fuzz-base\u002Fbase-builder-rust\n```\n\nSet `language: rust` in `project.yaml`.\n\n### Harness structure\n\nRust fuzz targets live in `fuzz\u002Ffuzz_targets\u002F\u003Cname>.rs` within the crate being\nfuzzed. The minimal harness using raw bytes:\n\n```rust\n#![no_main]\nuse libfuzzer_sys::fuzz_target;\n\nfuzz_target!(|data: &[u8]| {\n    \u002F\u002F Call into the target. The fuzzer will mutate `data` on every iteration.\n    let _ = my_crate::parse(data);\n});\n```\n\nFor structured fuzzing using the `arbitrary` crate (preferred when the target\nexpects typed input):\n\n```rust\n#![no_main]\nuse libfuzzer_sys::fuzz_target;\nuse arbitrary::Arbitrary;\n\n#[derive(Debug, Arbitrary)]\nstruct MyInput {\n    header: u8,\n    payload: Vec\u003Cu8>,\n    flags: u32,\n}\n\nfuzz_target!(|input: MyInput| {\n    let _ = my_crate::process(input.header, &input.payload, input.flags);\n});\n```\n\nThe `Cargo.toml` for the fuzz directory must declare dependencies:\n\n```toml\n# fuzz\u002FCargo.toml\n[package]\nname = \"my-crate-fuzz\"\nversion = \"0.0.0\"\nedition = \"2021\"\npublish = false\n\n[dependencies]\nlibfuzzer-sys = \"0.4\"\narbitrary = { version = \"1\", features = [\"derive\"] }   # only if using structured fuzzing\n\n[dependencies.my-crate]\npath = \"..\"\n\n[[bin]]\nname = \"fuzz_target_name\"\npath = \"fuzz_targets\u002Ffuzz_target_name.rs\"\ntest = false\ndoc = false\n```\n\n### Building in OSS-Fuzz\n\n`build.sh` uses `cargo fuzz build` and then copies binaries to `$OUT`:\n\n```bash\n# build.sh\ncd $SRC\u002F\u003Ccrate-dir>\ncargo fuzz build -O   # -O enables release optimisations; important for performance\n\nFUZZ_TARGET_OUTPUT_DIR=$SRC\u002F\u003Ccrate-dir>\u002Ftarget\u002Fx86_64-unknown-linux-gnu\u002Frelease\nfor f in fuzz\u002Ffuzz_targets\u002F*.rs; do\n    name=$(basename \"${f%.*}\")\n    cp \"$FUZZ_TARGET_OUTPUT_DIR\u002F$name\" \"$OUT\u002F\"\ndone\n```\n\nIf the project requires a nightly toolchain, set it in the Dockerfile:\n\n```dockerfile\nENV RUSTUP_TOOLCHAIN=nightly\n```\n\nOr pin to a specific nightly for reproducibility:\n\n```dockerfile\nENV RUSTUP_TOOLCHAIN=nightly-2025-07-03\n```\n\n### Seed corpus and dictionaries\n\n- Place seed files in `fuzz\u002Fcorpus\u002F\u003Ctarget_name>\u002F` within the repo; they are\n  automatically picked up by cargo-fuzz and can be zipped for OSS-Fuzz.\n- To ship a corpus with OSS-Fuzz copy a zip to `$OUT\u002F\u003Ctarget_name>_seed_corpus.zip`.\n- Dictionaries go to `$OUT\u002F\u003Ctarget_name>.dict`.\n- For targets that parse a structured format, generating seeds with a script\n  beats hand-picking a few files — random mutation rarely passes the parser's\n  early checks (note: cargo-fuzz's `arbitrary` is the better route when the\n  target takes typed data rather than a byte format). See the [structured seed\n  generation reference](..\u002Foss-fuzz-engineer\u002Freferences\u002Fstructured_seed_generation.md).\n\n## Characteristics of good Rust fuzzing harnesses\n\n1. **Targets attack surface**: parsers, deserializers, protocol implementations,\n   unsafe blocks, and any API that processes untrusted bytes.\n2. **Uses structured fuzzing** (`arbitrary`) when the target expects typed data\n   rather than raw bytes — this dramatically improves coverage.\n3. **Handles expected errors**: `Result` and `Option` should be let-bound and\n   ignored (`let _ = ...`). Only actual panics are findings.\n4. **Avoids panicking on every input**: do not use `.unwrap()` or `.expect()`\n   on fallible operations driven by fuzz input — these create false positives.\n5. **Avoids non-determinism**: no `rand`, no system time, no thread spawning\n   inside the fuzz callback.\n6. **Is fast**: avoid I\u002FO, heavy allocations, or expensive setup inside the\n   callback; do those outside the `fuzz_target!` macro if needed with\n   `LazyLock` \u002F `OnceLock`.\n7. **Considers `unsafe` code**: if the crate has `unsafe` blocks, write\n   harnesses that exercise those paths — this is where memory bugs can still\n   occur in Rust.\n8. **Builds in release mode** (`-O`): fuzzing in debug mode is much slower.\n\n## What Rust fuzzing finds\n\nRust's ownership model prevents most memory-corruption bugs, but fuzzing still\nfinds:\n\n- **Panics**: `unwrap`\u002F`expect` on `None`\u002F`Err`, index out of bounds,\n  arithmetic overflow in debug mode, explicit `panic!` calls.\n- **`unsafe` bugs**: use-after-free, out-of-bounds reads\u002Fwrites, undefined\n  behaviour in `unsafe` blocks — these are real memory bugs.\n- **Logic errors**: incorrect parsing, data corruption, wrong output.\n- **Hangs**: infinite loops triggered by crafted input.\n- **Stack overflows**: deep recursion on adversarial input.\n\n## Operational guidelines\n\n- Always validate with:\n  ```\n  python3 infra\u002Fhelper.py build_fuzzers \u003Cproject>\n  python3 infra\u002Fhelper.py check_build \u003Cproject>\n  python3 infra\u002Fhelper.py run_fuzzer \u003Cproject> \u003Cfuzzer_name> -- -max_total_time=30\n  ```\n- An instant crash usually means a `panic!` on every input — check for\n  `.unwrap()` calls on fuzz-driven paths and replace with `if let` or `?`.\n- Run `cargo build` and `cargo test` inside the crate before adding the fuzz\n  harness to catch pre-existing compilation errors.\n- When iterating locally clone the upstream repo and switch the Dockerfile from\n  `RUN git clone` to `COPY` to avoid network round-trips.\n- If the crate uses `no_std`, use `libfuzzer-sys`'s `no_std` feature and ensure\n  the harness does not rely on `std`.\n- Document why each entry point was chosen and what class of bugs it may find.\n","# Fuzzing Rust expert\n\nThis skill provides the agent with the knowledge and tools to write, build, and\nvalidate fuzz targets for Rust projects integrated into OSS-Fuzz. Rust fuzzing\nuses cargo-fuzz with the `libfuzzer_sys` crate, which drives libFuzzer.\n\n## Fundamental Concepts\n\n### OSS-Fuzz base image\n\nRust projects must use the Rust base builder image:\n\n```dockerfile\nFROM gcr.io\u002Foss-fuzz-base\u002Fbase-builder-rust\n```\n\nSet `language: rust` in `project.yaml`.\n\n### Harness structure\n\nRust fuzz targets live in `fuzz\u002Ffuzz_targets\u002F\u003Cname>.rs` within the crate being\nfuzzed. The minimal harness using raw bytes:\n\n```rust\n#![no_main]\nuse libfuzzer_sys::fuzz_target;\n\nfuzz_target!(|data: &[u8]| {\n    \u002F\u002F Call into the target. The fuzzer will mutate `data` on every iteration.\n    let _ = my_crate::parse(data);\n});\n```\n\nFor structured fuzzing using the `arbitrary` crate (preferred when the target\nexpects typed input):\n\n```rust\n#![no_main]\nuse libfuzzer_sys::fuzz_target;\nuse arbitrary::Arbitrary;\n\n#[derive(Debug, Arbitrary)]\nstruct MyInput {\n    header: u8,\n    payload: Vec\u003Cu8>,\n    flags: u32,\n}\n\nfuzz_target!(|input: MyInput| {\n    let _ = my_crate::process(input.header, &input.payload, input.flags);\n});\n```\n\nThe `Cargo.toml` for the fuzz directory must declare dependencies:\n\n```toml\n# fuzz\u002FCargo.toml\n[package]\nname = \"my-crate-fuzz\"\nversion = \"0.0.0\"\nedition = \"2021\"\npublish = false\n\n[dependencies]\nlibfuzzer-sys = \"0.4\"\narbitrary = { version = \"1\", features = [\"derive\"] }   # only if using structured fuzzing\n\n[dependencies.my-crate]\npath = \"..\"\n\n[[bin]]\nname = \"fuzz_target_name\"\npath = \"fuzz_targets\u002Ffuzz_target_name.rs\"\ntest = false\ndoc = false\n```\n\n### Building in OSS-Fuzz\n\n`build.sh` uses `cargo fuzz build` and then copies binaries to `$OUT`:\n\n```bash\n# build.sh\ncd $SRC\u002F\u003Ccrate-dir>\ncargo fuzz build -O   # -O enables release optimisations; important for performance\n\nFUZZ_TARGET_OUTPUT_DIR=$SRC\u002F\u003Ccrate-dir>\u002Ftarget\u002Fx86_64-unknown-linux-gnu\u002Frelease\nfor f in fuzz\u002Ffuzz_targets\u002F*.rs; do\n    name=$(basename \"${f%.*}\")\n    cp \"$FUZZ_TARGET_OUTPUT_DIR\u002F$name\" \"$OUT\u002F\"\ndone\n```\n\nIf the project requires a nightly toolchain, set it in the Dockerfile:\n\n```dockerfile\nENV RUSTUP_TOOLCHAIN=nightly\n```\n\nOr pin to a specific nightly for reproducibility:\n\n```dockerfile\nENV RUSTUP_TOOLCHAIN=nightly-2025-07-03\n```\n\n### Seed corpus and dictionaries\n\n- Place seed files in `fuzz\u002Fcorpus\u002F\u003Ctarget_name>\u002F` within the repo; they are\n  automatically picked up by cargo-fuzz and can be zipped for OSS-Fuzz.\n- To ship a corpus with OSS-Fuzz copy a zip to `$OUT\u002F\u003Ctarget_name>_seed_corpus.zip`.\n- Dictionaries go to `$OUT\u002F\u003Ctarget_name>.dict`.\n- For targets that parse a structured format, generating seeds with a script\n  beats hand-picking a few files — random mutation rarely passes the parser's\n  early checks (note: cargo-fuzz's `arbitrary` is the better route when the\n  target takes typed data rather than a byte format). See the [structured seed\n  generation reference](..\u002Foss-fuzz-engineer\u002Freferences\u002Fstructured_seed_generation.md).\n\n## Characteristics of good Rust fuzzing harnesses\n\n1. **Targets attack surface**: parsers, deserializers, protocol implementations,\n   unsafe blocks, and any API that processes untrusted bytes.\n2. **Uses structured fuzzing** (`arbitrary`) when the target expects typed data\n   rather than raw bytes — this dramatically improves coverage.\n3. **Handles expected errors**: `Result` and `Option` should be let-bound and\n   ignored (`let _ = ...`). Only actual panics are findings.\n4. **Avoids panicking on every input**: do not use `.unwrap()` or `.expect()`\n   on fallible operations driven by fuzz input — these create false positives.\n5. **Avoids non-determinism**: no `rand`, no system time, no thread spawning\n   inside the fuzz callback.\n6. **Is fast**: avoid I\u002FO, heavy allocations, or expensive setup inside the\n   callback; do those outside the `fuzz_target!` macro if needed with\n   `LazyLock` \u002F `OnceLock`.\n7. **Considers `unsafe` code**: if the crate has `unsafe` blocks, write\n   harnesses that exercise those paths — this is where memory bugs can still\n   occur in Rust.\n8. **Builds in release mode** (`-O`): fuzzing in debug mode is much slower.\n\n## What Rust fuzzing finds\n\nRust's ownership model prevents most memory-corruption bugs, but fuzzing still\nfinds:\n\n- **Panics**: `unwrap`\u002F`expect` on `None`\u002F`Err`, index out of bounds,\n  arithmetic overflow in debug mode, explicit `panic!` calls.\n- **`unsafe` bugs**: use-after-free, out-of-bounds reads\u002Fwrites, undefined\n  behaviour in `unsafe` blocks — these are real memory bugs.\n- **Logic errors**: incorrect parsing, data corruption, wrong output.\n- **Hangs**: infinite loops triggered by crafted input.\n- **Stack overflows**: deep recursion on adversarial input.\n\n## Operational guidelines\n\n- Always validate with:\n  ```\n  python3 infra\u002Fhelper.py build_fuzzers \u003Cproject>\n  python3 infra\u002Fhelper.py check_build \u003Cproject>\n  python3 infra\u002Fhelper.py run_fuzzer \u003Cproject> \u003Cfuzzer_name> -- -max_total_time=30\n  ```\n- An instant crash usually means a `panic!` on every input — check for\n  `.unwrap()` calls on fuzz-driven paths and replace with `if let` or `?`.\n- Run `cargo build` and `cargo test` inside the crate before adding the fuzz\n  harness to catch pre-existing compilation errors.\n- When iterating locally clone the upstream repo and switch the Dockerfile from\n  `RUN git clone` to `COPY` to avoid network round-trips.\n- If the crate uses `no_std`, use `libfuzzer-sys`'s `no_std` feature and ensure\n  the harness does not rely on `std`.\n- Document why each entry point was chosen and what class of bugs it may find.\n",{"name":5,"description":7},"master","e83ae3515d386e253ed7d86395d8cbdebd3e0917","infra\u002Fexperimental\u002Fagent-skills\u002Ffuzzing-rust-expert",2997,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Foss-fuzz","https:\u002F\u002Fgoogle.github.io\u002Foss-fuzz","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-14 23:27:56",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add google\u002Foss-fuzz --skill fuzzing-rust-expert",{"tool":51,"command":52},"bunx","bunx skills add google\u002Foss-fuzz --skill fuzzing-rust-expert",{"tool":54,"command":55},"pnpm","pnpm dlx skills add google\u002Foss-fuzz --skill fuzzing-rust-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Foss-fuzz\u002Fblob\u002Fmaster\u002Finfra\u002Fexperimental\u002Fagent-skills\u002Ffuzzing-rust-expert\u002FSKILL.md",true,[59],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"agents\u002Fopenai.yaml","REFERENCE","参考文档",146,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Fto-tickets\u002Ffef444bd40ea6849\u002Fto-tickets\u002Fagents\u002Fopenai.yaml",[66,79,91,102,114],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":30},"01M6996V9MBNRZ17CW93P54CQP","oss-fuzz-engineer","Use this skill to interact with the OSS-Fuzz infrastructure.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Foss-fuzz\u002Fblob\u002Fmaster\u002Finfra\u002Fexperimental\u002Fagent-skills\u002Foss-fuzz-engineer\u002FSKILL.md",[],[73,74,75,76,77,27,78],"oss fuzz","oss","oss fuzz engineer","engineer","with","infrastructure",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":30},"01M6996QG8NWMDC83GTK885TDD","fuzzing-python-expert","Use this skill to fuzz open source Python software projects using Atheris.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Foss-fuzz\u002Fblob\u002Fmaster\u002Finfra\u002Fexperimental\u002Fagent-skills\u002Ffuzzing-python-expert\u002FSKILL.md",[],[86,20,87,88,22,89,24,25,26,27,28,90,29],"python","fuzzing python expert","python expert","fuzzing python","atheris",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":30},"01M6996NKJDXKEJ3TZJZNKXV8M","fuzzing-memory-unsafe-expert","Use this skill to fuzz open source C\u002FC++ software projects.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Foss-fuzz\u002Fblob\u002Fmaster\u002Finfra\u002Fexperimental\u002Fagent-skills\u002Ffuzzing-memory-unsafe-expert\u002FSKILL.md",[],[98,22,99,20,100,29,24,25,26,27,101,28],"unsafe","fuzzing memory unsafe expert","memory","c++",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":30},"01M6996KFJ5JV7GTDHH4J4ZTJC","fuzzing-jvm-expert","Use this skill to fuzz open source JVM projects (Java, Kotlin, Scala, etc.) using Jazzer.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Foss-fuzz\u002Fblob\u002Fmaster\u002Finfra\u002Fexperimental\u002Fagent-skills\u002Ffuzzing-jvm-expert\u002FSKILL.md",[],[109,22,110,20,26,111,112,24,25,113,27,29],"jvm","fuzzing jvm expert","scala","java","kotlin",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":30},"01M6996H8NDKT37EGSJ31W9YRT","fuzzing-go-expert","Use this skill to fuzz open source Go software projects.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Foss-fuzz\u002Fblob\u002Fmaster\u002Finfra\u002Fexperimental\u002Fagent-skills\u002Ffuzzing-go-expert\u002FSKILL.md",[],[20,121,122,123,22,24,25,26,27,28,29],"fuzzing go expert","go","go expert"]