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

/cloudflare-one-migrations

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

Assess and plan migrations from existing VPN, SWG, or SASE platforms to Cloudflare One, including policy mapping, parity gaps, and rollout.

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

referencesskill-feedback.md

≈708 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-migrations 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-migrations: <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-migrations
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 alerts23d3 checks · Risk SAFE
  • Gen Agent Trust Hub23d

    This skill provides structured guidance for migrating network security configurations from third-party vendors to Cloudflare One. It includes a potential security consideration regarding the ingestion of external configuration data, which is inherent to its intended purpose as an assessment tool. No malicious patterns or security risks were identified.

  • Socket23d

    No alerts

  • Snyk23d

    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 4 weeks ago
  • cloudflare
  • cloudflare-one
  • migration
  • zscaler
  • palo-alto
  • vpn
  • gateway
  • access
  • network-security
  • sase

README badge

README badge for cloudflare/skills/cloudflare-one-migrations

Plans migrations from Zscaler ZIA/ZPA, Palo Alto, legacy VPN, or other security stacks to Cloudflare One by mapping source policies to Gateway traffic policies, Access applications, Tunnel routes, and identity/DLP configuration. Covers migration assessment, object inventory, dependency ordering, rollout staging, and source-specific mapping traps for each vendor to account for every rule with explicit unsupported/partial decisions.

Generated from the current SKILL.md.

Does this skill handle migrations from all major security vendors?
The skill covers Zscaler ZIA/ZPA, Palo Alto NGFW/Prisma/GlobalProtect, and legacy VPN/SWG/SD-WAN stacks. Other vendors are out of scope unless explicitly mapped in the migration assessment prompts.
What exports do I need to provide before the skill can generate a mapping plan?
You must provide structured exports (not screenshots) from the source stack: for ZIA, URL filtering and firewall rules; for ZPA, app segments and access policies; for Palo Alto, security rules and address/service objects. The skill requires object definitions, not just rule summaries, to resolve dependencies.
Does this skill automate the actual policy creation in Cloudflare One?
No. The skill generates a mapping plan, inventory, and gap analysis. You must manually create Cloudflare resources (Access apps, Gateway policies, tunnels) and configure split-tunnel bypass and egress IPs through the dashboard—these cannot be fully automated.
How does the skill handle rules with no exact Cloudflare equivalent?
The skill marks mappings as partial, unsupported, or manual-review rather than forcing false equivalence. Examples include Zscaler caution/warn behavior, Palo Alto App-ID logic, and custom DLP regex—these are flagged as explicit customer decision points.
Does the skill require SCIM and identity synchronization?
SCIM/group sync is a gating prerequisite for group-scoped policies. Without it, identity-scoped source rules become overly broad unless you use alternative selectors like user/email lists or Gateway identity selectors.

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