Index of every page on this site: llms.txt
All skills
cloudflare avatar

/cloudflare-one

@5108325 official
by cloudflarecloudflare/skills3.4k stars
357
Run it yourself

Design, configure, troubleshoot, or review Cloudflare One Zero Trust and SASE deployments. Use cloudflare-one-migrations for migration planning from other vendors. Also use when an agent, script, crawler, or other non-browser client needs to reach a webpage or API protected by Cloudflare Access.

Use this Skill: https://skilld.dev/gh/cloudflare/skills/cloudflare-one

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesskill-feedback.md

≈700 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Skill feedback

GitHub issues are public: anyone can read an issue once it is posted. Never include sensitive information, and never post an issue until the user has seen the exact title and body and approved it.

Use this when the user reports that the cloudflare-one skill gave incorrect or outdated guidance, is missing information, or could be improved. This is about the skill (agent instructions), not about Cloudflare products.

What not to include

The issue is drafted from the conversation, so remove the following before drafting and describe the problem in general terms instead:

  • Credentials, API tokens, secrets, and passwords
  • Account IDs, zone IDs, and other resource identifiers
  • Customer or personal data, such as names, email addresses, and IP addresses
  • Internal hostnames and URLs
  • Private code, configuration, and logs

Steps

  1. Ask permission – Ask the user if they would like to submit feedback to the skill maintainers. If they decline, move on.

  2. Draft the issue – Fill in the table below from the conversation and use it as the issue body. Always identify which specific file and section caused the problem. Leave out everything listed in What not to include.

  3. Review with the user – Show the user the exact title and body, then ask a yes/no question, such as "Post this as a public issue on cloudflare/skills?" Submit only after the user answers yes. If they ask for changes, apply them and ask again. If they answer no, do not post. Agreeing to send feedback in step 1 is not approval of the text.

  4. Submit – Create a GitHub issue on the cloudflare/skills repository with the approved draft as the body, for example with gh issue create --repo cloudflare/skills. The title must follow this format: skill-feedback: cloudflare-one: <summary of the problem>.

  5. Share the result – Share the issue URL with the user after submission. If submission fails, give the user the approved title and body, and this link to create the issue manually: https://github.com/cloudflare/skills/issues/new

Issue body

Field Value
Type bug (incorrect guidance), outdated, missing, or improvement
Skill cloudflare-one
Source File and section, e.g. SKILL.md > "Section name" or references/<file>.md > "Section name"
Agent The agent and model in use, if known
Task What the user was trying to do, e.g. "deploy a preview"
Expected What should have happened, e.g. "Create a Preview deployment"
Actual What the skill said or what happened, e.g. "Unknown option: --preview"
Impact The effect on the user, e.g. "Time spent finding the correct syntax"
Suggested fix How the skill should change; leave blank if unsure

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts12d3 checks · Risk SAFE
  • Gen Agent Trust Hub14d

    This skill provides configuration and troubleshooting guidance for Cloudflare One. It includes security best practices such as instruction to read credentials from secret stores rather than exposing them and emphasizes human approval for public feedback. No security issues were detected.

  • Socket12d

    No alerts

  • Snyk14d

    Risk: LOW · No issues

Signed by skilld at 5108325. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 days ago.

Activeupdated 2 weeks ago
  • cloudflare
  • zero-trust
  • access
  • gateway
  • warp
  • tunnel
  • dlp
  • casb
  • device-posture
  • sase

README badge

README badge for cloudflare/skills/cloudflare-one

Guides design, configuration, troubleshooting, and review of Cloudflare One Zero Trust deployments including Access, Gateway, WARP, Tunnel, DLP, CASB, and device posture. The skill prioritizes current Cloudflare docs and API schemas over embedded knowledge, then assesses architecture, identity, connectivity, and rollout constraints before proposing changes. Targets operators managing multi-product Cloudflare One stacks across offices, data centers, and remote users.

Generated from the current SKILL.md.

Does this skill work with all Cloudflare One products?
Yes. The skill covers Access, Gateway, WARP, Tunnel, Cloudflare WAN, DLP, CASB, device posture, and identity federation. It retrieves current docs and API schemas rather than relying on embedded product knowledge.
Can this skill make changes to my Cloudflare One account?
The skill can propose changes with prerequisites and rollback plans, but it requires account access to inspect existing resources before making any changes. It recommends staging risky changes as disabled or scoped to pilot groups unless you explicitly request wider rollout.
What should I provide when asking for help with Cloudflare One?
Provide context about your architecture: sites, users, applications, connectivity model, identity provider, compliance constraints, and current security stack. The skill will ask clarifying questions based on your task (architecture, configuration, troubleshooting, migration, or review).
Does this skill handle private hostname resolution?
Yes. The skill understands that creating an Access app alone is not enough for private hostnames—you must also configure DNS routing via resolver policies and ensure the connector can reach the origin.
Can this skill help with device client enrollment and profiles?
Yes. The skill covers enrollment rules (Access applications of type warp), device profiles, split tunnel modes, and headless device authentication with service tokens.

Generated from the current SKILL.md. These answers refresh after source changes.