CtrlK
BlogDocsLog inGet started
Tessl Logo

codex-claude-loop

Orchestrates a dual-AI engineering loop where Claude Code plans and implements, while Codex validates and reviews, with continuous feedback for optimal code quality

58

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/codex-claude-loop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

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

The body delivers a well-sequenced, validation-rich workflow with concrete codex commands, but is padded by restated loops and a duplicate command table. Structure is good though some content could be externalized.

Suggestions

Remove the 'The Perfect Loop' ASCII diagram and the 'Command Reference' table, or consolidate them so commands appear only once to improve conciseness.

Replace placeholders like '[Claude's plan here]' with a concrete minimal example and fill in the missing '-m' model value so commands are copy-paste ready.

Consider moving the Command Reference and Error Handling detail into a references/ file, keeping SKILL.md as a lean overview with one-level-deep navigation.

DimensionReasoningScore

Conciseness

Mostly efficient phase-based content, but the 'Perfect Loop' ASCII diagram, 'Best Practices', and 'Command Reference' table substantially duplicate the inline phase instructions and bash examples.

3 / 5

Actionability

Provides concrete executable codex commands with flags and named tools, but placeholders like '[Claude's plan here]' and an incomplete '-m' value keep it just short of copy-paste ready.

4 / 5

Workflow Clarity

A clear six-phase sequence with explicit, recurring validation checkpoints (plan validation, cross-review, re-validate loop) and dedicated error-recovery sections.

5 / 5

Progressive Disclosure

Well-organized into clear sections with no bundle files, but the ~100-line body duplicates command material that could be split into references, leaving minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

58%Weight 40%Scale 1-5

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 clearly conveys the skill's purpose and role division but omits explicit trigger guidance ('when to use'), which caps completeness. It is reasonably specific and distinct, with adequate but not comprehensive natural keywords.

Suggestions

Add a 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when the user wants a reviewed, two-AI implementation workflow or asks for Codex-backed code review').

Include more natural trigger phrases users would actually say, such as 'code review', 'review my implementation', or 'pair-program with Codex'.

Name a concrete output/deliverable (e.g., 'produces validated, reviewed code changes') to lift specificity from 4 toward 5.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Claude Code plans and implements', 'Codex validates and reviews', 'continuous feedback'), with a minor gap in naming concrete deliverables.

4 / 5

Completeness

Has a clear 'what' (orchestrates a dual-AI loop with role assignments) but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant keywords ('engineering loop', 'code quality', 'validates and reviews') but leans technical and omits common natural phrasings like 'code review' or 'review my code'.

3 / 5

Distinctiveness Conflict Risk

The dual-AI Claude+Codex framing carves a distinct niche with only minor overlap risk against general code-review skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
bear2u/my-skills
Reviewed

Table of Contents

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.