$skill-creator instructs codex to run package_skill.py. Codex gets confused because it doesn't exist.
What version of Codex is running?
.92.0
What subscription do you have?
Plus & Business
Which model were you using?
gpt-5.2-codex-high
What platform is your computer?
Darwin 25.2.0 arm64 arm
What terminal emulator and version are you using (if applicable)?
VS Code
What issue are you seeing?
codex-rs/core/src/skills/assets/samples/skill-creator/SKILL.md
^ This tells codex python scripts it doesn't appear to be able to use.
I’m planning to create a concise SKILL.md with frontmatter and usage instructions, referencing a separate config file stored in references for clarity. Next, I’ll locate init_skill.py within /.codex/skills to run it
with these resources.
user prefers otherwise and craft a concise SKILL.md with basic frontmatter and a focused description including triggers and MCP server mention.
Drafting skill instructions and preparing for escalated directory creation
I'm outlining a concise skill README with quick start, tool map, workflow, config, and troubleshooting sections, plus a references file summarizing user-provided options while keeping ASCII-only. Next, I'll request
permission to create the skill directory with escalated exec_command including justification.
✔ You approved codex to run cat <<'EOF' > /Users/npearce/.codex/skills/chrome-devtools-mcp/references/chr... this time
• Ran cat <<'EOF' > /Users/npearce/.codex/skills/chrome-devtools-mcp/references/chrome-devtools-mcp.md
│ # Chrome DevTools MCP Reference
│
│ … +88 lines
└ (no output)
• Created the skill at /.codex/skills/chrome-devtools-mcp with SKILL.md and reference files. Initialization and packaging scripts were not found, so packaging wasn’t performed. Next steps: 1) run packaging if scripts
become available; 2) try using the skill with your prompt; 3) update the SKILL.md description or skill name if desired. Let me know if you want to rename or adjust anything.
What steps can reproduce the bug?
Uploaded thread: 019c106a-251a-77e0-9ab0-418fc765b0e6
What is the expected behavior?
_No response_
Additional information
_No response_
2 Comments
Works fine if I tell it the full path. Codex said it searched .codex/skills & .codex but not ~/.codex/skills/.system/skill-creator/scripts/
This what I was told when I asked:
› where did you look for scripts/init_skill.py?
• I searched with rg --files -g 'init_skill.py' /home/zbynek and then rg --files -g 'init_skill.py' /home/zbynek/.codex. Both returned nothing. If it lives elsewhere, tell me the path and I can use it next time.
› it lives in /home/zbynek/.codex but since it is a system skill, it is hidden in hidden directory .system which is by default ignored by rg
• I'm apologizing for the interruption and offering to rerun the task or regenerate it using the init script based on the user's preference.
• Got it — thanks for the correction. I missed that because rg skips hidden directories by default. If you want, I can re‑initialize the skill using /home/zbynek/.codex/skills/.system/skill-creator/scripts/init_skill.py and migrate what I already created into the generated structure. Just say the word.
----
So it seems it got confused by its own file layout. I suppose that it should know from where the skill was loaded and just look there and not go looking for it blindly everywhere.