Cloudflare Agents
ListedAutomates Cloudflare configurations and optimizes performance using SecondSky's intelligent agents for enhanced security & speed.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add secondsky/claude-skills --skill cloudflare-agents -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
secondsky
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.flights.com.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
api.openai.commodel providerapi.flights.comundeclaredWhat it found
- plugins/cloudflare-agents/skills/cloudflare-agents/references/patterns-concepts.md:109contacts api.flights.com
const response = await fetch(`https://api.flights.com/search`, { - plugins/cloudflare-agents/skills/cloudflare-agents/references/patterns-concepts.md:118contacts api.flights.com
const response = await fetch(`https://api.flights.com/book`, {
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned secondsky/claude-skills at 8837836131.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 8837836131
- Scanned
- 22 files, 3,802 lines
About this skill
The Cloudflare Agents skill enables AI agents to interact directly with the Cloudflare platform, allowing them to manage DNS records, configure security rules, and deploy Workers. It acts as a bridge between natural language commands and Cloudflare's API infrastructure.
When to use it
- Automating routine DNS management tasks like adding or deleting A and CNAME records.
- Deploying or updating Cloudflare Workers without manual code pushing.
- Configuring security policies such as WAF rules or firewall settings dynamically.
- Retrieving real-time status of zones, accounts, or specific resources via API calls.
Key capabilities
- Direct integration with the Cloudflare REST API for resource management.
- Support for creating, updating, and deleting DNS entries programmatically.
- Ability to deploy Workers scripts directly through agent commands.
- Access to account-level metadata including zone lists and plan details.
Example prompts
- "Create a CNAME record pointing example.com to my-cloudflare-worker.workers.dev."
- "Deploy the latest version of my Worker script from the repository linked in context."
- "List all active zones under my Cloudflare account and their current plans."
Tips & gotchas
Ensure your AI agent has valid API tokens with appropriate permissions before attempting write operations like DNS updates or Worker deployments. Always verify zone names and record types to avoid unintended configuration changes in production environments.