vulnerability-writeup — Codex skill: what it does, how to install
Turns vulnerability notes, PoCs, and source code into a checked, self-contained report. Use it to assess one finding or a disclosure campaign.
npx skills add openai/plugins --skill vulnerability-writeup -a codexWhat vulnerability-writeup does
This skill turns vulnerability notes, disclosure documents, PoCs, source trees, or Codex Security findings into a self-contained report. It treats the original finding as a hypothesis, then checks the entry point, expected behaviour, actual failure, and demonstrated impact before making a strong claim.
Its workflow covers software and source revision checks, tracing the vulnerable code, reviewing release history and fixes, and keeping separate reports for distinct findings. The result is written for another researcher to inspect and reproduce. A Codex Security scan is optional.
Verify the exact vulnerable source revision first, because source-dependent conclusions need that evidence. PoCs must run only against explicitly authorised targets; destructive checks call for disposable local targets.
What it helps with
- turn vulnerability notes and a PoC into a report
- test whether an original finding holds up
- map vulnerable behaviour to a software release
- describe the entry point and demonstrated impact
- separate observed evidence from inference
Example prompts for the agent
- Review this vulnerability finding and write a self-contained report from the source code and PoC.
- Turn these disclosure notes into a report for one vulnerability, separating verified evidence from assumptions.
- Assess these Codex Security findings and produce a reproducible report with the narrowest demonstrated impact.
How to install vulnerability-writeup
1Skills CLI (Vercel)
npx skills add openai/plugins --skill vulnerability-writeup -a codex2Manually: put the files in place
.agents/skills/vulnerability-writeup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add openai/plugins --skill vulnerability-writeup -a claude-code2Manually: put the files in place
~/.claude/skills/vulnerability-writeup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vulnerability-writeup/
Manually: put the files in place
.cursor/skills/vulnerability-writeup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install openai/plugins vulnerability-writeup2Manually: put the files in place
.github/skills/vulnerability-writeup/SKILL.mdPlatform CLI
gemini skills install https://github.com/openai/plugins --path plugins/codex-security/skills/vulnerability-writeupManually: put the files in place
.devin/skills/vulnerability-writeup/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set201
The whole set →Similar
Questions about vulnerability-writeup
How do I install vulnerability-writeup in Codex?
Run these steps in order: npx skills add openai/plugins --skill vulnerability-writeup, then npx skills add openai/plugins --skill vulnerability-writeup -a codex. The installed skill file is .agents/skills/vulnerability-writeup/SKILL.md.
What does vulnerability-writeup do?
It turns vulnerability material into a self-contained report. The skill checks evidence, software and source revisions, the reachable entry point, and the demonstrated impact.
Do I need a Codex Security scan to use the skill?
No. It accepts notes, disclosure documents, PoCs, and source code directly; a Codex Security scan is optional.