Audit skill for Codex.
The Audit skill has Codex review a product flow, screen or funnel by capturing screenshots first, then reporting UX, design and accessibility findings tied to each step. It ships in OpenAI’s Product Design plugin.
Updated November 12, 2026 · 3 min read
At a glance
| Skill name | audit |
| Comes with | The Product Design plugin, by OpenAI |
| Install | codex plugin add product-design@openai-curated, or /plugins in Codex |
| Codex uses it | When you ask it to audit, review, critique or give feedback on a flow, onboarding, checkout or screen |
| Source | openai/plugins on GitHub |
What it does
The skill won’t give a loose opinion. It first settles which product, which flow and which capture tool to use, then moves through the flow one step at a time. At each step it waits for the screen to settle, takes a screenshot, and rejects it if it’s blank, cropped, loading or showing the wrong state.
Its notes follow a framework file with two sets of lenses:
- UX: task entry, information architecture, friction, hierarchy, trust, empty states, copy and calls to action, and consistency.
- Accessibility: contrast, reading order, keyboard and focus, target size, labels and error recovery, motion, reflow and zoom, and assistive-technology clarity.
The report is inline in the chat, with the screenshots in flow order, a verdict, a numbered step list with the health of each step, and the changes that matter most. It states what screenshots can’t prove and never claims full accessibility compliance. It uses only evidence from the current run, not old screenshots or help-center pages. If you ask for a Figma board, it lays the screenshots and notes out there as well.
When to use it
Use it before a redesign, or to check a flow you just shipped. Because every finding points to a real screenshot, the report is easy to hand to a team.
Try it
Use the audit skill. Audit the sign-up flow on our staging site, from the landing page to the first dashboard screen. Screenshot each step and report UX and accessibility issues, most important first.
Does it work in Claude Code?
Partly. The audit method and the framework file are plain text you can copy into ~/.claude/skills. But the skill’s capture steps point to the Codex in-app browser and to the Product Design plugin’s router skill, which won’t come with it. In Claude Code you’d need a browser tool that can take screenshots, and the Figma board option needs the Figma MCP server.