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.
Developer Tools
Matt Pocock Skills
21+ battle-tested Claude agent skills from TypeScript's top educator
75%
Panel ship
—
Community
Free
Entry
Matt Pocock — known for Total TypeScript and beloved among frontend developers — has published his personal directory of Claude agent skills straight from his own `.claude` directory. The repository contains 21+ modular skills organized across four areas: Planning & Design (to-prd, to-issues, grill-me), Development (tdd, triage-issue, improve-codebase-architecture), Tooling (setup-pre-commit, git-guardrails-claude-code), and Writing & Knowledge (edit-article, ubiquitous-language, obsidian-vault). Installation is a single command — `npx skills@latest add mattpocock/skills/[skill-name]` — and each skill is a self-contained module that plugs into Claude Code or similar agent runners. The repository blew up on GitHub trending today with 857 stars, reflecting how hungry developers are for curated, production-tested skill templates from people who actually use them daily. What makes this different from generic awesome-lists is the editorial voice — these are skills Pocock actually uses in his content production workflow. The `edit-article` skill, `write-a-skill` meta-skill, and `obsidian-vault` integration reflect real non-code use cases that most developer-focused skill repos ignore entirely. MIT licensed.
Developer Tools
oh-my-codex (OMX)
Oh-my-zsh but for OpenAI Codex CLI — agent teams, hooks, and structured workflows
50%
Panel ship
—
Community
Paid
Entry
oh-my-codex (OMX) is an open-source orchestration layer for OpenAI's Codex CLI, created by Yeachan-Heo. The framing is dead simple: like oh-my-zsh extended the terminal, OMX extends Codex CLI with structured multi-agent workflows, customizable hooks, persistent memory, and a heads-up display (HUD) for monitoring agent activity. It hit 2,867 GitHub stars within days of going trending in early April 2026. OMX's key innovation is team-based execution: rather than one AI agent working through a task linearly, OMX spawns specialist roles — planner, implementer, reviewer, tester — each running in an isolated git worktree to prevent conflicts. The $deep-interview workflow gathers context before starting, $ralplan creates a structured action plan, and $team coordinates the parallel execution. It also adds native Codex hook ownership with PreToolUse/PostToolUse guidance, and ships with Windows and tmux reliability improvements. The practical use case: you have a complex feature to build across multiple files, and you want Codex to plan it properly before touching any code, run specialists in parallel for different modules, and produce a PR-ready result. OMX is that layer. It's explicitly for power users who already live in the terminal and find vanilla Codex too unstructured for serious projects.
Reviewer scorecard
“The TDD skill and git-guardrails-claude-code alone are worth the install. Pocock's skills reflect how a TypeScript professional actually works — not generic demo code. The npx install pattern is elegant and composable.”
“If you use OpenAI Codex CLI daily, OMX is an immediate productivity upgrade. Structured $deep-interview → $ralplan → $team workflows mean Codex actually understands the codebase before writing, and isolated git worktrees for parallel specialists eliminate the merge conflicts that kill multi-agent coding sessions.”
“This is one person's personal workflow, not a maintained framework. Skills will drift as Claude updates and Pocock's priorities shift. You're better off building your own SKILL.md files once you understand the pattern.”
“This is a power-user wrapper on Codex CLI, which itself is still early-stage software. You're now debugging two layers of abstraction when things break. The hook system is clever but brittle — and the project is maintained by one developer. Evaluate your risk tolerance before making this a team dependency.”
“When influential developers publish their agent workflows publicly it accelerates the entire ecosystem's skill vocabulary. This is how best practices emerge — through high-signal personal repos from trusted practitioners.”
“Multi-agent coding with isolated worktrees and structured pre-work phases is the right abstraction for complex software. OMX ships this today in a scrappy, hackable form that feels like a preview of where all coding agents are heading in 18 months. The project may get superseded — but the pattern it establishes won't.”
“The edit-article and ubiquitous-language skills are gems for anyone who writes documentation or content alongside code. Having a creator's perspective embedded in a developer's skill repo is refreshingly rare.”
“Terminal-native and entirely engineer-focused. Zero relevance for creative workflows unless someone builds a GUI on top. Check back if a visual interface emerges.”
Weekly AI Tool Verdicts
Get the next comparison in your inbox
New AI tools ship daily. We compare them before you waste an afternoon.