oss-fuzz
Use when enrolling a project in OSS-Fuzz, running its helper workflow locally, or reproducing an OSS-Fuzz report. Not for remote, credential, publish, deploy, or irreversible changes.
Install / Use
npx skills add OutlineDriven/outline-driven-development --skill oss-fuzzInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Tags
Our assessment of oss-fuzz
oss-fuzz scores 62/100 on our quality scale, 2678th of 2,790 Automation skills we index.
Its SKILL.md is 7.1 KB long, well organised into 8 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-11-16. Automated pattern scan on 2026-11-16. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
oss-fuzz compared with similar skills
All 4 of these similar skills score higher than oss-fuzz; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| oss-fuzz (this skill)by OutlineDriven | 62 | 0 | — | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install oss-fuzz?
- Run
npx skills add OutlineDriven/outline-driven-development --skill oss-fuzz. The install tabs above show the steps for each supported agent. - Which AI agents does oss-fuzz work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is oss-fuzz safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is oss-fuzz still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubname: oss-fuzz description: 'Use when enrolling a project in OSS-Fuzz, running its helper workflow locally, or reproducing an OSS-Fuzz report. Not for remote, credential, publish, deploy, or irreversible changes.' disable-model-invocation: true
OSS-Fuzz
Contract
| Field | Bound contract |
|---|---|
| Trigger | User needs to enroll an open-source project in OSS-Fuzz, run its helper workflow locally, or reproduce an OSS-Fuzz report. |
| Authority | Reversible local: writes only named local artifacts (oss-fuzz clone, Docker images, project enrollment files); rollback is docker rmi for images and filesystem deletion for the clone. No remote mutation. |
| Side effect | OSS-Fuzz project integration files, Docker image builds, and local fuzzing campaign artifacts written to the oss-fuzz working directory. |
| Done | Task A: the project Docker image builds, fuzzers compile with AddressSanitizer, and the named harness executes. Task B: projects/<project_name>/project.yaml, Dockerfile, and build.sh are present and structurally valid. |
Inputs
| Input | Required | Description |
|---|---|---|
| project_name | Required | OSS-Fuzz project identifier (slug used in infra/helper.py commands and the projects/ subdirectory). |
| harness_name | Required for local run | Fuzzer executable name inside the project's build output directory. |
| language | Required for enrollment | Project language (e.g. c++, python, rust, go). |
| main_repo | Required for enrollment | URL of the project's primary source repository. |
| sanitizer | Optional | Sanitizer for build_fuzzers: address (default), undefined, coverage. |
| fuzzer_args | Optional | Extra arguments passed through to the fuzzer binary. |
| oss_fuzz_dir | Optional | Local path of the cloned oss-fuzz repository; defaults to ./oss-fuzz. |
| primary_contact | Required for enrollment | Maintainer email for project.yaml. |
Procedure
Task A: run an enrolled project locally
- Verify
dockeris available and the user has permission to run containers (docker infoexits 0). Done when:docker infoexits 0. - Clone oss-fuzz if
oss_fuzz_dirdoes not exist or is not a git repository:
Done when: the oss-fuzz repository is cloned and present atoss_fuzz_dir="${oss_fuzz_dir:-./oss-fuzz}" git clone https://github.com/google/oss-fuzz "$oss_fuzz_dir"oss_fuzz_dir. - Change to the oss-fuzz directory:
Done when: the working directory is the oss-fuzz directory.oss_fuzz_dir="${oss_fuzz_dir:-./oss-fuzz}" cd "$oss_fuzz_dir" - Build the project Docker image:
Ifproject_name="${project_name:?project_name is required}" uv run --no-project python infra/helper.py build_image --pull "$project_name"build_imagereports the project directory does not exist underprojects/, stop and returnenrollment-missing. Done when: the project Docker image builds successfully orenrollment-missingis returned. - Build the fuzzers with AddressSanitizer:
Capture stdout/stderr. If the build exits non-zero, returnproject_name="${project_name:?project_name is required}" sanitizer="${sanitizer:-address}" uv run --no-project python infra/helper.py build_fuzzers --sanitizer="$sanitizer" "$project_name"build-failedwith the captured output. Done when: fuzzers compile with the configured sanitizer and stdout/stderr are captured. - Run the named harness:
Observe for at least 10 seconds. If the harness exits with a sanitizer report, returnproject_name="${project_name:?project_name is required}" harness_name="${harness_name:?harness_name is required}" fuzzer_args="${fuzzer_args:-}" uv run --no-project python infra/helper.py run_fuzzer "$project_name" "$harness_name" ${fuzzer_args:+"$fuzzer_args"}crash-detectedwith the report path. Otherwise returnharness-ran. Done when: the harness runs for at least 10 seconds and returnsharness-ranorcrash-detected.
Task B: enroll a new project
- Verify the project has an OSS-Fuzz-compatible harness at
$main_repoor an associated harness repository. Done when: a compatible harness is confirmed at$main_repoor the associated repository. - Create
projects/<project_name>/under the oss-fuzz directory. Done when: the project directory is created. - Write
projects/<project_name>/project.yaml:
Extendhomepage: "<main_repo>" language: "<language>" primary_contact: "<primary_contact>" main_repo: "<main_repo>" fuzzing_engines: - libfuzzer sanitizers: - addresssanitizersandfuzzing_enginesif the task specifies additional values. Done when:project.yamlis written with all required fields and any extensions. - Write
projects/<project_name>/Dockerfileusinggcr.io/oss-fuzz-base/base-builderas the base image; add language-specific and project-specificRUNcommands to install build dependencies. Do not copy source code directly; usegit clonein the Dockerfile. Done when:Dockerfileis written with the base image andgit clonefor source. - Write
projects/<project_name>/build.shas an executable script:- Set
#!/bin/bash -eu. - Clone or build project dependencies.
- Compile harnesses using
$CXX,$CXXFLAGS,$LIB_FUZZING_ENGINE,$SRC, and$OUTas provided by the OSS-Fuzz environment. - Copy corpus and dictionary files to
$OUTif present. Done when:build.shis written as an executable script with all four elements.
- Set
- Return
enrollment-artifacts-writtenlisting the three files and their paths. Done when: the three artifact paths are returned.
Failure and recovery
| Failure class | Trigger | Result |
|---|---|---|
| docker-unavailable | docker info exits non-zero | Return blocked: docker-unavailable. Do not attempt container operations. |
| enrollment-missing | projects/<project_name> absent and task is local run | Return blocked: enrollment-missing. Enrollment is out of scope for local-run unless explicitly requested. |
| build-failed | build_fuzzers exits non-zero | Return failed: build-failed with captured stderr. Do not proceed to run step. |
| crash-detected | Harness exits with ASan/UBSan report | Return crash-detected with the report file path. Do not suppress or dismiss the report. |
| rollback | Any step fails; Docker images written by this session | Rollback: docker rmi $(docker images --filter=reference="gcr.io/oss-fuzz/$(basename "$project_name")*" -q) 2>/dev/null; delete the oss_fuzz_dir clone if this session created it. |
Output
| Outcome | Output |
|---|---|
| Local run, build success, no crash | done: harness-ran: fuzzer is running and producing coverage or execution output. |
| Local run, crash detected | crash-detected: <report-path>: sanitizer report written to the build output directory. |
| Enrollment artifacts written | done: enrollment-artifacts-written: project.yaml, Dockerfile, build.sh paths listed. |
| Build failed | failed: build-failed: full build log for diagnosis. |
| Prerequisites not met | blocked: <failure-class>: reason stated, no progress claimed. |
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
