CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

codex-auth

Setup and manage OpenAI Codex CLI authentication including ChatGPT Plus/Pro OAuth, API keys, and multi-account management. Use when configuring Codex access, switching accounts, or troubleshooting authentication.

Quality

72%

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 ./.claude/skills/codex-auth/SKILL.md

The canonical home for this skill is codex-auth in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

50%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 is rich with executable, copy-paste-ready commands and configurations, but it functions as a monolithic reference manual rather than a skill: it is noticeably verbose with padded sections and undated-version annotations, offers no progressive disclosure via bundle files, and lacks explicit workflow sequencing with validation checkpoints. Actionability is its strongest dimension.

Suggestions

Move bulk reference material (CI/CD pipeline recipes, the configuration-profile catalog, keychain/pass storage guides, audit logging) into references/ files and keep SKILL.md as a concise overview with clearly signaled one-level-deep pointers.

Cut padding that assumes Claude's ignorance: the 'Benefits' bullet lists, pass/GPG installation walkthroughs, the trivial $ENV if/elif example, and the comment-only 'Least Privilege' and 'Related Skills'/'Updates' sections — and isolate the December-2025 version markers into a single dated section rather than scattering them through configs.

Restructure setup and troubleshooting as sequenced workflows with explicit validation checkpoints (e.g., login -> verify with 'codex exec' -> only then proceed), and add a validation step before the destructive 'rm -rf ~/.codex/credentials' credential reset.

DimensionReasoningScore

Conciseness

The 583-line body contains several padded or unnecessary sections: 'Benefits' bullet lists, pass/GPG installation walkthroughs Claude already knows, a trivial $ENV if/elif example, a comment-only 'Least Privilege' section, and repeated verification one-liners. Time-sensitive markers ('Last Updated: December 2025 (GPT-5.2 Release)', '(December 2025)' comments) are scattered throughout rather than confined to a deprecated section.

2 / 5

Actionability

Most sections are concrete, copy-paste-ready commands and configs (codex login/exec, config.toml with priority order, GitHub Actions YAML, TOML profiles). Minor gaps: the 'Least Privilege' section is comment-only with no executable guidance, and the audit script has a tilde-expansion bug ('local log_dir="~/.codex/audit"' will not expand, creating a literal '~' directory).

4 / 5

Workflow Clarity

Content is organized by scenario rather than as a sequenced workflow; verification snippets ('codex exec "Test authentication"', test_all_accounts) exist but as scattered inline checks rather than explicit validate-then-fix-then-retry checkpoints. The destructive 'rm -rf ~/.codex/credentials' step has no validation before or after it.

3 / 5

Progressive Disclosure

No references/, scripts/, or assets/ bundle exists, so all 583 lines — CI/CD recipes, the profile catalog, keychain/pass storage guides, and audit logging — are inlined in one file. Section headers do provide real navigation structure (so above anchor 2's header-less example), but large tracts that clearly belong in separate reference files are inline, matching anchor 3.

3 / 5

Total

12

/

20

Passed

Description

83%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.

A strong description with an explicit what-and-when structure, natural trigger phrases, and a well-delineated niche. Its only weaknesses are general verbs in the capability list, a few missing trigger synonyms, and one slightly broad trigger ('configuring Codex access').

DimensionReasoningScore

Specificity

Names the domain ('OpenAI Codex CLI authentication') and enumerates several concrete capabilities ('ChatGPT Plus/Pro OAuth, API keys, and multi-account management'), though the verbs themselves ('Setup and manage') are general rather than a full list of distinct actions as in the anchor-5 example.

4 / 5

Completeness

Explicitly answers both questions: a clear 'what' ('Setup and manage OpenAI Codex CLI authentication including ChatGPT Plus/Pro OAuth, API keys, and multi-account management') followed by an explicit 'Use when' clause with three concrete triggers ('configuring Codex access, switching accounts, or troubleshooting authentication').

5 / 5

Trigger Term Quality

'configuring Codex access', 'switching accounts', and 'troubleshooting authentication' are natural phrases users would say, but common variations like 'log in', 'sign in', or 'API key setup' are absent from the when-clause.

4 / 5

Distinctiveness Conflict Risk

The authentication niche is clear with auth-specific triggers, but 'configuring Codex access' is slightly broader than authentication and sibling skills (codex-cli, codex-git) exist, creating minor overlap risk with closely related skills.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (583 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/Skrillz

Path

.claude/skills/codex-auth/SKILL.md

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.