PlugWiki

workers-profiling skill (Cloudflare) for Claude: find slow code in Workers

Makes your agent capture and read CPU or memory profiles of a deployed Cloudflare Worker, then suggest the smallest fix. For Workers developers.

Installs
18K
on skills.sh
Stars
3.2K
on GitHub
Files
1
besides SKILL.md
Updated
Oct 2026
last repo commit

workers-profiling makes your agent find expensive functions or memory allocations in deployed Cloudflare Workers and Durable Objects. It confirms the account, Worker, environment and version with you, picks CPU or heap profiling, captures a profile, reads the pprof file for hotspots, and proposes the smallest code change.

It loads when you ask to profile or debug CPU or memory in a deployed Worker. Where possible it uses the cf command line to capture profiles, and offers to install it if missing. It first reads Cloudflare's production profiling guide, so it needs internet access.

Good for

  • Developers chasing high CPU use or latency in a deployed Worker
  • Teams debugging memory growth in a Durable Object
  • Anyone already using the cf command line on Cloudflare

Install workers-profiling

Claude Code

  1. 1

    Copy this prompt.

    Install the workers-profiling skill in Claude Code. Run this command:
    
    npx skills add https://github.com/cloudflare/skills --skill workers-profiling
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

Profile or debug CPU usage and memory allocation in deployed Cloudflare Workers and Durable Objects. Then use this information to optimize your code.

Sections in SKILL.md

  1. Retrieve the docs
  2. Profiling steps
  3. Inspect the evidence
  4. Optimise
  5. Report findings
  6. Skill feedback

Key facts

License
Apache-2.0
Installs on skills.sh
17,969 (Nov 2, 2026)
Last commit
Oct 31, 2026

What it includes

  • Read the production profiling guide first

    Loads Cloudflare's Workers profiling-in-production guide so the agent knows how profiling works.

    Network · Retrieve the docs

  • Confirm what to profile and which type

    Identifies the symptom, then confirms the account, Worker, environment and deployed version with you. For Durable Objects it also confirms the namespace and instance. Then it chooses CPU or heap profiling.

    Try: “Profile CPU usage on my deployed Worker api-gateway in production.”

    Profiling steps

  • Use the cf CLI to get a profile

    Checks the installed version's help and schema if you ask for cf, and asks before installing it if it is missing.

    Runs code · Capture with cf

  • Read the pprof file for hotspots

    Maps hotspots to functions and source locations, and suggests enabling source maps if names point at generated JavaScript.

    Files · Inspect the evidence

  • Propose the smallest supported change

    Suggests the smallest code change that the capture supports.

    Optimise

  • Evidence, change and how to check it

    A short report with file, function, location and metric for each finding, plus how to verify the change.

    Report findings

  • Optionally file a public GitHub issue

    If you say the skill was wrong, outdated or missing something, it reads references/skill-feedback.md. It asks permission, drafts the issue, shows you the exact text and posts only after you answer yes.

    Write · Skill feedback

From the official docs

Permissions

Low risk

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It can post a public GitHub issue

    After you say the skill was wrong or outdated, skill-feedback.md has the agent ask permission, draft an issue, show you the exact title and body, and run something like gh issue create --repo cloudflare/skills only after you answer yes. It tells the agent to leave out secrets, account IDs, hostnames and private code. Check the draft anyway. github.com

  • It may run cf against your deployed Worker

    Profile capture runs against deployed code and may ask to install the cf CLI. Confirm the account and Worker name it states before approving. github.com

Technical details
Talks todevelopers.cloudflare.com docs. Cloudflare APIs through cf. GitHub, only if you approve a feedback issue
Sign-in and keysSKILL.md does not describe credentials or where cf keeps them.
Scopes
  • Cloudflare account access through the cf CLI (SKILL.md does not say how it signs in)

Questions

What does the workers-profiling skill do?

It guides your agent through profiling a deployed Cloudflare Worker or Durable Object for CPU use or memory growth. It captures a profile, finds the hotspots and suggests the smallest fix.

How do I install it in Claude Code, the Claude app or Codex?

Use the install box above. The Cloudflare skills README documents plugin installs for Claude Code and Codex, a skills CLI install of the whole repository, and copying skill folders. It does not document a Claude app upload.

Does it need an API key?

SKILL.md names no key. It uses the cf command line to capture profiles against your deployed Worker, and it does not say how cf signs in, so check the cf docs for that. It also reads Cloudflare's docs over the internet.

Is it safe to install?

It bundles no scripts. The agent may run the cf CLI against your deployed Worker and offer to install it. A feedback file can also post a public GitHub issue, but only after you approve the exact text.

Can it post to GitHub without asking?

No. Its feedback file says to ask permission first, show you the exact title and body, and post only after you answer yes. It says never to include secrets, account IDs or private code.

Does it profile local dev Workers?

The skill is written for deployed code. It names deployed Workers and Durable Objects, and confirms the deployed version with you.

Does the Cloudflare plugin add more than this skill?

Yes. The README says the native plugin installs both Cloudflare guidance and the Cloudflare MCP server, which gives the agent access to the Cloudflare API. Installing only this skill through the skills CLI gives you the skill alone.

Information

updated Nov 2, 2026

Folder
skills/workers-profiling

cloudflare/skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 3
  1. workers-profiling SKILL.md · github.com
  2. workers-profiling skill-feedback.md · github.com
  3. cloudflare/skills README · github.com

Updated Nov 2, 2026.