Compare/Matt Pocock Skills vs oh-my-codex (OMX)

AI tool comparison

Matt Pocock Skills vs oh-my-codex (OMX)

Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.

M

Developer Tools

Matt Pocock Skills

Battle-tested Claude agent skills from decades of engineering XP

Ship

75%

Panel ship

Community

Free

Entry

Matt Pocock's Skills is the #1 trending GitHub repository today — a curated collection of Claude agent skills designed to fix the most common failure modes in AI-assisted software development. Install via `npx skills@latest`, choose which skills to activate, and your coding agent gets new slash commands like /tdd, /grill-with-docs, /diagnose, /to-prd, and /handoff. The skills tackle real pain points: misalignment (grilling sessions ensure agents understand requirements before touching code), verbosity (CONTEXT.md shared language documents reduce token waste), code quality (TDD loops give agents automated feedback cycles), and architecture drift (deliberate design reviews prevent the entropy that accelerates with AI-generated code). Each skill is a small Markdown file — easy to read, adapt, and compose. With 76,000+ stars, this is clearly resonating. It's MIT licensed and free, backed by Pocock's newsletter of 60,000+ subscribers. Whether you think AI coding agents are overhyped or not, the patterns here for keeping them aligned and productive are worth studying.

O

Developer Tools

oh-my-codex (OMX)

Like oh-my-zsh but for Codex — teams, memory, and TDD workflows

Mixed

50%

Panel ship

Community

Paid

Entry

oh-my-codex (OMX) is an orchestration layer that wraps OpenAI's Codex CLI, adding everything Codex lacks out of the box: multi-agent team coordination, persistent memory, structured workflows, and async delegation. The analogy to oh-my-zsh is apt — it doesn't replace Codex, it supercharges it. The framework ships four canonical skills: $deep-interview for intent classification and clarification, $ralplan for structured implementation planning with trade-off review, $ralph for persistent completion loops that carry a plan to verified done, and TDD and code-review workflows. Since v0.13.1, every team worker runs in an isolated git worktree by default, preventing context bleed between parallel agents. A persistent-state MCP server carries memory across sessions. Built originally by Yeachan Heo and now also at github.com/scalarian/oh-my-codex, OMX has quietly accumulated nearly 3,000 GitHub stars. It's particularly powerful for developers already comfortable with Codex CLI who want to run parallel agents on large refactors or full-stack builds — the async delegation means no more hitting Codex timeout walls.

Decision
Matt Pocock Skills
oh-my-codex (OMX)
Panel verdict
Ship · 3 ship / 1 skip
Mixed · 2 ship / 2 skip
Community
No community votes yet
No community votes yet
Pricing
Free (MIT / Open Source)
Open Source (MIT)
Best for
Battle-tested Claude agent skills from decades of engineering XP
Like oh-my-zsh but for Codex — teams, memory, and TDD workflows
Category
Developer Tools
Developer Tools

Reviewer scorecard

Builder
80/100 · ship

The /grill-with-docs skill alone is worth installing — it forces the agent to read actual documentation before writing a single line. I've been burned so many times by agents hallucinating APIs. This is the discipline layer that was missing.

80/100 · ship

The git worktree isolation per worker agent is the feature that sold me — parallel agents without stomping each other's context is exactly the problem I kept hitting in vanilla Codex. The $ralph persistent completion loop is genuinely useful for large multi-file refactors.

Skeptic
45/100 · skip

These patterns are good but they're essentially just well-written CLAUDE.md prompts. The 76k stars reflects Matt's audience size more than revolutionary tooling. Anyone who's been using coding agents seriously already has similar workflows custom-built.

45/100 · skip

Orchestration layers on top of CLI tools tend to accumulate abstraction debt fast. OMX is already on v0.13.1 with breaking changes between minor versions. Unless you're a Codex power user, you'll spend more time debugging the orchestration layer than doing actual work.

Futurist
80/100 · ship

The emergence of shareable, composable agent skill libraries signals a new layer in the software stack — above code, below LLMs. Matt is one of the first to package this formally. In two years every senior engineer will have a curated skill set they share with their team.

80/100 · ship

We're in the oh-my-zsh moment for AI agent CLIs — community-built orchestration layers will fragment and recombine until a few patterns win. OMX is one of the more principled early experiments, and its worktree-isolation approach will likely influence how official tooling handles parallelism.

Creator
80/100 · ship

The /write-a-skill skill is meta and delightful — you can use the agent to create more skills. It's a low-code way for non-engineers on product and design teams to shape how the AI assists their workflows without touching a config file.

45/100 · skip

This is deep CLI territory — not designed for non-developers at all. If you're a developer who lives in the terminal and wants to push Codex further, it's interesting. Otherwise, skip.

Weekly AI Tool Verdicts

Get the next comparison in your inbox

New AI tools ship daily. We compare them before you waste an afternoon.

Bookmarks

Loading bookmarks...

No bookmarks yet

Bookmark tools to save them for later