Docs Codex skills
Use Edge and install skills in Codex
Add Edge to Codex MCP configuration and start a new chat. Edge can find and load task instructions without permanently copying a skill. For persistent local skills, keep a reviewed skill folder in .agents/skills in the repository or ~/.agents/skills for your user, with SKILL.md and its supporting files together.
No skill to install: Edge loads the right one per task.
Where can I find skills for Codex?
Codex CLI reads skills from .agents/skills in your repository and ~/.agents/skills for your user. Add curated ones with $skill-installer, any public skill with npx skills add owner/repo, or connect Edge so Codex searches the public catalog mid-task and loads a screened skill without installing it.
Checked 2 October 2026 against OpenAI's skills documentation. Edge is our product.
| Way | How it works | Best for |
|---|---|---|
| Built-in and curated | System skills ship with Codex; $skill-installer adds curated skills from openai/skills or another repo | You know the skill, and it is in OpenAI's set |
| Plugins | Skills and connectors from the plugin directory shared by ChatGPT and Codex | Packaged workflows with connectors |
| skills.sh | npx skills add owner/repo installs any public skill, with Codex as a target | Popular open skills by name |
| Agensi | A Codex CLI store of free and paid creator skills | Paid business workflows |
| Edge | MCP connector: Codex searches 254,734 public skills by task and loads a screened one for this task only | You do not know which skill fits |
Edge setup for Codex is one command: Edge setup for Codex. Prefer to let Codex do it? Give Codex Set up Edge for me: fetch https://getedge.cc/SKILL.md with curl, read it, and follow it and it configures itself. Before you keep any skill, read are agent skills safe. Comparing sources? See skills.sh alternatives.
Codex skills: common questions
How do I install a skill in Codex CLI?
Put the skill folder, with its SKILL.md and supporting files, in .agents/skills in your repository or ~/.agents/skills for your user. Codex detects new skills automatically; restart Codex if one does not appear. For OpenAI's curated skills, run $skill-installer inside Codex.
Why does Codex not see Edge in the first chat?
Codex waits 1 second for MCP servers that are still starting, and an npx start takes longer. npx -y @getedge/mcp@0.6.58 setup codex puts mcp_optional_startup_grace_ms = 10000 at the top of ~/.codex/config.toml for you; by hand, add that line yourself.
What are the best skills for Codex?
The best skill is the one that fits your task. Edge ranks public skills by fit for the task Codex is working on, which is why it searches at the moment of the task instead of from a fixed list.
How do I connect Edge?
Follow Edge setup for Codex: run one command in your terminal, then open a new chat.
Pro: after setup, add EDGE_KEY = "edge_YOUR_KEY" to the [mcp_servers.edge.env] table in that file.
Undo it with npx -y @getedge/mcp@0.6.58 setup codex --remove. Free setup uses no Edge key. Read Edge setup for plans and data handling.
Can I add the config by hand?
Yes. Put the block in ~/.codex/config.toml, replacing any existing [mcp_servers.edge] table and preserving other server entries. Keep its first line, mcp_optional_startup_grace_ms = 10000, on its own line at the top of the file, above the first [section]: Codex otherwise waits only 1 second for MCP servers that are still starting when the first message is sent, and an npx start takes longer, so the first chat misses Edge. Run codex mcp get edge.
mcp_optional_startup_grace_ms = 10000 [mcp_servers.edge] command = "npx" args = ["-y", "@getedge/mcp"] omit_tools_from = ["deferred", "code_mode"] startup_timeout_sec = 30
Then run npx -y @getedge/mcp --version once and wait for the version number, so the package is downloaded before the first chat. Adding Edge with a bare codex mcp add leaves Edge's tools deferred and the startup wait at 1 second, so Codex usually never sees Edge; use the setup command or the block above.
Where do I keep a skill?
.agents/skills/my-skill/SKILL.md or ~/.agents/skills/my-skill/SKILL.md
Repository skill discovery walks from the working directory to the repository root. The omit_tools_from line exposes Edge’s tools directly in clients that defer MCP tools. It is recommended for this setup, rather than required for the MCP connection.
Review a skill before adding it. Preserve its whole folder, including scripts, references and assets. Follow the skill selection guide to check its exact source and requirements.
How do I check that setup works?
Ask: Use Edge to find a skill for my task, show its source, and load it if it fits. Confirm an actual find_skill and use_skill result. Then try one small task and inspect the output. A visible configuration entry confirms setup syntax; it does not prove that a skill improves the result.
Sources, method and limits
Edge is our product. Checked 2026-10-02. The latest npm connector returned find_skill results. Codex CLI 0.154.0 called the local Edge tool with omit_tools_from configured; without it, the local tool was not directly available in the tested session. This checks connectivity and exposure, not how often an agent chooses Edge. This guide uses client documentation and Edge setup instructions, without performance scores.