path-types

Choose Rust types for operating system paths across the Codex repository. Use when defining new path-bearing types or explicitly migrating existing ones.

Quality

69%

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 ./.codex/skills/path-types/SKILL.md

Quality

Content

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

A lean, specific policy skill with concrete type-selection guidance and clean structure, held back only by absent validation checkpoints for batch migration and a couple of trimmable rationale lines.

Suggestions

Add an explicit validation step for the migration workflow (e.g., 'after migrating, run cargo check and the path-type tests') to lift workflow clarity above the destructive/batch cap of 3.

Trim the closing rationale paragraphs ('It is OK if the conversion... somewhat lossy' and 'Migrating to URIs should not add significant new failure modes') into a single concise note to improve token efficiency.

Include a short code snippet showing a typical type boundary (e.g., LegacyAppPathString -> PathUri conversion at the protocol boundary) to make the guidance copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Dense rule bullets assume Claude's competence with no padding about what paths or URIs are; the closing rationale paragraphs ('It is OK if the conversion... somewhat lossy', 'Migrating to URIs should not add significant new failure modes') are minor over-explanation that could be trimmed, placing it just below the lean anchor 5.	4 / 5
Actionability	Names exact types per context ('use LegacyAppPathString', 'convert it to PathUri', 'use AbsolutePathBuf or PathBuf'), giving highly actionable instruction-only guidance, but lacks code examples showing usage signatures, so it is just below the fully copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	The per-server bullets form a clear decision structure, but the batch migration context has no validation or verification checkpoints (e.g., run cargo check/tests after migrating), so per the guideline workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	Under 50 lines with no external references needed and well-organized sections (intro bullets plus a '## Migration requirements' section), meeting the simple-skill exception for a top score without bundle files.	5 / 5
	Total	16 / 20 Passed

Description

66%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 tightly scoped, distinctive description that clearly states both capability and explicit trigger conditions, with only minor limits on action breadth and natural-term coverage.

Dimension	Reasoning	Score
Specificity	Quotes 'Choose Rust types for operating system paths across the Codex repository' name the domain plus one concrete action (choosing types); 'migrating existing ones' is a trigger context rather than a distinct action, so it sits at the '1-2 concrete actions' anchor and below the 'several specific actions' anchor 4.	3 / 5
Completeness	Explicitly answers both what ('Choose Rust types for operating system paths across the Codex repository') and when ('Use when defining new path-bearing types or explicitly migrating existing ones'), but the 'what' is a single action rather than a comprehensive list, keeping it just below the concrete-multi-trigger anchor 5.	4 / 5
Trigger Term Quality	Triggers like 'defining new path-bearing types' and 'migrating existing ones' are relevant but fairly technical phrasing, missing the more natural synonyms a user might say; matches 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The narrow, repo-specific niche of choosing Rust path types for the Codex repository gives a clear distinct trigger set with minimal overlap risk against other skills.	5 / 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: openai/codex
Path: .codex/skills/path-types/SKILL.md
Commit: 78245b4

Reviewed: 5 days 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.