Skip to content

feat: add CF1 Stack skills for Cloudflare One (21 skills)#55

Open
abelinkinbio wants to merge 1 commit into
cloudflare:mainfrom
abelinkinbio:cf1-stack-skills
Open

feat: add CF1 Stack skills for Cloudflare One (21 skills)#55
abelinkinbio wants to merge 1 commit into
cloudflare:mainfrom
abelinkinbio:cf1-stack-skills

Conversation

@abelinkinbio

Copy link
Copy Markdown

What

Adds 21 Cloudflare One skills covering the full CF1 platform — Gateway (SWG), Access (ZTNA), Tunnels, WAN, Device Posture, CASB, DLP, Risk Scoring, Architecture Design, and vendor migration (Zscaler ZIA/ZPA, Palo Alto).

Why

Cloudflare Skills currently covers the Developer Platform (Workers, D1, R2, etc.). This PR extends coverage to Cloudflare One — the SASE/zero trust side of the platform — enabling AI agents to assist with deployment, migration, and operations across the full Cloudflare stack.

What's included

21 new skill directories under skills/, each containing a single SKILL.md:

Domain Skills
Gateway (SWG) gateway-policy-design, gateway-tls-inspection, gateway-dns-security, gateway-network-policies, gateway-dlp
Access (ZTNA) access-app-setup, access-identity, access-private-network, access-saas-federation
Tunnels & Connectivity tunnel-deployment, tunnel-routing, wan-site-connectivity
Device Posture device-posture-setup
CASB / SSPM casb-integration, casb-posture-triage
DLP dlp-profile-design
Risk risk-scoring
Migration migrate-zscaler-zia, migrate-zscaler-zpa, migrate-palo-alto
Architecture architecture-design

1 modified file: README.md — added a "Cloudflare One (CF1 Stack)" section with skill descriptions.

Skill format

Each skill follows the existing skills/<name>/SKILL.md convention and includes:

  • YAML frontmatter (name, description, domain, stage, tools, docs)
  • Lifecycle stages: Assess → Design → Implement → Validate → Operate
  • Both MCP-automated and manual (Dashboard/API) implementation paths
  • Decision matrices, gotchas from real deployments, and related skill links

Impact

  • Zero file collisions — all 21 directories are new
  • No structural changes — follows the existing skill directory convention
  • No config changes.mcp.json, plugin manifests untouched

Source: CF1 Stack

Add 21 Cloudflare One deployment, migration, and operations skills
covering Gateway (SWG), Access (ZTNA), Tunnels, WAN, Device Posture,
CASB, DLP, Risk Scoring, Architecture Design, and vendor migration
(Zscaler ZIA/ZPA, Palo Alto).

Each skill follows the CF1 Lifecycle (Assess → Design → Implement →
Validate → Operate) and includes both MCP-automated and manual
(Dashboard/API) implementation paths.

Source: https://gitlab.cfdata.org/fmeszaro/cf1stack

@irvinebroque irvinebroque left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't a good use of Agent Skills.

  • Overfits and will get out of sync with API
  • Duplicates lots of content that is in docs (or if not, should be)
  • Separates into many discrete skills in ways that models/agents don't need / hurt more than they help
  • Eats lots of context

Would like to see some kind of lightweight evals / something that shows agent run with and without these skills that demonstrate they are effective.

See:

You could probably solve most of this with 1-2 skills, ex:

#56

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants