agentleFS
Sign inStart free
mazze93mazze93/claude-code-skills/skills/cloudflare-one/SKILL.md

cloudflare-one

Skill1 starsChanged 11 days agoMITView on GitHub

Cloudflare One Zero Trust / SASE: Access, Gateway, WARP, Tunnel, WAN, DLP, CASB, device posture, identity — design, configure, troubleshoot, review, and migrate from Zscaler/Palo Alto/legacy VPN. Retrieval-first: use current Cloudflare docs over embedded knowledge.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use sandbox-sdk, remotion-maps and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenAISkill

    sandbox-sdk

    Build sandboxed applications for secure code execution. Load when building AI code execution, code interpreters, CI/CD systems, interactive dev environments, or executing untrusted code. Covers Sandbox SDK lifecycle, commands, files, code interpreter, and preview URLs. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.

    Also in 11 projects that use this

  • OpenAISkill

    remotion-maps

    Remotion Map animation knowledge

    Also in 4 projects that use this

  • LangChainSkill

    hyperframes-audio

    Use when audio already placed in a HyperFrames composition needs to be mixed: fade-in/fade-out, crossfade, track gain or volume, volume automation, ducking, a music bed that fights a voiceover (voiceover carve), effects on a track (EQ, compressor, limiter, gate, saturation, delay, reverb, chorus, phaser, bitcrush), automation envelopes drawn on a track's volume or any effect parameter, or one submix bus carrying a chain, a fader and an automation clock for several tracks at once (`<hf-audio-group>`). Don't use for sourcing or generating audio — finding BGM, SFX, or making a voiceover is `/media-use`. Don't use for clip timing or track layout, which is `/hyperframes-core`.

    Also in 3 projects that use this

  • AWSSkill

    wizard

    Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

    Also in 4 projects that use this

  • AnasX7Skill

    design-taste-frontend

    Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

    Also in 4 projects that use this

  • VercelSkill

    remotion-best-practices

    Best practices for Remotion - Video creation in React

    Also in 4 projects that use this

  • +4 more from openai

The file

We split this skill into the rules it gives an agent

6 rules. 1 is common, 3 are distinctive, and 2 are very specific to this project.

  • 1

    Common

    Most of the 24 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Before citing limits, settings, API fields, category IDs, or exact UI paths, retrieve current information from the Cloudflare One docs, the …

    line 13
  2. Very specific:

    If account access is available, inspect existing resources before proposing or making changes: Access apps/policies/groups/IdPs, Gateway …

    line 20
  3. Very specific:

    Check the domain guardrails before proposing anything.

    line 21
  4. Distinctive:

    Use fully qualified MCP tool names when MCP tools are available.

    line 41
  5. Distinctive:

    Never guess category IDs, application IDs, wirefilter fields, or API request bodies.

    line 42
  6. Distinctive:

    Do not enable broad production policies without explicit approval.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cloudflare One

Before citing limits, settings, API fields, category IDs, or exact UI paths, retrieve current information from the Cloudflare One docs, the Cloudflare docs MCP server, or the Cloudflare API schema.

Workflow

  1. Classify the ask: architecture, configuration, troubleshooting, migration, or review.
  2. Gather context: account ID, users/sites/apps, identity provider, SCIM/group sync, device management, traffic path, compliance constraints, and rollout blast radius. → references/assessment.md
  3. Retrieve only the current docs needed for the products involved: Access, Gateway, WARP/device client, Tunnel/Mesh, Cloudflare WAN, DLP, CASB, device posture, or identity.
  4. If account access is available, inspect existing resources before proposing or making changes: Access apps/policies/groups/IdPs, Gateway rules/lists/categories, device profiles/posture checks, tunnels/routes, DNS/resolver settings, and locations/sites.
  5. Check the domain guardrails before proposing anything. → references/guardrails.md
  6. Propose the change set with prerequisites, validation, and rollback. For risky changes, stage disabled or scoped to a pilot group/site unless the user explicitly asks otherwise. → references/validation.md

References

Load whenReference
Scoping a deployment — what to ask before configuring anythingreferences/assessment.md
Any config/troubleshooting work — per-domain gotchas and non-obvious semantics (identity, device client & split tunnels, private networking, Gateway/TLS/DLP, CASB & risk, infrastructure access, logs & DEX, WAN)references/guardrails.md
Before enabling broadly — per-product test casesreferences/validation.md
Migrating from Zscaler ZIA/ZPA, Palo Alto, legacy VPN, SWG, or another SASE stack — assessment, policy mapping, rollout, parity/gap analysisreferences/migrations.md

Output Defaults

  • Designs: current assumptions, target architecture, product responsibilities, rollout phases, validation, and open decisions.
  • Configuration work: prerequisites, exact resources to inspect/create/change, test cases, and rollback.
  • Troubleshooting: traffic path, likely failure point, evidence to collect, and next test.

API Safety

  • Use fully qualified MCP tool names when MCP tools are available.
  • Never guess category IDs, application IDs, wirefilter fields, or API request bodies. Retrieve the current schema/docs and existing account objects.
  • Do not enable broad production policies without explicit approval.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free