Skip to content
TakoAPI
Back to skills

cloudflare-guard

by guifav

DevOps & Cloud
572Downloads reported by clawskills.sh
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Configures and manages Cloudflare DNS, caching, security rules, rate limiting, and Workers.

Description

What This Skill Does

Manages Cloudflare DNS records, SSL/TLS settings, caching rules, rate limiting, and bot protection for web apps deployed on Vercel. Uses the Cloudflare API v4 directly via curl. Follows a mandatory plan-before-execute protocol to avoid downtime.

The mandatory planning protocol catches risky DNS and SSL changes before execution, reducing the chance of accidental downtime from misconfiguration.

When to Use It

  • Setting up DNS for a new Vercel deployment
  • Purging CDN cache after a production release
  • Adding rate limits to API routes under traffic abuse
  • Enabling bot fight mode on a public-facing site
  • Troubleshooting 522 errors caused by wrong SSL mode

Example Workflow

INPUT

User asks: Set up Cloudflare for my new Vercel project at example.com

AGENT
  1. 1

    Query existing DNS records and current SSL settings for the zone

  2. 2

    Add CNAME record pointing to cname.vercel-dns.com with proxy enabled

  3. 3

    Set SSL mode to Full (Strict) and enable Always Use HTTPS

  4. 4

    Create rate limiting rule for /api/* routes and enable Bot Fight Mode

  5. 5

    Set browser cache TTL and add page rule to aggressively cache _next/static/*

OUTPUT

All 7 setup steps completed. DNS propagation may take up to 24 hours. SSL is strict, bot protection is active, and static assets are cached for 30 days.

Requirements

  • CLOUDFLARE_API_TOKEN environment variable
  • CLOUDFLARE_ZONE_ID environment variable
  • Cloudflare account with the target domain added

Installation

clawhub install guifav/cloudflare-guard

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links