Skip to content
TrustedSkillsbeta
Back to all skills

Cloudflare Deploy

Listed
davila7·vlatest·cloud·MIT

Helps with Cloudflare, deployment as part of deploying and managing cloud infrastructure workflows.

Repository

Install on your platform

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

  1. 1

    Run this in your project

    terminal
    $ npx skills add davila7/claude-code-templates --skill cloudflare-deploy -a claude-code

  2. 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

davila7

Taken from the source listing. We haven't verified who controls this account.

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

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: api.cloudflare.com, gateway.ai.cloudflare.com.

    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.

    Hosts contacted

    api.cloudflare.comundeclaredgateway.ai.cloudflare.comundeclared

    What it found (3 of 14)

    • cli-tool/components/skills/development/cloudflare-deploy/references/ai-gateway/configuration.md:10contacts api.cloudflare.com
      curl -X POST https://api.cloudflare.com/client/v4/accounts/{account_id}/ai-gateway/gateways \
    • cli-tool/components/skills/development/cloudflare-deploy/references/ai-gateway/configuration.md:73contacts api.cloudflare.com
      curl https://api.cloudflare.com/client/v4/accounts/{account_id}/ai-gateway/gateways \
    • cli-tool/components/skills/development/cloudflare-deploy/references/ai-search/api.md:82contacts api.cloudflare.com
      curl https://api.cloudflare.com/client/v4/accounts/{ACCOUNT_ID}/autorag/rags/{NAME}/ai-search \

  • 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 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 davila7/claude-code-templates at 79182c51fb.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
79182c51fb
Manifest
cli-tool/components/skills/development/cloudflare-deploy/SKILL.md
Scanned
60 files, 6,908 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

cloudflare-deploy

What it does

This skill enables AI agents to deploy applications directly to Cloudflare's global network using the wrangler CLI. It automates the process of uploading assets, configuring domains, and managing environment variables for serverless functions and static sites.

When to use it

  • You need to rapidly prototype serverless functions (Workers) without setting up a local development environment.
  • Your team requires an automated pipeline to push code changes directly from version control or CI/CD triggers to production.
  • You are managing multiple environments (e.g., dev, staging, prod) and need consistent deployment configurations across them.

Key capabilities

  • Asset Upload: Automatically uploads static assets like HTML, CSS, JavaScript, and images to Cloudflare Pages.
  • Worker Deployment: Deploys and updates Cloudflare Workers with specific environment settings.
  • Configuration Management: Handles wrangler.toml configurations, including route definitions and compatibility flags.
  • Authentication Integration: Manages API tokens required for secure deployment operations.

Example prompts

  • "Deploy my static site to Cloudflare Pages using the current directory contents and update the production environment."
  • "Update the api-handler Worker with the latest code from the repository and set the STAGE variable to 'production'."
  • "Configure a new route for my domain on Cloudflare Workers and deploy the associated script."

Tips & gotchas

Ensure your wrangler.toml file is correctly configured with valid API tokens before attempting deployment, as missing credentials will cause immediate failure. This skill relies on the underlying wrangler CLI functionality; ensure your agent has access to the necessary network permissions to reach Cloudflare's endpoints.