cloudflare-manager

What This Skill Does

The cloudflare-manager skill provides a comprehensive interface for OpenClaw AI to interact with Cloudflare infrastructure. It abstracts the complexity of managing DNS records, configuring Zero Trust tunnels, and orchestrating ingress rules for local services. By automating API calls to Cloudflare and managing local system configuration for the cloudflared daemon, it allows users to expose local servers securely to the internet without manual intervention or risky port forwarding.

Installation

To integrate this skill into your OpenClaw environment, execute the command: clawhub install openclaw/skills/skills/1999azzar/cloudflare-manager. Ensure that you have python3 and cloudflared installed on your host machine. Configure your environment variables by setting CLOUDFLARE_API_TOKEN and CLOUDFLARE_ZONE_ID within a .env file located in your workspace root. Finally, run the initialization script via bash scripts/install.sh to prepare the directory structures and verify dependencies.

Use Cases

• Domain Pointing: Automate the creation of A, CNAME, or TXT records when provisioning new staging environments or microservices.
• Local Tunneling: Safely expose local web development servers (like localhost:8080) to a public domain via a Cloudflare Tunnel, eliminating the need to expose ports on your router.
• Infrastructure Updates: Dynamically update ingress rules as your service architecture scales, ensuring that your local cloudflared configuration stays synchronized with your Cloudflare Zero Trust dashboard.
• DevOps Orchestration: Integrate this skill into broader automation pipelines to ensure your network settings are updated immediately following code deployments.

Example Prompts

1. "Add an A record for dev-server pointing to 192.168.1.50 in my Cloudflare zone."
2. "Update my tunnel ingress to map api.example.com to localhost:3000 and restart the service."
3. "List all current DNS records for the configured zone to verify the environment state."

Tips & Limitations

• Safety First: Always utilize the --dry-run flag when performing ingress updates to validate the configuration file changes before the tool attempts to restart the cloudflared service.
• Least Privilege: Always scope your CLOUDFLARE_API_TOKEN to the specific zone and required permissions (e.g., DNS read/write only). Avoid using global API keys.
• Sudo Permissions: Because this tool interacts with /etc/cloudflared/, ensure you have reviewed the references/sudoers.example to provide the minimum required sudo privileges without exposing your system to security risks. If you are running in a restricted user environment, verify that your user is part of the appropriate group to execute the tunnel restart command.