Install Cloudflare Skills in Codex with the official plugin

Who it's for

This guide is for developers who want to build on Cloudflare, Workers, the Agents SDK, and the wider Cloudflare Developer Platform, and want an Agent to load the official Agent Skills.

The primary path is the native plugin. The page states: where supported, use the native plugin to install both Cloudflare guidance and the Cloudflare MCP server; Agents that only support the Agent Skills standard can install skills separately. The first try uses only the official Codex plugin commands as written; do not place a second “skills-only” path beside them when that command is not given.

Skills are contextual and auto-loaded from the conversation: when a request matches a skill’s triggers, the Agent loads and applies the relevant skill. The plugin also includes Cloudflare’s main remote MCP server for enhanced functionality. The first question should only be a check; do not call operations that would change a live Worker or account resources.

Complete a first try in 3 minutes

Use only the recommended install path given on the page (run the two commands in order):

codex plugin marketplace add cloudflare/skills
codex plugin add cloudflare@cloudflare

Precondition: you are currently in a Codex environment that supports this native plugin. The install location is written by these two codex plugin commands into Codex’s marketplace and plugin list; do not rewrite them as npx or another marketplace command that does not appear.

Side-effect confirmation point: the first command adds the marketplace, the second installs the cloudflare@cloudflare plugin; the plugin includes a remote MCP server. If this is not the Codex environment you intend to change, stop first. Confirm, then run them.

Success signal: both commands finish normally, and Codex can see the plugin or Cloudflare-related skills. Then ask only one question that can trigger a skill without changing resources, for example how to understand an existing Workers project structure. It is enough to see the Agent auto-load the relevant skill and give guidance. If it is about to change an account or deploy through MCP, stop at the confirmation point.

Use cases

Case 1: Install the plugin in Codex in the official order. First run codex plugin marketplace add cloudflare/skills, then run codex plugin add cloudflare@cloudflare. The evidence covers exactly these two lines. The completion criterion stops at a successful plugin install. Do not add a separate skills-install command that does not appear.

Case 2: After install, trigger skills from conversation rather than naming a slash command that is not given. The page states skills auto-load from conversation and apply when triggers match; the plugin includes the main remote MCP server for enhanced functionality. The excerpt does not list specific trigger words or MCP tool names, so the first time only ask a read-only question related to Cloudflare / Workers / Agents SDK. The observable success signal is that the Agent loads a skill and gives platform-specific guidance. Do not write “install skills separately” as if a second official command already existed.

Limits

The primary install path is only the two Codex plugin commands above. Hosts that only support the Agent Skills standard can install skills separately, but this page’s excerpt does not give that command, so do not invent it. Skills auto-load; the MCP server enhances functionality and therefore may reach remote capabilities. The listed platform range cannot be generalized to an installer that does not appear. Uninstall and specific triggers are not written and cannot be treated as a safety conclusion.