[FEATURE] Allow disabling built-in skills via config.toml
What feature would you like to see?
A setting in config.toml to disable built-in skills (e.g. Skill Creator).
Currently, there is no way to opt out of built-in skills that ship with Codex. If a user has their own custom skill that covers the same domain (e.g. a custom skill creator), the built-in one still gets loaded and competes for activation, wasting context and sometimes triggering instead of the user's preferred skill.
A config.toml option like this would solve it:
[[skills.config]]
name = "Skill Creator"
enabled = falseOr alternatively a top-level list:
[skills]
disabled_builtins = ["Skill Creator"]This would let users curate exactly which skills are active, avoiding conflicts with custom skills that serve the same purpose.
Additional information
Related but distinct from #14161 (sub-agent [[skills.config]] overrides being ignored) — that issue is about per-agent overrides for custom skills. This request is about globally disabling built-in skills that ship with Codex itself.
5 Comments
lol google already says this exists, looks like gemini doesnt care if its a feature request or existing fact :D
You can use this as a workaround:
Yes please I would love this to exist, it's so annoying seeing millions of skills that you don't care about! I simply cannot believe this is actually how it works and barely anyone is complaining about it.
[[skills.config]] enabled = falseis implemented.@etraut-openai to confirm, the correct way to disable it is like this, right?
The
pathis required - you can't just write[[skills.config]] enabled = false