Cloudflare Skills: Agent Skills for Workers, Durable Objects, and the Agents SDK

What Cloudflare Skills Solves for Platform Developers

AI coding tools can generate plausible-looking but incorrect Cloudflare Workers code, especially for platform-specific APIs like Durable Objects, the Agents SDK, and wrangler configuration. The root cause is that these tools have general knowledge but no mechanism for loading authoritative, up-to-date Cloudflare platform guidance at the moment it is needed.

Agent Skills is a standard developed by Anthropic for equipping AI agents with packaged, contextual guidance. The cloudflare/skills repository implements that standard for the Cloudflare developer platform. When a developer asks a question that triggers one of the configured skills, the agent automatically loads the relevant skill text and applies it.

The repository is published and maintained by Cloudflare. The last push was on 2026-09-21, and it is not archived. There are no tagged releases: the project is distributed through the plugin marketplaces of each supported agent tool rather than through versioned releases.

Skills Included and What Each One Covers

The repository provides fourteen named skills. The cloudflare skill is the entry point: it helps agents discover which Cloudflare products are relevant to a request and routes to the appropriate skill. The agents-sdk skill covers building stateful AI agents with state management, scheduling, RPC, MCP servers, email, and streaming chat. The durable-objects skill covers stateful coordination use cases such as chat rooms, games, and booking systems, including RPC, SQLite storage, alarms, and WebSockets.

Two sandbox skills exist: sandbox-next covers the preview release of @cloudflare/sandbox@next and is described as recommended for new projects, while sandbox-stable covers the current stable @cloudflare/sandbox package. A third skill, sandbox-migrate-to-next, handles porting a stable Sandbox app to the preview API. The wrangler skill covers deploying and managing Workers, KV, R2, D1, Vectorize, Queues, and Workflows. The workers-best-practices skill covers writing, reviewing, and configuring production Workers.

Other skills in the collection include cloudflare-email-service for email sending, routing, and delivery configuration; turnstile-spin for bot verification; web-perf for auditing Core Web Vitals; cloudflare-one for designing and configuring Access, Gateway, WARP, and Magic WAN deployments; and cloudflare-one-migrations for assessments and rollout plans when migrating from Zscaler, Palo Alto, or legacy VPN solutions to Cloudflare One.

The nextjs-on-cloudflare skill specifically covers running Next.js on Workers using the vinext adapter.

Installing Cloudflare Skills in Claude Code, Codex, and Cursor

Installation differs by agent tool. For Claude Code, the README gives two commands:

/plugin marketplace add cloudflare/skills
/plugin install cloudflare@cloudflare

For OpenAI Codex, the equivalent is:

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

After installation, start a new Codex session for the plugin to take effect. For Cursor, install from the Cursor Marketplace or add it manually through Settings, then Rules, then Add Rule, then Remote Rule (Github), entering cloudflare/skills as the source.

For VS Code and GitHub Copilot, the README instructs enabling `chat.plugins.enabled` in VS Code settings, then opening the Command Palette and running Chat: Install Plugin From Source, entering the repository URL.

A cross-tool installation path uses the npx skills CLI:

npx skills add https://github.com/cloudflare/skills

For tools not covered by a marketplace, the README provides a manual clone and copy path. Skills live in a tool-specific directory: `~/.claude/skills/` for Claude Code, `~/.cursor/skills/` for Cursor, `~/.config/opencode/skills/` for OpenCode, and `~/.codex/skills/` for Codex.

How Auto-Loading Works and What to Expect at Runtime

Skills in this collection are contextual. The README states that skills are auto-loaded based on the conversation. When a request matches a skill's triggers, the agent loads and applies the relevant skill text. A developer asking about Durable Objects will trigger the durable-objects skill; a developer asking about deploying a Worker will trigger the wrangler skill.

This means the developer does not need to name the skill explicitly. The matching happens inside the agent tool's skill-loading mechanism, not by any code in this repository. The repository provides the skill text and trigger configuration; the agent tool decides when to load it.

The plugin also bundles Cloudflare's main remote MCP server, which the README describes as providing access to the Cloudflare API and current developer documentation through the Code Mode MCP server. Cloudflare publishes additional product-specific MCP servers, but the repository intentionally includes only the main cloudflare MCP server and leaves the others for manual addition.

Limitations and When to Use the Documentation Directly

Cloudflare Skills is only useful if the developer's tool supports the Agent Skills standard. The README lists Claude Code, Cursor, OpenAI Codex, VS Code with Copilot, OpenCode, and Pi as supported tools. Tools that do not support the standard cannot load the skills, regardless of how they are installed.

The skills provide guidance text, not runtime enforcement. They improve the agent's responses by supplying accurate platform context, but they do not guarantee that the generated code is correct. The underlying agent model still makes decisions; the skill shifts the probability distribution of those decisions toward correct Cloudflare-specific patterns.

For developers who work primarily with one Cloudflare product and want the most precise guidance, reading the Cloudflare developer documentation at developers.cloudflare.com directly may be more reliable than relying on a skill that packages a summary of that documentation. The skill approach trades coverage and convenience for depth.

The repository has no GitHub releases, so there is no versioned changelog. Changes to skill text are tracked through commit history on the main branch.

Repository Structure and the MCP Configuration

The repository top level includes separate directories for each supported agent tool's plugin format: .claude-plugin/, .codex-plugin/, and .cursor-plugin/. A skills/ directory holds the individual skill files. A rules/ directory holds rules files. The .mcp.json and mcp.json files configure the bundled MCP server.

The plugin.json file at the root describes the plugin to marketplaces. The .agents/ directory is present, consistent with projects that use Claude Code's agent configuration features.

The repository is licensed under Apache-2.0. The CONTRIBUTING.md and CODEOWNERS files indicate that Cloudflare engineers maintain ownership of the content, though the repository is open source and accepts external contributions.

The icon.png and logo.svg files in the root are used by plugin marketplaces to display the plugin's branding. The .github/ directory contains CI configuration. There are no test files in the repository: the skills are plain text and shell fragments, so correctness is verified by the Cloudflare team rather than by automated tests against a test runner.

Editorial conclusion

Cloudflare Skills is useful for any developer who builds regularly on Cloudflare Workers or the Agents SDK and works inside an AI coding tool that supports the Agent Skills standard. It is not useful if your agent tool does not support that standard, or if your work does not touch the Cloudflare platform. The repository has no releases: the primary delivery mechanism is the plugin marketplaces of each supported agent tool.

Frequently asked questions

Official sources

1. cloudflare/skills on GitHub
2. Issues
3. License: Apache-2.0
4. README