[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6996KFJ5JV7GTDHH4J4ZTJC":3,"skill-same:01M6996KFJ5JV7GTDHH4J4ZTJC":66},{"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":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6996KFJ5JV7GTDHH4J4ZTJC","fuzzing-jvm-expert",null,"Use this skill to fuzz open source JVM projects (Java, Kotlin, Scala, etc.) using Jazzer.","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-jvm-expert\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"fuzzing","fuzzing jvm expert","expert","jvm","scala","java","open source","open","projects","kotlin","use","source","2026-11-10 10:12:30",false,"---\nname: fuzzing-jvm-expert\ndescription:\n  Use this skill to fuzz open source JVM projects (Java, Kotlin, Scala, etc.)\n  using Jazzer.\n---\n\n# Fuzzing JVM expert\n\nThis skill provides the agent with the knowledge and tools to write, build, and\nvalidate fuzz targets for JVM-based projects (Java, Kotlin, Scala, Groovy)\nintegrated into OSS-Fuzz. JVM fuzzing uses\n[Jazzer](https:\u002F\u002Fgithub.com\u002FCodeIntelligenceTesting\u002Fjazzer), which wraps\nlibFuzzer and instruments JVM bytecode for coverage guidance.\n\n## Fundamental Concepts\n\n### OSS-Fuzz base image\n\nJVM projects must use the JVM base builder image:\n\n```dockerfile\nFROM gcr.io\u002Foss-fuzz-base\u002Fbase-builder-jvm\n```\n\nSet `language: jvm` in `project.yaml`.\n\n### Harness structure — raw bytes\n\nThe simplest Jazzer harness receives raw bytes via `fuzzerTestOneInput`:\n\n```java\nimport com.code_intelligence.jazzer.api.FuzzedDataProvider;\n\npublic class MyTargetFuzzer {\n    public static void fuzzerTestOneInput(byte[] data) {\n        try {\n            MyLibrary.parse(data);\n        } catch (ExpectedExceptionType e) {\n            \u002F\u002F Ignore expected exceptions; they are not bugs.\n        }\n    }\n}\n```\n\n### Harness structure — typed input via FuzzedDataProvider\n\n`FuzzedDataProvider` splits the raw byte stream into typed values, which is\nessential for targets that require structured input:\n\n```java\nimport com.code_intelligence.jazzer.api.FuzzedDataProvider;\n\npublic class MyTargetFuzzer {\n    public static void fuzzerTestOneInput(FuzzedDataProvider data) {\n        String header    = data.consumeString(64);\n        int    version   = data.consumeInt();\n        byte[] payload   = data.consumeRemainingAsBytes();\n\n        try {\n            MyLibrary.process(header, version, payload);\n        } catch (IllegalArgumentException | IOException e) {\n            \u002F\u002F Expected — not a finding.\n        }\n    }\n}\n```\n\nUseful `FuzzedDataProvider` methods:\n\n| Method | Description |\n|---|---|\n| `consumeBytes(n)` | `byte[]` of length n |\n| `consumeRemainingAsBytes()` | all remaining bytes |\n| `consumeString(maxLen)` | arbitrary String |\n| `consumeAsciiString(maxLen)` | ASCII-only String |\n| `consumeInt()` \u002F `consumeInt(min, max)` | int |\n| `consumeLong()` | long |\n| `consumeBoolean()` | boolean |\n| `consumeDouble()` | double |\n| `pickValue(collection)` | random element |\n\n### One-time setup with `fuzzerInitialize`\n\nIf initialisation is expensive (loading config, creating DB connections, etc.),\nput it in an optional static method that Jazzer calls once before fuzzing:\n\n```java\npublic class MyTargetFuzzer {\n    private static MyClient client;\n\n    public static void fuzzerInitialize() {\n        client = new MyClient(\u002F* static config *\u002F);\n    }\n\n    public static void fuzzerTestOneInput(FuzzedDataProvider data) {\n        client.process(data.consumeRemainingAsBytes());\n    }\n}\n```\n\n### Building in OSS-Fuzz\n\nThe `build.sh` pattern for Maven projects:\n\n```bash\n# Build the project JARs.\n$MVN package -DskipTests -Dmaven.javadoc.skip=true\n\n# Collect JARs needed at runtime.\nALL_JARS=\"mylib-1.0.jar\"\nBUILD_CLASSPATH=$(echo $ALL_JARS | xargs printf -- \"$OUT\u002F%s:\"):$JAZZER_API_PATH\nRUNTIME_CLASSPATH=$(echo $ALL_JARS | xargs printf -- \"\\$this_dir\u002F%s:\"):\\$this_dir\n\nfor fuzzer in $(find $SRC -maxdepth 1 -name '*Fuzzer.java'); do\n    fuzzer_basename=$(basename -s .java \"$fuzzer\")\n    javac -cp $BUILD_CLASSPATH \"$fuzzer\"\n    cp $SRC\u002F$fuzzer_basename.class $OUT\u002F\n\n    # Wrapper script that launches jazzer_driver with the right arguments.\n    echo \"#!\u002Fbin\u002Fbash\nthis_dir=\\$(dirname \\\"\\$0\\\")\nif [[ \\\"\\$@\\\" =~ (^| )-runs=[0-9]+($| ) ]]; then\n  mem_settings='-Xmx1900m:-Xss900k'\nelse\n  mem_settings='-Xmx2048m:-Xss1024k'\nfi\nLD_LIBRARY_PATH=\\\"$JVM_LD_LIBRARY_PATH\\\":\\$this_dir \\\\\n\\$this_dir\u002Fjazzer_driver --agent_path=\\$this_dir\u002Fjazzer_agent_deploy.jar \\\\\n--instrumentation_includes=com.example.** \\\\\n--cp=$RUNTIME_CLASSPATH \\\\\n--target_class=$fuzzer_basename \\\\\n--jvm_args=\\\"\\$mem_settings\\\" \\\\\n\\$@\" > $OUT\u002F$fuzzer_basename\n    chmod u+x $OUT\u002F$fuzzer_basename\ndone\n```\n\nFor Gradle projects replace `$MVN package` with the appropriate Gradle command\nand adjust JAR paths accordingly.\n\n### Seed corpus and dictionaries\n\n- Zip seed files to `$OUT\u002F\u003Cfuzzer_name>_seed_corpus.zip`.\n- Place dictionaries at `$OUT\u002F\u003Cfuzzer_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. See the [structured seed generation\n  reference](..\u002Foss-fuzz-engineer\u002Freferences\u002Fstructured_seed_generation.md).\n\n## Characteristics of good JVM fuzzing harnesses\n\n1. **Targets attack surface**: parsers, deserializers (JSON, XML, Protobuf,\n   custom binary formats), network protocol handlers, template engines, and\n   any API that accepts untrusted bytes or strings.\n2. **Catches expected exceptions**: wrap calls in `try\u002Fcatch` for all\n   documented exception types. Only unexpected exceptions and crashes are\n   findings.\n3. **Uses `FuzzedDataProvider`** for structured input rather than passing raw\n   bytes to methods that expect well-formed data.\n4. **Initialises heavy state in `fuzzerInitialize`**: client connections,\n   parsers with complex configuration, and loaded schemas should be set up once.\n5. **Avoids non-determinism**: no `Math.random()`, no `System.currentTimeMillis()`\n   in the fuzzing path, no thread spawning.\n6. **Sets `--instrumentation_includes`** to the package prefix of the target\n   library in the wrapper script — without this Jazzer cannot guide fuzzing.\n7. **Configures JVM memory appropriately**: use the `mem_settings` pattern\n   shown above to avoid OOM kills during runs vs. crash reproduction.\n8. **Avoids false positives**: `OutOfMemoryError`, `StackOverflowError`, and\n   `NullPointerException` on invalid input are usually expected — decide which\n   are genuine bugs for this project.\n\n## What JVM fuzzing finds\n\n- **Unexpected exceptions**: `NullPointerException`, `ArrayIndexOutOfBoundsException`,\n  `ClassCastException`, `NumberFormatException` on paths that should not throw.\n- **Assertion errors and contract violations**: internal consistency checks\n  that fail on adversarial input.\n- **Hang \u002F infinite loops**: detected by OSS-Fuzz's timeout.\n- **Security bugs**: deserialization gadgets, path traversal via crafted\n  filenames, SSRF via crafted URLs — depends on the library.\n- **Logic bugs**: incorrect output for valid-ish input.\n\nJazzer can also detect:\n- SQL injection (via JDBC hooks)\n- Path traversal (via file API hooks)\n- Command injection (via `Runtime.exec` hooks)\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 missing JAR on the classpath or an\n  uncaught expected exception — check `check_build` output carefully.\n- Build the project outside the fuzzing harness first (`mvn package` or\n  `gradle build`) to ensure the project itself compiles cleanly.\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- Document why each entry point was chosen and what class of bugs it may find.\n","# Fuzzing JVM expert\n\nThis skill provides the agent with the knowledge and tools to write, build, and\nvalidate fuzz targets for JVM-based projects (Java, Kotlin, Scala, Groovy)\nintegrated into OSS-Fuzz. JVM fuzzing uses\n[Jazzer](https:\u002F\u002Fgithub.com\u002FCodeIntelligenceTesting\u002Fjazzer), which wraps\nlibFuzzer and instruments JVM bytecode for coverage guidance.\n\n## Fundamental Concepts\n\n### OSS-Fuzz base image\n\nJVM projects must use the JVM base builder image:\n\n```dockerfile\nFROM gcr.io\u002Foss-fuzz-base\u002Fbase-builder-jvm\n```\n\nSet `language: jvm` in `project.yaml`.\n\n### Harness structure — raw bytes\n\nThe simplest Jazzer harness receives raw bytes via `fuzzerTestOneInput`:\n\n```java\nimport com.code_intelligence.jazzer.api.FuzzedDataProvider;\n\npublic class MyTargetFuzzer {\n    public static void fuzzerTestOneInput(byte[] data) {\n        try {\n            MyLibrary.parse(data);\n        } catch (ExpectedExceptionType e) {\n            \u002F\u002F Ignore expected exceptions; they are not bugs.\n        }\n    }\n}\n```\n\n### Harness structure — typed input via FuzzedDataProvider\n\n`FuzzedDataProvider` splits the raw byte stream into typed values, which is\nessential for targets that require structured input:\n\n```java\nimport com.code_intelligence.jazzer.api.FuzzedDataProvider;\n\npublic class MyTargetFuzzer {\n    public static void fuzzerTestOneInput(FuzzedDataProvider data) {\n        String header    = data.consumeString(64);\n        int    version   = data.consumeInt();\n        byte[] payload   = data.consumeRemainingAsBytes();\n\n        try {\n            MyLibrary.process(header, version, payload);\n        } catch (IllegalArgumentException | IOException e) {\n            \u002F\u002F Expected — not a finding.\n        }\n    }\n}\n```\n\nUseful `FuzzedDataProvider` methods:\n\n| Method | Description |\n|---|---|\n| `consumeBytes(n)` | `byte[]` of length n |\n| `consumeRemainingAsBytes()` | all remaining bytes |\n| `consumeString(maxLen)` | arbitrary String |\n| `consumeAsciiString(maxLen)` | ASCII-only String |\n| `consumeInt()` \u002F `consumeInt(min, max)` | int |\n| `consumeLong()` | long |\n| `consumeBoolean()` | boolean |\n| `consumeDouble()` | double |\n| `pickValue(collection)` | random element |\n\n### One-time setup with `fuzzerInitialize`\n\nIf initialisation is expensive (loading config, creating DB connections, etc.),\nput it in an optional static method that Jazzer calls once before fuzzing:\n\n```java\npublic class MyTargetFuzzer {\n    private static MyClient client;\n\n    public static void fuzzerInitialize() {\n        client = new MyClient(\u002F* static config *\u002F);\n    }\n\n    public static void fuzzerTestOneInput(FuzzedDataProvider data) {\n        client.process(data.consumeRemainingAsBytes());\n    }\n}\n```\n\n### Building in OSS-Fuzz\n\nThe `build.sh` pattern for Maven projects:\n\n```bash\n# Build the project JARs.\n$MVN package -DskipTests -Dmaven.javadoc.skip=true\n\n# Collect JARs needed at runtime.\nALL_JARS=\"mylib-1.0.jar\"\nBUILD_CLASSPATH=$(echo $ALL_JARS | xargs printf -- \"$OUT\u002F%s:\"):$JAZZER_API_PATH\nRUNTIME_CLASSPATH=$(echo $ALL_JARS | xargs printf -- \"\\$this_dir\u002F%s:\"):\\$this_dir\n\nfor fuzzer in $(find $SRC -maxdepth 1 -name '*Fuzzer.java'); do\n    fuzzer_basename=$(basename -s .java \"$fuzzer\")\n    javac -cp $BUILD_CLASSPATH \"$fuzzer\"\n    cp $SRC\u002F$fuzzer_basename.class $OUT\u002F\n\n    # Wrapper script that launches jazzer_driver with the right arguments.\n    echo \"#!\u002Fbin\u002Fbash\nthis_dir=\\$(dirname \\\"\\$0\\\")\nif [[ \\\"\\$@\\\" =~ (^| )-runs=[0-9]+($| ) ]]; then\n  mem_settings='-Xmx1900m:-Xss900k'\nelse\n  mem_settings='-Xmx2048m:-Xss1024k'\nfi\nLD_LIBRARY_PATH=\\\"$JVM_LD_LIBRARY_PATH\\\":\\$this_dir \\\\\n\\$this_dir\u002Fjazzer_driver --agent_path=\\$this_dir\u002Fjazzer_agent_deploy.jar \\\\\n--instrumentation_includes=com.example.** \\\\\n--cp=$RUNTIME_CLASSPATH \\\\\n--target_class=$fuzzer_basename \\\\\n--jvm_args=\\\"\\$mem_settings\\\" \\\\\n\\$@\" > $OUT\u002F$fuzzer_basename\n    chmod u+x $OUT\u002F$fuzzer_basename\ndone\n```\n\nFor Gradle projects replace `$MVN package` with the appropriate Gradle command\nand adjust JAR paths accordingly.\n\n### Seed corpus and dictionaries\n\n- Zip seed files to `$OUT\u002F\u003Cfuzzer_name>_seed_corpus.zip`.\n- Place dictionaries at `$OUT\u002F\u003Cfuzzer_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. See the [structured seed generation\n  reference](..\u002Foss-fuzz-engineer\u002Freferences\u002Fstructured_seed_generation.md).\n\n## Characteristics of good JVM fuzzing harnesses\n\n1. **Targets attack surface**: parsers, deserializers (JSON, XML, Protobuf,\n   custom binary formats), network protocol handlers, template engines, and\n   any API that accepts untrusted bytes or strings.\n2. **Catches expected exceptions**: wrap calls in `try\u002Fcatch` for all\n   documented exception types. Only unexpected exceptions and crashes are\n   findings.\n3. **Uses `FuzzedDataProvider`** for structured input rather than passing raw\n   bytes to methods that expect well-formed data.\n4. **Initialises heavy state in `fuzzerInitialize`**: client connections,\n   parsers with complex configuration, and loaded schemas should be set up once.\n5. **Avoids non-determinism**: no `Math.random()`, no `System.currentTimeMillis()`\n   in the fuzzing path, no thread spawning.\n6. **Sets `--instrumentation_includes`** to the package prefix of the target\n   library in the wrapper script — without this Jazzer cannot guide fuzzing.\n7. **Configures JVM memory appropriately**: use the `mem_settings` pattern\n   shown above to avoid OOM kills during runs vs. crash reproduction.\n8. **Avoids false positives**: `OutOfMemoryError`, `StackOverflowError`, and\n   `NullPointerException` on invalid input are usually expected — decide which\n   are genuine bugs for this project.\n\n## What JVM fuzzing finds\n\n- **Unexpected exceptions**: `NullPointerException`, `ArrayIndexOutOfBoundsException`,\n  `ClassCastException`, `NumberFormatException` on paths that should not throw.\n- **Assertion errors and contract violations**: internal consistency checks\n  that fail on adversarial input.\n- **Hang \u002F infinite loops**: detected by OSS-Fuzz's timeout.\n- **Security bugs**: deserialization gadgets, path traversal via crafted\n  filenames, SSRF via crafted URLs — depends on the library.\n- **Logic bugs**: incorrect output for valid-ish input.\n\nJazzer can also detect:\n- SQL injection (via JDBC hooks)\n- Path traversal (via file API hooks)\n- Command injection (via `Runtime.exec` hooks)\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 missing JAR on the classpath or an\n  uncaught expected exception — check `check_build` output carefully.\n- Build the project outside the fuzzing harness first (`mvn package` or\n  `gradle build`) to ensure the project itself compiles cleanly.\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- 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-jvm-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":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add google\u002Foss-fuzz --skill fuzzing-jvm-expert",{"tool":52,"command":53},"bunx","bunx skills add google\u002Foss-fuzz --skill fuzzing-jvm-expert",{"tool":55,"command":56},"pnpm","pnpm dlx skills add google\u002Foss-fuzz --skill fuzzing-jvm-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Foss-fuzz\u002Fblob\u002Fmaster\u002Finfra\u002Fexperimental\u002Fagent-skills\u002Ffuzzing-jvm-expert\u002FSKILL.md",true,[60],{"path":61,"resourceType":62,"resourceTypeDesc":63,"sizeBytes":64,"sourceHtmlUrl":65},"writing-good-tests.md","REFERENCE","参考文档",8268,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Ftest-driven-development\u002Fd8a2bff179711178\u002Ftest-driven-development\u002Fwriting-good-tests.md",[67,80,91,103,114],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":31},"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",[],[74,75,76,77,78,79,29],"oss","oss fuzz engineer","oss fuzz","engineer","infrastructure","with",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":31},"01M6996SBDQB83B9ACW5SPSM78","fuzzing-rust-expert","Use this skill to fuzz open source Rust software projects.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Foss-fuzz\u002Fblob\u002Fmaster\u002Finfra\u002Fexperimental\u002Fagent-skills\u002Ffuzzing-rust-expert\u002FSKILL.md",[],[87,19,88,21,89,25,26,27,29,90,30],"rust","fuzzing rust expert","rust expert","software",{"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":31},"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",[],[98,21,99,100,19,101,30,25,26,27,29,90,102],"fuzzing python","python expert","fuzzing python expert","python","atheris",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":31},"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",[],[110,21,111,19,112,29,25,26,27,113,90,30],"unsafe","fuzzing memory unsafe expert","memory","c++",{"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":31},"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",[],[19,121,122,123,21,25,26,27,29,90,30],"fuzzing go expert","go","go expert"]