codex-tools

Execute and manage Codex CLI tools including file operations, shell commands, web search, and automation patterns. Use for automated workflows, tool orchestration, and full automation with permission bypass.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/codex-tools/SKILL.md

Quality

Content

57%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 content is action-rich with many executable Codex CLI patterns and useful safety framing, but it is repetitive, lacks validation checkpoints for its destructive/batch workflows, and inlines everything in a single file rather than splitting examples into references.

Suggestions

Add explicit validate-fix-retry checkpoints to the batch and destructive workflows (e.g., run tests/linters after batch_process and automate_refactoring, only proceed on pass) so workflow clarity can exceed the destructive-operations cap.

Consolidate the repeated `codex exec --dangerously-bypass-approvals-and-sandbox` examples into a compact core pattern plus a few representative cases, removing redundant near-duplicate sections to improve conciseness.

Move the large worked examples (setup_project, automate_testing, automate_refactoring) into a separate examples reference file with clearly signaled one-level-deep links from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly code with little prose, but it repeats the same `codex exec --dangerously-bypass-approvals-and-sandbox` pattern across many near-identical examples (file ops, shell, web search, batch, testing, refactoring) that could be tightened, and carries time-sensitive metadata ("Last Updated: December 2025 (GPT-5.2 Release)").	3 / 5
Actionability	It provides concrete, copy-paste-ready bash functions and commands across common cases, but the task payloads inside each `codex exec` are natural-language briefs rather than fully specified steps, leaving minor gaps versus the fully executable 5.	4 / 5
Workflow Clarity	Batch and destructive workflows (batch_process, automate_testing, automate_refactoring) lack validation/verification checkpoints; the Safety Patterns section offers a git-stash fallback but no validate-fix-retry loop, so per the destructive/batch cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	No bundle files exist and all content is inlined in one ~205-line file with section headers, but large worked examples (setup_project, batch_process, automate_testing) that belong in separate reference files are inlined and no external references are signaled.	3 / 5
	Total	13 / 20 Passed

Description

67%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 is clear and specific about Codex CLI capabilities with an explicit trigger clause covering both what and when. Trigger-term naturalness and "when" specificity are the main weaknesses keeping it just below top marks.

Dimension	Reasoning	Score
Specificity	Names the domain (Codex CLI tools) and several concrete action categories — "file operations, shell commands, web search, and automation patterns" — with only minor coverage gaps, matching the "lists several specific actions" anchor rather than the fully comprehensive 5.	4 / 5
Completeness	It explicitly states both what ("Execute and manage Codex CLI tools including...") and when ("Use for automated workflows, tool orchestration...") via an explicit trigger clause, but the "when" could be more specific about scenarios, matching anchor 4 rather than the fully concrete 5.	4 / 5
Trigger Term Quality	"automated workflows, tool orchestration, and full automation with permission bypass" are relevant but lean technical; common natural synonyms a user would actually say are missing, fitting the "some relevant keywords but missing variations" anchor rather than the well-covered 4.	3 / 5
Distinctiveness Conflict Risk	Tied specifically to the Codex CLI niche with distinct triggers, giving mostly-distinct positioning with only minor overlap risk against adjacent CLI/automation skills, so anchor 4 fits better than the minimal-conflict 5.	4 / 5
	Total	15 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: fernandezbaptiste/Skrillz
Path: skills/codex-tools/SKILL.md
Commit: 93ed392

Reviewed: 1 day 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.