codex-cli-bridge

Bridge between Claude Code and OpenAI Codex CLI - generates AGENTS.md from CLAUDE.md, provides Codex CLI execution helpers, and enables seamless interoperability between both tools

Install with Tessl CLI

npx tessl i github:alirezarezvani/claude-code-skill-factory --skill codex-cli-bridge

What are skills?

Review — 46%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 11 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

57%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear, distinctive niche (Claude Code/Codex CLI bridging) with specific file references, but lacks explicit trigger guidance and natural user language. The 'what' is partially covered but could be more concrete about specific actions, and the 'when' is entirely missing.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios like 'Use when migrating from Claude Code to Codex, converting CLAUDE.md files, or running Codex CLI commands'

Include natural user phrases like 'convert', 'migrate', 'switch tools', 'port configuration' that users would actually say when needing this skill

Replace vague phrases like 'execution helpers' and 'seamless interoperability' with concrete actions like 'translates configuration syntax' or 'runs Codex commands from Claude context'

Dimension	Reasoning	Score
Specificity	Names the domain (Claude Code/OpenAI Codex CLI interoperability) and some actions ('generates AGENTS.md from CLAUDE.md', 'provides Codex CLI execution helpers'), but 'enables seamless interoperability' is vague and 'execution helpers' lacks concrete detail.	2 / 3
Completeness	Describes what it does (bridge, generates files, provides helpers) but lacks an explicit 'Use when...' clause. The when is only implied through the description of capabilities, not explicitly stated.	2 / 3
Trigger Term Quality	Includes relevant technical terms like 'AGENTS.md', 'CLAUDE.md', 'Codex CLI', 'OpenAI', but missing natural user phrases like 'convert', 'migrate', 'switch between tools', or variations users might actually say when needing this functionality.	2 / 3
Distinctiveness Conflict Risk	Very specific niche targeting Claude Code and OpenAI Codex CLI interoperability with distinct file references (AGENTS.md, CLAUDE.md). Unlikely to conflict with other skills due to the unique tool combination.	3 / 3
	Total	9 / 12 Passed

Implementation

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is overly verbose and repetitive, explaining the same concepts multiple times while failing to provide complete, executable code. The structure attempts organization but results in a monolithic document that could benefit from splitting into focused reference files. The actionability is hampered by referencing Python scripts that aren't actually provided.

Suggestions

Remove redundant explanations (e.g., consolidate all 'always use codex exec' mentions into one clear statement in Best Practices)

Provide actual executable Python implementations for the scripts listed, or remove the script descriptions and show only the bash commands users should run

Split troubleshooting, installation, and detailed examples into separate reference files linked from a concise main SKILL.md

Add explicit validation steps with expected outputs (e.g., 'After generation, verify AGENTS.md contains ## Available Skills section')

Dimension	Reasoning	Score
Conciseness	Extremely verbose with significant redundancy. The document repeats concepts multiple times (e.g., 'always uses codex exec' appears 4+ times), includes unnecessary sections like License/Version metadata, and explains obvious concepts. The 'Key Capabilities' section duplicates information found in later detailed sections.	1 / 3
Actionability	Provides concrete command examples and JSON schemas, but the Python code shown is incomplete/pseudocode (imports from non-existent modules like 'codex_executor'). The scripts section lists filenames without actual implementations, making it not copy-paste ready.	2 / 3
Workflow Clarity	Multi-step processes are listed (e.g., 'What happens' sections) but lack explicit validation checkpoints. The AGENTS.md generation workflow mentions safety checks but doesn't show how to verify success or handle failures between steps.	2 / 3
Progressive Disclosure	Has some structure with sections and references to external files (openai-codex-cli-instructions.md, etc.), but the main document is monolithic at 300+ lines. Content that could be in separate files (troubleshooting, installation, examples) is all inline.	2 / 3
	Total	7 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.