Workers Best Practices

Name: Workers Best Practices
Author: cloudflare

Official

cloudflare·vlatest·cloud·Apache-2.0

Provides Cloudflare workers with optimized code snippets and configuration examples based on best practices.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add cloudflare/skills --skill workers-best-practices -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

cloudflare

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 19 Oct 2026

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned cloudflare/skills at 86505e44f8.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 86505e44f8
Manifest: skills/workers-best-practices/SKILL.md
Scanned: 4 files, 535 lines

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

The workers-best-practices skill provides guidance on optimizing and effectively using Cloudflare Workers, including performance tuning, security practices, and efficient code structure.

When to use it

When deploying a new Worker and looking for optimization strategies.
When encountering performance bottlenecks in existing Workers.
When aiming to follow secure coding standards for serverless functions.
When seeking best practices for managing multiple Workers or scaling applications.

Key capabilities

Performance optimization techniques for Cloudflare Workers
Security recommendations for handling sensitive data and requests
Code structure and modularization strategies
Deployment and management best practices

Example prompts

"How can I optimize the performance of my Cloudflare Worker?"
"What are the security best practices when using Cloudflare Workers?"
"Can you provide guidelines on organizing multiple Cloudflare Workers efficiently?"

Tips & gotchas

Ensure your environment is set up with Cloudflare's CLI or dashboard for full functionality.
Best practices may vary based on specific use cases, so review documentation alongside this skill for tailored advice.