Codex CLI 0.166.0 was released on 29 October 2026. When checking a reusable workflow after an update, verify which skill file it will use. A personal skill and a repository skill can both be named weekly-brief. The current authoring guide says same-name skills are not merged and both can appear in selectors. This is documented discovery behavior, not a newly announced merging feature.
Identify the intended file
Check the path shown in the available-skill list. Open the relevant SKILL.md and compare its purpose, required inputs and output location with the current task. A repository-specific procedure may be appropriate for one checkout and unsuitable elsewhere.
For a small check, give two harmless sample skills different output labels, such as “project draft” and “personal draft”. Explicitly select the intended one, then inspect the saved result and the reported skill path. This is a proposed check, not evidence that any installed skills were run here.
Remove ambiguity in the names
When you maintain both skills, choose names and descriptions that expose their different jobs. Rename a skill through the product’s documented authoring process and keep its metadata and folder consistent. Do not delete another person’s repository skill just to simplify your picker. A clearer label helps selection; it does not replace reading the actual instructions.