Add Codex integration and installer support#73
Add Codex integration and installer support#73artile wants to merge 1 commit intomsitarzewski:mainfrom
Conversation
msitarzewski
left a comment
There was a problem hiding this comment.
Great to see Codex support! We definitely want this integration.
To keep things consistent with how we handle other tools, we'd like to see this wired into the conversion/install pipeline rather than pre-generated files checked into the repo. This keeps the repo lightweight and ensures Codex files stay in sync when agents are added or updated.
Here's the pattern (same as Cursor, Aider, Windsurf, etc.):
- Add a
convert_codex()function toscripts/convert.sh— reads agent.mdfiles and outputs Codex-format files tointegrations/codex/ - Add an
install_codex()function toscripts/install.sh— copies generated files to the right location - Remove the pre-generated files — they'll be regenerated on demand via
./scripts/convert.sh --tool codex
Take a look at convert_cursor() or convert_opencode() in scripts/convert.sh for examples of the pattern. Each converter reads the YAML frontmatter + body and outputs the tool-specific format.
End result for users:
./scripts/convert.sh --tool codex
./scripts/install.sh --tool codexHappy to help if you have questions about the structure!
|
Hey @artile — the Codex integration approach is solid, and the convert.sh + install.sh additions are well-structured. However, the 92 pre-generated skill files in Could you update the PR to:
Users run |
Summary
codexintegrations/codex/skill package and refresh multi-tool docsVerification
bash -n scripts/convert.sh scripts/install.sh./scripts/convert.sh --tool codex./scripts/install.sh --tool codex