cloudflare — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited cloudflare (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<!-- metadata: { "openclaw": { "requires": { "bins": ["cloudflare-cli"], "env": ["CLOUDFLARE_API_TOKEN"] } } } -->
Use the cloudflare-cli command to manage Cloudflare domains, DNS records, SSL/TLS settings, cache, and analytics.
CLOUDFLARE_API_TOKEN environment variable must be set# List all zones
cloudflare-cli zones list
# Filter by domain name
cloudflare-cli zones list --name example.com
# Get zone details
cloudflare-cli zones get <zone-id># List all DNS records for a zone
cloudflare-cli dns list <zone-id>
# Filter by type
cloudflare-cli dns list <zone-id> --type A
cloudflare-cli dns list <zone-id> --type CNAME
# Create DNS records
cloudflare-cli dns create <zone-id> -t A -n www -c 192.168.1.1 --proxied
cloudflare-cli dns create <zone-id> -t CNAME -n blog -c example.com --proxied
cloudflare-cli dns create <zone-id> -t MX -n @ -c mail.example.com --priority 10
cloudflare-cli dns create <zone-id> -t TXT -n @ -c "v=spf1 include:_spf.google.com ~all"
# Update DNS record
cloudflare-cli dns update <zone-id> <record-id> -c 192.168.1.2
# Delete DNS record
cloudflare-cli dns delete <zone-id> <record-id># Get Universal SSL settings
cloudflare-cli ssl settings <zone-id>
# Enable/Disable Universal SSL
cloudflare-cli ssl enable <zone-id>
cloudflare-cli ssl disable <zone-id>
# List SSL certificates
cloudflare-cli ssl certificates <zone-id>
# Check SSL verification status
cloudflare-cli ssl verification <zone-id># Purge everything
cloudflare-cli cache purge <zone-id> --all
# Purge specific URLs
cloudflare-cli cache purge <zone-id> --files https://example.com/page1 https://example.com/page2
# Purge by cache tags
cloudflare-cli cache purge <zone-id> --tags tag1 tag2# Get analytics for last 24 hours
cloudflare-cli analytics dashboard <zone-id> --since -1d --until now
# Get analytics for last 7 days
cloudflare-cli analytics dashboard <zone-id> --since -7d --until now
# Get analytics for specific date range (ISO format)
cloudflare-cli analytics dashboard <zone-id> --since 2024-01-01T00:00:00Z --until 2024-01-31T23:59:59ZAll commands output JSON for easy parsing. Example:
{
"id": "abc123",
"name": "www.example.com",
"type": "A",
"content": "192.168.1.1",
"proxied": true,
"ttl": 1
}Errors are also returned as JSON:
{
"error": "Cloudflare API error: Invalid zone identifier"
}# First, get the zone ID
cloudflare-cli zones list --name example.com
# Create the A record (replace <zone-id> with actual ID)
cloudflare-cli dns create <zone-id> -t A -n subdomain -c 123.45.67.89 --proxied# List current records
cloudflare-cli dns list <zone-id> --type A
# Update the record with new IP
cloudflare-cli dns update <zone-id> <record-id> -c 98.76.54.32
# Purge cache to ensure changes propagate
cloudflare-cli cache purge <zone-id> --all# Add MX record
cloudflare-cli dns create <zone-id> -t MX -n @ -c mail.example.com --priority 10
# Add SPF record
cloudflare-cli dns create <zone-id> -t TXT -n @ -c "v=spf1 include:_spf.google.com ~all"
# Add DKIM record
cloudflare-cli dns create <zone-id> -t TXT -n google._domainkey -c "v=DKIM1; k=rsa; p=..."~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.