GUIDE · CODEX
Choose a Skill for the work in front of you, not for a generic promise of autonomy. These candidates explicitly list Codex as native support and expose the tradeoffs you should inspect first.
The goal is a smaller, reviewable starting stack for Codex. Each card points back to the fuller profile, source evidence, and Agent-specific install guidance.
SELECTION ORDER
Use a short sequence rather than installing a whole category at once. The important signal is the match between scope, access, and your current task.
Start with the work type: code review, browser work, research, documents, or delivery
Keep native Codex support separate from portable SKILL.md compatibility
Prefer the least access needed for the first controlled test
Treat a high score and popularity as evidence to inspect, not proof of safe behavior
REVIEWABLE CANDIDATES
Sorted from the same published SkillSignal metadata score used throughout the directory. Scores are signals, not safety approval.
Browser automation built for repeatable agent workflows.
Design constraints that push generated interfaces beyond generic AI UI.
Build, analyze and verify spreadsheet files with formula-aware workflows.
Create and edit professional Word documents with visual verification.
Review interfaces against practical web design and accessibility rules.
Relentless decision interviews for sharper plans and designs.
DECISION BOUNDARY
A clear install path does not validate the full runtime behavior of a Skill with Codex. Review its instructions and test it in a controlled project before relying on it.
KEEP EXPLORING
Use the directory matcher to combine your task, system, permission limit, price preference, and Codex fit. It uses deterministic rules and metadata only.
Open the Skill matcher ↗