jelly-codex-skill

Automate Codex CLI coding tasks via non-interactive codex exec in Claude Code.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/dev-jelly/jelly-dotclaude --skill jelly-codex-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jelly-codex-skill
Source: https://github.com/dev-jelly/jelly-dotclaude/tree/main/skills/jelly-codex-skill
Command: npx skills add https://github.com/dev-jelly/jelly-dotclaude --skill jelly-codex-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Claude Code integration that enforces deterministic, non-interactive Codex CLI usage for automated coding tasks. Provides clear guardrails like mandatory codex exec usage and pre-run authentication checks to ensure safe, reliable automation.

Core Features & Use Cases

  • MUST USE codex exec: All Codex CLI invocations must use codex exec in Claude Code's non-interactive environment.
  • Authentication Check: Always verify login status before execution; supports ChatGPT or API key-based flows.
  • Common Scenarios: Code design, architecture reviews, and implementation tasks using Codex with non-interactive prompts.
  • Templates & Help: Rich references and examples to guide usage, including help docs and session/workflow templates.

Quick Start

Run a Codex task non-interactively: codex exec -m gpt-5.1-codex -s workspace-write "Implement authentication module" with the appropriate authentication status.

Frequently Asked Questions about jelly-codex-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate coding tasks with Codex CLI in a non-interactive environment?

Automate coding tasks by running `codex exec` with non-interactive prompts in Claude Code. The Skill enforces deterministic execution, mandatory authentication checks, and predefined model defaults to ensure safe, reliable automation for code design, debugging, and multi-turn sessions.

What authentication does Codex CLI require before running automated tasks?

Codex CLI requires login verification before execution, supporting ChatGPT or API key-based authentication flows. The Skill includes built-in authentication checks to ensure you're logged in before running any `codex exec` commands.

Can I use Codex CLI for architecture design and code implementation tasks?

Yes. Codex CLI handles architecture design, code editing, implementation, API design, and debugging through non-interactive `codex exec` invocations. The Skill provides templates and references to guide complex multi-turn workflows with safety controls.

Why must I use codex exec instead of direct Codex CLI commands?

The `codex exec` wrapper enforces deterministic, testable, non-interactive execution in Claude Code's sandbox environment. It applies mandatory safety controls, authentication verification, and predefined defaults to prevent interactive prompts and ensure reliable automation.

What happens if I run Codex CLI commands interactively instead of with codex exec?

Interactive Codex CLI commands fail in Claude Code's non-interactive environment. The Skill requires `codex exec` to operate reliably; interactive execution breaks determinism and testing, defeating the automation guardrails.