Best Codex Skills That Add the Most Value in 2026

OpenAI officially launched Codex Skills as an experimental feature in December 2025, letting users create reusable, markdown-based workflows for their coding agent. The capability expanded in early 2026, with the SKILL.md format becoming an open standard adopted across Claude Code, Gemini CLI, Cursor, GitHub Copilot, and more than twenty other AI coding tools.

Codex is a capable coding agent. What limits it is not reasoning ability but context. Out of the box, Codex does not know your preferences, cannot browse the live web, and has no awareness of the workflows your team actually follows. Skills fix this. They activate when the task matches, stay dormant when it does not, and load progressively so they never waste context on unrelated work.

The community around the openai/skills repository (19.3k stars) has grown quickly since the Agent Skills spec went cross-platform. One developer on the Codex subreddit captured it directly: "With the right skills, Codex is honestly better than Claude Code for me." That is not a universal claim, but it points at something real. The right skills reshape the experience more than prompt tuning ever will. If you are still deciding between the two agents, the Claude Code vs Codex comparison covers pricing, harness depth, sandboxing, and community verdict side by side.

These are the eleven I would install first.

Codex skills are directories containing a SKILL.md file and optional supporting scripts. The SKILL.md file opens with YAML frontmatter (name, description, trigger conditions) followed by markdown instructions Codex follows when the skill activates.

At startup, Codex reads only the name and description from every installed skill using a capped budget (roughly 2% of context). When you give Codex a task, it checks whether any installed skills match. If one does, the full instructions load. If nothing matches, nothing loads and context stays clean.

The format is an open standard. The same SKILL.md file works across Codex CLI, Claude Code, Gemini CLI, Cursor, and GitHub Copilot without modification. If you want to see the same idea built end-to-end on the Anthropic side, our Claude Code skill tutorial walks through building a complete skill from scratch. For a deep dive into how agent skills became an open standard and why they grew to 40,000 installs so fast, that post covers the full story. Codex can activate a skill two ways: explicit invocation (type $skill-name or /skills in the CLI) and implicit invocation when the task description matches.

Skill locations:

Codex ships with a set of system skills automatically available to every user:

• skill-creator: Builds new skills interactively through a Q&A session
• plugin-creator: Scaffolds plugin packages that bundle skills, agents, and hooks
• skill-installer: Installs curated skills from the openai/skills repository
• imagegen: Image generation inside Codex
• openai-docs: Access to OpenAI documentation as a tool

System skills are maintained by the OpenAI team alongside Codex itself. The full curated skills library lives at github.com/openai/skills. skills.sh (maintained by Vercel) is the searchable directory for the broader ecosystem across all AI coding tools.

When OpenAI officially rolled out skills for Codex, the Hacker News announcement pulled 304 points and 130 comments. The reaction was not just curiosity — it was recognition that skills change what an agent can consistently deliver.

Skills Officially Comes to Codex — Hacker News

One developer in the thread put it plainly:

It's so nice that skills are becoming a standard, they are imo a much bigger deal long-term than e.g. MCP.

The reason is architectural: skills are context-efficient where MCP is not. A skill loads only when the task matches; MCP server definitions consume context every session regardless. Another commenter described how this compounds:

Use the agents themselves to edit / improve / add to the skills. One easy one to do is something like "take the key points from this session and add the learnings as a skill". It works both on good sessions with new paths/functionality and on "bad" sessions where you had to hand-hold the agent.

The community verdict on Reddit is direct. One user wrote "With the right skills, Codex is honestly better than Claude Code for me". A second developer in the same thread: "As somebody who has used both extensively over the past 6+ months, Codex has been better than Claude this entire time. No doubts about that."

Firecrawl's Agent Skills Explained covers what happened after the spec became an open standard: 40,285 publicly listed skills within weeks — an 18.5× growth spike driven by the same insight that skills give a general-purpose agent specialist knowledge on demand, without burning context when it is not needed. The right skills do not just tune Codex's behavior. They reshape the experience entirely.

Here are the eleven I keep installed and actually reach for.

An agent is only as smart as the context it has. The Firecrawl skill gives Codex live web context.

Codex's built-in web search queries a stale pre-scraped cache by default, silently fabricates results when network access is restricted, and returns snippets with no full-page content. The Firecrawl skill solves all of this by teaching Codex how to install and use the Firecrawl CLI automatically, giving it access to live web data without any manual configuration.

The Firecrawl CLI is built for AI agents. Results write to files rather than flooding the context window. JavaScript rendering is handled automatically. Commands map directly to how agents think about web tasks: search to find sources, scrape to read them, crawl to index an entire site, interact to control a live browser session.

If Codex is doing research, documentation lookups, or any task that requires knowing what is true today, this skill is the difference between confident answers and confident hallucinations.

Install:

npx -y firecrawl-cli@latest init --all --browser

The --all flag installs the Firecrawl skill to every detected AI coding agent on your machine. The --browser flag opens browser authentication to connect your API key. Get a free API key at firecrawl.dev/app/api-keys.

Commands Codex gets access to:

• firecrawl search: Live web search with real-time results, not a cached index (see the best web search MCP servers guide for how Firecrawl compares to Tavily and Exa)
• firecrawl scrape: Clean markdown from any page, including JavaScript-heavy sites
• firecrawl crawl: Recursively follow links across an entire site
• firecrawl map: Discover all URLs on a domain
• firecrawl interact: Scrape a page, then interact with it via natural language or Playwright code

Example:

"Check the React 19 migration guide and list any breaking changes from this month"
"Crawl the Prisma docs and find every page that mentions connection pooling"
"Research the top three competitors to our product and extract their pricing structures"

Pros: JavaScript rendering is automatic. File-based output keeps context efficient. Live results replace Codex's stale cache for documentation lookups, research, and competitor analysis.

Cons: You can try the endpoints without an API key, but ongoing use needs one and consumes credits on heavy usage. The free tier (1,000 credits per month) covers substantial testing, but production research workflows may need a paid plan.

Firecrawl is used by 1.25M+ developers and non-developers across 150,000+ companies, and has served 5B+ requests to date. It has reached that scale because it handles the full workflow — search, scrape, crawl, interact — in a single install, on the real web. Builders who need reliable web context for agentic workflows keep coming back to it — and recommend it to others. Peter Steinberger, founder of OpenClaw, put it plainly:

Users aren't just using Firecrawl's skill as-is. They're creating their own skills for custom workflows and wiring Firecrawl into them — which is where it gets really powerful. Any Codex skill that needs live web context can call Firecrawl directly, turning a one-time automation into a reusable agent workflow. Riley Brown built a skill that pulls any asset from the internet using Firecrawl and creates moodboards by one-shotting assets from any company in a single pass:

Full reference at skills.sh/firecrawl/cli. Also read: Codex web search guide for a deeper look at why the default cache falls short.

Matt Pocock's grill-me skill interviews you relentlessly about every aspect of a plan until you reach shared understanding.

The skill went viral on X recently, with developers sharing how it fixes the most common failure mode in agentic coding: Codex charging ahead with wrong assumptions before you had a chance to correct them.

The SKILL.md instruction is direct: "Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer." If a question can be answered by reading the codebase, Codex reads it and moves on rather than asking you.

This is a design review tool. Use it before you write code, not after. The questions surface implicit assumptions, dependency chains between decisions, and gaps in your plan that seem obvious until you try to articulate them. Codex's recommended answers move the session forward rather than leaving you stuck at each question with no direction.

Install:

npx skills add https://github.com/mattpocock/skills --skill grill-me

Example:

"Grill me on this feature spec before I start building"
"Run grill-me on my plan for the auth refactor"
"Walk me through every decision in this architecture before I commit to it"

Pros: Surfaces the assumptions and dependency chains in your plan before they become bugs. Codex's recommended answers move the session forward rather than just blocking you with questions. 156.2K installs. Matt Pocock's skills collection has 87.3K GitHub stars.

Cons: Requires an actual plan or design to stress-test. "I want to build X" is too vague to grill effectively. Prepare a written spec or description before invoking the skill. The session is open-ended by design, not a checklist with a fixed number of questions.

One Reddit user tried grill-me and said it completely changed how they plan with Codex. Their before: switch to plan mode, give Codex a prompt, get a plan that made wrong assumptions or included work they never asked for, then spend time asking clarifying questions and repeating the cycle. Their after: run $grill-me, Codex asks questions one by one, they make decisions together as they go — including context they hadn't considered — until there's a shared understanding, then Codex implements. The result: "it does exactly what I wanted 90% of the time, and reviewing the code it generates is a lot easier."

r/codex: "I tried the grill-me skill and it completely changed how I plan with Codex"

Full reference at skills.sh/mattpocock/skills/grill-me.

Matt Pocock's handoff skill compresses your current agent session into a structured markdown document so you can continue the work in a fresh session — or pass it to a different agent entirely.

The problem it solves is context drift. As discussed on HN, sessions nearing compaction limits don't just slow down — they get dumber. After roughly 120k tokens, attention relationships strain and response quality degrades. /handoff gives you a clean exit before you hit that wall: it generates a document containing the purpose of the next session, relevant context from the current one, suggested skills to invoke, and pointers to existing artifacts — without duplicating content.

The difference from /compact is intent. Compact keeps you in the same thread with a compressed summary. Handoff is for moving on — to a new session, a fresh worktree, or a completely different agent. Ben Holmes captured the pattern that makes this genuinely powerful: plan in Claude Code with /grill-me, then pass the handoff doc to multiple Codex worktrees for parallel implementation:

Install: