Cloudflare Dns logo

Cloudflare Dns

Organization
OpenMinis
cloudflare-dns

Use the flarectl command-line tool to manage Cloudflare DNS records, including listing, adding, updating, and deleting DNS records, as well as querying zone information. This skill must be triggered whenever a user mentions "Cloudflare DNS," "CF DNS," "add DNS record," "delete DNS record," "update DNS," "view DNS records," "cloudflare-dns," "flarectl," or any scenario involving Cloudflare DNS management.

Overview

PublisherOpenMinis
RepositoryMinisSkills
Skill namecloudflare-dns
Stars
543
Forks
86
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by OpenMinis on GitHub. Read the source before you install it.

Installation

Install the Cloudflare Dns AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/OpenMinis/MinisSkills/tree/main/cloudflare-dns
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/OpenMinis/MinisSkills.git /tmp/MinisSkills
mkdir -p .claude/skills
cp -r /tmp/MinisSkills/cloudflare-dns .claude/skills/cloudflare-dns
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cloudflare Dns in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cloudflare Dns on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cloudflare Dns is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Cloudflare DNS Management

Environment Setup

Install flarectl

In the current environment (Alpine Linux arm64), the preinstalled version can be used directly. If it is not available, install it from the release:

bash
if ! which flarectl > /dev/null 2>&1; then
  wget -q https://github.com/wsvn53/flarectl/releases/download/flarectl-v0.1.0-alpine-arm64/flarectl-linux-arm64 \
    -O /usr/local/bin/flarectl && chmod +x /usr/local/bin/flarectl
fi

Authentication Configuration

flarectl supports two authentication methods. Prefer the API Token method:

Method 1: API Token (recommended)

bash
export CF_API_TOKEN=<your_token>

Method 2: Global API Key

bash
export CF_API_KEY=<your_key>
export CF_API_EMAIL=<your_email>

Optional:

bash
export CF_ACCOUNT_ID=<account_id>   # Specify when using multiple accounts

Check whether the environment variables are set:

bash
[ -n "$CF_API_TOKEN" ] && echo "Token: set" || echo "Token: NOT SET"
[ -n "$CF_API_KEY" ] && echo "API Key: set" || echo "API Key: NOT SET"

If they are not set, tell the user which variable names are required and provide setup links:


Common Operations

Query the Zone List

bash
flarectl zone list

Example output:

ID                               NAME          PLAN   STATUS
abc123...                        example.com   Free   active

List DNS Records

bash
# List all records for a domain
flarectl dns list --zone example.com

# Filter by type
flarectl dns list --zone example.com --type A

# Filter by name
flarectl dns list --zone example.com --name sub.example.com

# Output in JSON format (useful for parsing IDs)
flarectl --json dns list --zone example.com

Add DNS Records

bash
# A record
flarectl dns create --zone example.com --type A --name sub.example.com --content 1.2.3.4 --ttl 1

# CNAME record (enable orange-cloud proxy)
flarectl dns create --zone example.com --type CNAME --name www.example.com --content example.com --proxy

# MX record
flarectl dns create --zone example.com --type MX --name example.com --content mail.example.com --priority 10

# TXT record
flarectl dns create --zone example.com --type TXT --name _dmarc.example.com --content "v=DMARC1; p=none"

# AAAA record (IPv6)
flarectl dns create --zone example.com --type AAAA --name ipv6.example.com --content "2001:db8::1"

Parameter descriptions:

  • --ttl 1: Automatic TTL (recommended); other values are in seconds (for example, --ttl 300)
  • --proxy: Enable the Cloudflare orange-cloud proxy (supported only for A/AAAA/CNAME records)

Update DNS Records

Updating requires the record id. Use dns list to get it first:

bash
# Get the record ID
flarectl --json dns list --zone example.com --name sub.example.com | python3 -c "
import sys,json
for r in json.load(sys.stdin):
    print(r['id'], r['type'], r['name'], r['content'])
"

# Update the content
flarectl dns update --zone example.com --id <record_id> --content 5.6.7.8

# Update and enable proxy
flarectl dns update --zone example.com --id <record_id> --content 5.6.7.8 --proxy

Create or Update (upsert)

bash
# Update if it exists; create it if it does not exist
flarectl dns create-or-update --zone example.com --type A --name sub.example.com --content 1.2.3.4

Delete DNS Records

bash
# Look up the ID first
flarectl --json dns list --zone example.com --name sub.example.com | python3 -c "
import sys,json
for r in json.load(sys.stdin):
    print(r['id'], r['name'], r['type'])
"

# Delete
flarectl dns delete --zone example.com --id <record_id>

Batch Delete Records with the Same Name

bash
flarectl --json dns list --zone example.com --name sub.example.com | python3 -c "
import sys,json,subprocess
for r in json.load(sys.stdin):
    subprocess.run(['flarectl','dns','delete','--zone','example.com','--id',r['id']])
    print('Deleted:', r['id'], r['type'], r['content'])
"

Workflow

  1. Verify authentication: Check whether CF_API_TOKEN or CF_API_KEY+CF_API_EMAIL is set
  2. Confirm the domain: If the user has not specified a zone, first use flarectl zone list to list available domains for the user to choose from
  3. Perform the operation: Run list/create/update/delete as needed
  4. Display results: After the operation, use flarectl dns list --zone <zone> to show the latest record status

Notes

  • Deletions are irreversible; confirm with the user before proceeding
  • --proxy supports only A, AAAA, and CNAME record types
  • MX records must specify --priority
  • TXT record content that contains spaces must be enclosed in quotes
  • The global flag flarectl --json must be placed before the subcommand.

Frequently asked questions

What does the Cloudflare Dns AI skill do?

Use the flarectl command-line tool to manage Cloudflare DNS records, including listing, adding, updating, and deleting DNS records, as well as querying zone information. This skill must be triggered whenever a user mentions "Cloudflare DNS," "CF DNS," "add DNS record," "delete DNS record," "update DNS," "view DNS records," "cloudflare-dns," "flarectl," or any scenario involving Cloudflare DNS management.

Why use Cloudflare Dns on TypingMind?

Because you install it once and use it with any model. Cloudflare Dns is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cloudflare Dns in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/OpenMinis/MinisSkills/tree/main/cloudflare-dns. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Cloudflare Dns?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cloudflare Dns?

As many as you like. As long as a model supports skills, you can use Cloudflare Dns with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cloudflare Dns AI skill free?

Yes. It is published on GitHub by OpenMinis under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇