Skip to content
BSWEN
Blog

What Are the Best Skills for Codex CLI

Cowrie
Cowrie
Dev @ Bswen

Developer working with AI tools

Problem

When I started using Codex CLI, I got decent results for simple tasks. But for specialized work like frontend design or thorough planning, the outputs were inconsistent.

I’d ask Codex to design a UI component and get generic, unstyled HTML. I’d request a feature implementation and get code that missed half my requirements. The default Codex behavior wasn’t optimized for specific domains.

What happened?

Codex CLI is powerful out of the box, but it lacks domain-specific optimizations. The default prompt templates don’t know that:

  • Frontend components need proper styling and accessibility
  • Planning requires interrogating requirements before coding
  • Code review should catch AI-specific anti-patterns

Here’s what I got from a default Codex prompt for a button component:

Generic output from default Codex
<button>Submit</button>

That’s technically correct but useless in production.

How to solve it?

I discovered that Codex CLI supports “skills” - specialized prompt templates created by the community. Each skill optimizes Codex for a specific task type.

The Top 5 Skills for Codex CLI

After testing and reading community recommendations, here are the skills that made the biggest difference:

1. Grill Me (Planning)

Best for: Complex features requiring thorough upfront planning

Grill Me interrogates you about requirements before coding begins. It asks clarifying questions:

Grill Me workflow example
User: I want to add authentication
Grill Me: What auth provider? OAuth or email?
          Need password reset? 2FA requirements?
          Session duration preferences?
          What's your user model structure?

This prevents scope creep and ensures Codex understands full context.

2. Superpowers (General Enhancement)

Best for: Overall productivity boost

Created by obra, Superpowers adds commonly-needed capabilities that Codex CLI lacks by default. It improves the general coding workflow.

3. design-skill (Frontend Design)

Best for: UI/UX work, component design

This skill produces superior frontend results. The same button request now gives:

Production-ready output from design-skill
<button class="px-4 py-2 bg-blue-600 hover:bg-blue-700
               text-white rounded-md shadow-sm
               transition-colors duration-200
               focus:outline-none focus:ring-2
               focus:ring-blue-500 focus:ring-offset-2">
  Submit
</button>

Proper styling, accessibility, hover states - everything a production component needs.

4. ai-grouch (Code Review)

Best for: Ensuring code quality before commits

Provides strict, thorough code reviews that catch issues default reviews miss. It specifically looks for patterns that AI coding tends to produce poorly.

5. Playwright MCP (Browser Automation)

Best for: E2E testing, browser-based debugging

Enables Codex to interact with browsers for testing and fixing non-frontend issues.

Installing Skills

Install skills
# From skills.sh repository
codex skill add mattpoclock/skills/grill-me


# From GitHub
codex skill add https://github.com/obra/superpowers
codex skill add https://github.com/arjunkshah/design-skill
codex skill add https://github.com/vectorlane80/ai-grouch-codex

Skill Selection Guide

Choose the right skill
Task Type              → Recommended Skill
───────────────────────────────────────────
Planning new feature   → Grill Me
UI/UX development      → design-skill
Code review            → ai-grouch
E2E testing            → Playwright MCP
General productivity   → Superpowers

The reason

I think skills work because they encode domain expertise into prompt templates. Instead of generic instructions, each skill applies patterns that experts use for that specific task type.

When I use design-skill:

  • The prompt includes frontend best practices
  • Styling conventions are built in
  • Accessibility requirements are specified
  • Responsive design patterns are included

When I use Grill Me:

  • The prompt forces requirement gathering
  • Ambiguities get resolved before coding
  • Scope is locked down early
  • Codex has clear targets to hit

Common mistakes to avoid

1. Using no skills at all

You’re missing significant productivity gains by sticking with defaults.

2. Using wrong skill for the task

Don’t use design-skill for backend logic. Each skill has optimal use cases.

3. Not updating skills

Skills improve with community contributions. Check for updates periodically.

4. Ignoring skill documentation

Each skill has optimal usage patterns. Read the docs to get best results.

Summary

In this post, I showed the best skills for Codex CLI based on community recommendations. The key point is specialized skills like Grill Me for planning and design-skill for frontend dramatically improve output quality.

Start with Grill Me for your next complex feature - you’ll experience the difference immediately. Then add design-skill if you do frontend work, and ai-grouch for better code reviews.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!

Comments

Tags: