{"id":"0ced7936-6498-4c1c-ad95-ef83242f789f","entityType":"agent","slug":"clawhub-hith3sh-cloudflare-infrastructure","name":"Cloudflare","canonicalUrl":"https://www.xpersona.co/agent/clawhub-hith3sh-cloudflare-infrastructure","canonicalPath":"/agent/clawhub-hith3sh-cloudflare-infrastructure","generatedAt":"2026-10-09T12:57:18.676Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T10:36:47.760Z","emptyReason":null},"description":"Manage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. Use this skill when users want to insp... Skill: Cloudflare Owner: hith3sh Summary: Manage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. Use this skill when users want to insp... Tags: clawlink:0.1.0, integration:0.1.0, latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:05:30.130Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page a","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.9K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:cloudflare-infrastructure","sourceUrl":"https://clawhub.ai/hith3sh/cloudflare-infrastructure","homepage":"https://clawhub.ai/hith3sh/skills/cloudflare-infrastructure","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/hith3sh/cloudflare-infrastructure","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/hith3sh/skills/cloudflare-infrastructure","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":69,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Manage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. Use this skill when users want to insp..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T10:36:47.760Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T10:36:47.760Z","emptyReason":null},"stars":null,"forks":null,"downloads":2949,"packageName":null,"latestVersion":"1.0.6","tractionLabel":"2.9K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T10:36:47.760Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T10:36:47.760Z","lastCrawledAt":"2026-10-09T10:36:47.760Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T10:36:47.760Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.6","createdAt":"2026-06-09T07:05:30.130Z","changelog":"Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.","fileCount":3,"zipByteSize":5828},{"version":"1.0.5","createdAt":"2026-06-09T06:08:31.384Z","changelog":"- Updated SKILL.md documentation (minor revisions and image link update, no functional changes). - Removed skill-card.md file. - No changes to API, usage, or supported tools.","fileCount":3,"zipByteSize":5575},{"version":"1.0.4","createdAt":"2026-06-09T04:45:15.850Z","changelog":"- Removed the sample file skill-card.md to reduce redundancy. - No changes to features or functionality.","fileCount":3,"zipByteSize":5539},{"version":"1.0.2","createdAt":"2026-06-08T16:45:25.388Z","changelog":"- No file changes detected in this release. - Documentation and skill metadata remain unchanged. - No new features, fixes, or updates included in this version.","fileCount":3,"zipByteSize":5571},{"version":"1.0.1","createdAt":"2026-06-08T16:26:55.575Z","changelog":"- Added a Cloudflare logo image at the top of the documentation. - Removed the outdated skill-card.md file. - No changes to functionality or available tools; documentation only.","fileCount":3,"zipByteSize":5555},{"version":"0.1.1","createdAt":"2026-06-07T13:27:48.668Z","changelog":"Full rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.","fileCount":3,"zipByteSize":5786},{"version":"0.1.0","createdAt":"2026-05-16T15:33:51.865Z","changelog":"Initial ClawLink integration skill.","fileCount":3,"zipByteSize":3649}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:cloudflare-infrastructure","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-cloudflare-infrastructure/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-cloudflare-infrastructure/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-cloudflare-infrastructure/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-cloudflare-infrastructure/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-cloudflare-infrastructure/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-cloudflare-infrastructure/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-09T12:57:18.674Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-cloudflare-infrastructure/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-cloudflare-infrastructure/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-cloudflare-infrastructure/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-cloudflare-infrastructure/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-09T10:36:47.760Z","emptyReason":null},"readme":"Skill: Cloudflare\n\nOwner: hith3sh\n\nSummary: Manage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. Use this skill when users want to insp...\n\nTags: clawlink:0.1.0, integration:0.1.0, latest:1.0.6\n\nVersion history:\n\nv1.0.6 | 2026-06-09T07:05:30.130Z | user\n\nAdd UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.\n\nv1.0.5 | 2026-06-09T06:08:31.384Z | auto\n\n- Updated SKILL.md documentation (minor revisions and image link update, no functional changes).\n- Removed skill-card.md file.\n- No changes to API, usage, or supported tools.\n\nv1.0.4 | 2026-06-09T04:45:15.850Z | auto\n\n- Removed the sample file skill-card.md to reduce redundancy.\n- No changes to features or functionality.\n\nv1.0.2 | 2026-06-08T16:45:25.388Z | auto\n\n- No file changes detected in this release.\n- Documentation and skill metadata remain unchanged.\n- No new features, fixes, or updates included in this version.\n\nv1.0.1 | 2026-06-08T16:26:55.575Z | auto\n\n- Added a Cloudflare logo image at the top of the documentation.\n- Removed the outdated skill-card.md file.\n- No changes to functionality or available tools; documentation only.\n\nv0.1.1 | 2026-06-07T13:27:48.668Z | user\n\nFull rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.\n\nv0.1.0 | 2026-05-16T15:33:51.865Z | user\n\nInitial ClawLink integration skill.\n\nArchive index:\n\nArchive v1.0.6: 3 files, 5828 bytes\n\nFiles: skill-card.md (2793b), SKILL.md (13809b), _meta.json (144b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: cloudflare-infrastructure\ndescription: Manage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. Use this skill when users want to inspect DNS records, manage zones, configure workers, or update firewall rules.\n---\n\n# Cloudflare\n\n![Cloudflare](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/cloudflare.svg?v=2)\n\nWork with Cloudflare from chat — manage zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API with API token authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=cloudflare-infrastructure) for hosted connection flows and credentials so you do not need to configure Cloudflare API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Cloudflare |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Cloudflare |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│ Cloudflare API    │\n│   (User Chat)   │     │   (API Token)│     │ (Zones/DNS/APIs) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Cloudflare│                       │\n         │                       │  4. Secure Token      │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │ Cloudflare│\n   │  File    │           │ Auth     │           │ Dashboard│\n   └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Cloudflare again.\"\n\n## Quick Start\n\n```bash\n# List all zones\nclawlink_call_tool --tool \"cloudflare_list_zones\" --params '{}'\n\n# List DNS records in a zone\nclawlink_call_tool --tool \"cloudflare_list_dns_records\" --params '{\"zone_id\": \"ZONE_ID\"}'\n\n# List accounts\nclawlink_call_tool --tool \"cloudflare_list_accounts\" --params '{}'\n```\n\n## Authentication\n\nAll Cloudflare tool calls are authenticated automatically by ClawLink using the user's connected Cloudflare account.\n\n**No API token is required in chat.** ClawLink stores the API token securely and injects it into every Cloudflare API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=cloudflare and connect Cloudflare.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `cloudflare` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration cloudflare\n```\n\n**Response:** Returns the live tool catalog for Cloudflare.\n\n### Reconnect\n\nIf Cloudflare tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=cloudflare\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration cloudflare`\n\n## Security & Permissions\n\n- Access is scoped to the permissions granted by the Cloudflare API token.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete zone, delete DNS record, delete WAF list) are marked as high-impact and must be confirmed.\n\n## Tool Reference\n\n### Zones\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_zones` | List zones in the account with pagination | Read |\n| `cloudflare_create_zone` | Create a new DNS zone (domain) | Write |\n| `cloudflare_update_zone` | Update zone properties (one field at a time) | Write |\n| `cloudflare_delete_zone` | Permanently delete a zone and all DNS records | Write |\n\n### DNS Records\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_dns_records` | List and search DNS records in a zone | Read |\n| `cloudflare_create_dns_record` | Create a new DNS record in a zone | Write |\n| `cloudflare_update_dns_record` | Update an existing DNS record | Write |\n| `cloudflare_delete_dns_record` | Permanently delete a DNS record | Write |\n\n### Accounts & Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_accounts` | List all Cloudflare accounts accessible to the user | Read |\n| `cloudflare_list_account_members` | List account members with roles and permissions | Read |\n\n### Load Balancers\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_monitors` | List load balancer monitors | Read |\n| `cloudflare_list_pools` | List load balancer origin pools | Read |\n\n### WAF & Rules\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_firewall_rules` | List firewall rules for a zone | Read |\n| `cloudflare_create_list` | Create a WAF custom list (IPs, hostnames, ASNs) | Write |\n| `cloudflare_get_lists` | List all WAF lists | Read |\n| `cloudflare_update_list` | Update a WAF list description | Write |\n| `cloudflare_delete_list` | Delete a WAF list | Write |\n\n### Tunnels\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_tunnels` | List Cloudflare Tunnel tunnels | Read |\n| `cloudflare_update_tunnel_configuration` | Update tunnel ingress rules (replaces full config) | Write |\n\n### Bot Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_get_bot_management_settings` | Get bot management configuration for a zone | Read |\n\n## Code Examples\n\n### List zones\n\n```bash\nclawlink_call_tool --tool \"cloudflare_list_zones\" \\\n  --params '{}'\n```\n\n### Create a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_create_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"type\": \"A\",\n    \"name\": \"api\",\n    \"content\": \"192.0.2.1\",\n    \"ttl\": 3600\n  }'\n```\n\n### Update a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_update_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"dns_record_id\": \"RECORD_ID\",\n    \"type\": \"A\",\n    \"name\": \"api\",\n    \"content\": \"192.0.2.2\",\n    \"ttl\": 1800\n  }'\n```\n\n### Delete a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_delete_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"dns_record_id\": \"RECORD_ID\"\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Cloudflare is connected.\n2. Call `clawlink_list_tools --integration cloudflare` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `cloudflare`.\n5. If no Cloudflare tools appear, direct the user to https://claw-link.dev/dashboard?add=cloudflare.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  list → get → describe → call                              │\n│                                                             │\n│  Example: List zones → List DNS records → Show results      │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE OPERATIONS (Require Confirmation)                     │\n│  list → get → describe → preview → confirm → call         │\n│                                                             │\n│  Example: Describe tool → Preview changes → User approves   │\n│           → Execute update                                 │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Zone IDs and DNS record IDs are required for all zone-scoped operations — retrieve them via list tools first.\n- Pagination: use `page` and `per_page` parameters and check `result_info.total_pages` to iterate all pages.\n- Tunnel configuration updates replace the entire configuration — fetch the current config first to avoid losing existing rules.\n- WAF lists have plan-based limits (Free: 1 list, Pro/Business: 10 lists, Enterprise: 1000 lists).\n- DNS record updates only modify provided fields.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration cloudflare`. |\n| Missing connection | Cloudflare is not connected. Direct the user to https://claw-link.dev/dashboard?add=cloudflare. |\n| `zone_not_found` | Zone does not exist or is not accessible. |\n| `dns_record_not_found` | DNS record does not exist. |\n| `InvalidArgument` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `cloudflare`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Cloudflare API Documentation](https://developers.cloudflare.com/api/)\n- [Cloudflare DNS API](https://developers.cloudflare.com/api/operations/dns-records-for-a-zone)\n- [Cloudflare Zones API](https://developers.cloudflare.com/api/operations/zones)\n- ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=cloudflare-infrastructure\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [AWS](https://clawhub.ai/hith3sh/aws-infrastructure) — For AWS infrastructure management\n- [GitHub](https://clawhub.ai/hith3sh/github-repos) — For GitHub CI/CD and deployments\n- [Datadog](https://clawhub.ai/hith3sh/datadog-monitoring) — For observability and monitoring\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=cloudflare-infrastructure)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.6:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"cloudflare-infrastructure\",\n  \"version\": \"1.0.6\",\n  \"publishedAt\": 1780988730130\n}\n\nFile v1.0.6:skill-card.md\n\n## Description:\n\nManage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and operators use this skill from OpenClaw to inspect and manage Cloudflare infrastructure, including zones, DNS records, account resources, workers, rules, firewall settings, WAF lists, tunnels, and related Cloudflare API resources.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill manages high-impact Cloudflare infrastructure through a third-party ClawLink plugin that stores and uses Cloudflare credentials.\n\nMitigation: Install only if the publisher and ClawLink are trusted, use the narrowest Cloudflare permissions possible, and revoke the Cloudflare connection when it is no longer needed.\n\nRisk: Write operations can create, update, or delete zones, DNS records, WAF lists, tunnel configuration, and other account resources.\n\nMitigation: Confirm the target resource and intended effect before every write, preview tool calls where supported, and prefer read/list/describe operations before changes.\n\nRisk: Tunnel configuration updates replace the full configuration and can unintentionally remove existing ingress rules.\n\nMitigation: Fetch and review the current tunnel configuration before applying an update, then confirm that the preview preserves required rules.\n\n## Reference(s):\n\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/cloudflare-infrastructure)\n- [Cloudflare API Documentation](https://developers.cloudflare.com/api/)\n- [Cloudflare DNS API](https://developers.cloudflare.com/api/operations/dns-records-for-a-zone)\n- [Cloudflare Zones API](https://developers.cloudflare.com/api/operations/zones)\n- [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=cloudflare-infrastructure)\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include Cloudflare tool names, preview guidance, confirmation prompts, and troubleshooting steps.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.5: 3 files, 5575 bytes\n\nFiles: skill-card.md (2339b), SKILL.md (13575b), _meta.json (144b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: cloudflare-infrastructure\ndescription: Manage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. Use this skill when users want to inspect DNS records, manage zones, configure workers, or update firewall rules.\n---\n\n# Cloudflare\n\n![Cloudflare](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/cloudflare.svg?v=2)\n\nWork with Cloudflare from chat — manage zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API with API token authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Cloudflare API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Cloudflare |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Cloudflare |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│ Cloudflare API    │\n│   (User Chat)   │     │   (API Token)│     │ (Zones/DNS/APIs) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Cloudflare│                       │\n         │                       │  4. Secure Token      │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │ Cloudflare│\n   │  File    │           │ Auth     │           │ Dashboard│\n   └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Cloudflare again.\"\n\n## Quick Start\n\n```bash\n# List all zones\nclawlink_call_tool --tool \"cloudflare_list_zones\" --params '{}'\n\n# List DNS records in a zone\nclawlink_call_tool --tool \"cloudflare_list_dns_records\" --params '{\"zone_id\": \"ZONE_ID\"}'\n\n# List accounts\nclawlink_call_tool --tool \"cloudflare_list_accounts\" --params '{}'\n```\n\n## Authentication\n\nAll Cloudflare tool calls are authenticated automatically by ClawLink using the user's connected Cloudflare account.\n\n**No API token is required in chat.** ClawLink stores the API token securely and injects it into every Cloudflare API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=cloudflare and connect Cloudflare.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `cloudflare` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration cloudflare\n```\n\n**Response:** Returns the live tool catalog for Cloudflare.\n\n### Reconnect\n\nIf Cloudflare tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=cloudflare\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration cloudflare`\n\n## Security & Permissions\n\n- Access is scoped to the permissions granted by the Cloudflare API token.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete zone, delete DNS record, delete WAF list) are marked as high-impact and must be confirmed.\n\n## Tool Reference\n\n### Zones\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_zones` | List zones in the account with pagination | Read |\n| `cloudflare_create_zone` | Create a new DNS zone (domain) | Write |\n| `cloudflare_update_zone` | Update zone properties (one field at a time) | Write |\n| `cloudflare_delete_zone` | Permanently delete a zone and all DNS records | Write |\n\n### DNS Records\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_dns_records` | List and search DNS records in a zone | Read |\n| `cloudflare_create_dns_record` | Create a new DNS record in a zone | Write |\n| `cloudflare_update_dns_record` | Update an existing DNS record | Write |\n| `cloudflare_delete_dns_record` | Permanently delete a DNS record | Write |\n\n### Accounts & Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_accounts` | List all Cloudflare accounts accessible to the user | Read |\n| `cloudflare_list_account_members` | List account members with roles and permissions | Read |\n\n### Load Balancers\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_monitors` | List load balancer monitors | Read |\n| `cloudflare_list_pools` | List load balancer origin pools | Read |\n\n### WAF & Rules\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_firewall_rules` | List firewall rules for a zone | Read |\n| `cloudflare_create_list` | Create a WAF custom list (IPs, hostnames, ASNs) | Write |\n| `cloudflare_get_lists` | List all WAF lists | Read |\n| `cloudflare_update_list` | Update a WAF list description | Write |\n| `cloudflare_delete_list` | Delete a WAF list | Write |\n\n### Tunnels\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_tunnels` | List Cloudflare Tunnel tunnels | Read |\n| `cloudflare_update_tunnel_configuration` | Update tunnel ingress rules (replaces full config) | Write |\n\n### Bot Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_get_bot_management_settings` | Get bot management configuration for a zone | Read |\n\n## Code Examples\n\n### List zones\n\n```bash\nclawlink_call_tool --tool \"cloudflare_list_zones\" \\\n  --params '{}'\n```\n\n### Create a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_create_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"type\": \"A\",\n    \"name\": \"api\",\n    \"content\": \"192.0.2.1\",\n    \"ttl\": 3600\n  }'\n```\n\n### Update a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_update_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"dns_record_id\": \"RECORD_ID\",\n    \"type\": \"A\",\n    \"name\": \"api\",\n    \"content\": \"192.0.2.2\",\n    \"ttl\": 1800\n  }'\n```\n\n### Delete a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_delete_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"dns_record_id\": \"RECORD_ID\"\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Cloudflare is connected.\n2. Call `clawlink_list_tools --integration cloudflare` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `cloudflare`.\n5. If no Cloudflare tools appear, direct the user to https://claw-link.dev/dashboard?add=cloudflare.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  list → get → describe → call                              │\n│                                                             │\n│  Example: List zones → List DNS records → Show results      │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE OPERATIONS (Require Confirmation)                     │\n│  list → get → describe → preview → confirm → call         │\n│                                                             │\n│  Example: Describe tool → Preview changes → User approves   │\n│           → Execute update                                 │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Zone IDs and DNS record IDs are required for all zone-scoped operations — retrieve them via list tools first.\n- Pagination: use `page` and `per_page` parameters and check `result_info.total_pages` to iterate all pages.\n- Tunnel configuration updates replace the entire configuration — fetch the current config first to avoid losing existing rules.\n- WAF lists have plan-based limits (Free: 1 list, Pro/Business: 10 lists, Enterprise: 1000 lists).\n- DNS record updates only modify provided fields.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration cloudflare`. |\n| Missing connection | Cloudflare is not connected. Direct the user to https://claw-link.dev/dashboard?add=cloudflare. |\n| `zone_not_found` | Zone does not exist or is not accessible. |\n| `dns_record_not_found` | DNS record does not exist. |\n| `InvalidArgument` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `cloudflare`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Cloudflare API Documentation](https://developers.cloudflare.com/api/)\n- [Cloudflare DNS API](https://developers.cloudflare.com/api/operations/dns-records-for-a-zone)\n- [Cloudflare Zones API](https://developers.cloudflare.com/api/operations/zones)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [AWS](https://clawhub.ai/hith3sh/aws-infrastructure) — For AWS infrastructure management\n- [GitHub](https://clawhub.ai/hith3sh/github-repos) — For GitHub CI/CD and deployments\n- [Datadog](https://clawhub.ai/hith3sh/datadog-monitoring) — For observability and monitoring\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"cloudflare-infrastructure\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1780985311384\n}\n\nFile v1.0.5:skill-card.md\n\n## Description: <br>\nManage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nExternal users, developers, and infrastructure operators use this skill to inspect and manage Cloudflare zones, DNS records, workers, WAF rules, tunnels, and account resources from an agent workflow through ClawLink. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Cloudflare write operations can change live DNS, zone, WAF, tunnel, or account infrastructure. <br>\nMitigation: Use least-privilege Cloudflare API tokens, preview write operations, and execute changes only after explicit user confirmation. <br>\nRisk: Incorrect zone, DNS record, or tunnel identifiers can affect the wrong resource. <br>\nMitigation: List and verify target resources before writes, and use live tool descriptions and schemas before constructing tool calls. <br>\n\n\n## Reference(s): <br>\n- [Cloudflare API Documentation](https://developers.cloudflare.com/api/) <br>\n- [Cloudflare DNS API](https://developers.cloudflare.com/api/operations/dns-records-for-a-zone) <br>\n- [Cloudflare Zones API](https://developers.cloudflare.com/api/operations/zones) <br>\n- [ClawLink](https://claw-link.dev) <br>\n- [ClawLink Docs for OpenClaw](https://docs.claw-link.dev/openclaw) <br>\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/cloudflare-infrastructure) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance] <br>\n**Output Format:** [Markdown with inline shell commands and JSON tool-call parameters] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Guides ClawLink tool discovery, previews, confirmation-gated writes, and Cloudflare API calls.] <br>\n\n## Skill Version(s): <br>\n1.0.5 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.4: 3 files, 5539 bytes\n\nFiles: skill-card.md (2271b), SKILL.md (13571b), _meta.json (144b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: cloudflare-infrastructure\ndescription: Manage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. Use this skill when users want to inspect DNS records, manage zones, configure workers, or update firewall rules.\n---\n\n# Cloudflare\n\n![Cloudflare](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/cloudflare.svg)\n\nWork with Cloudflare from chat — manage zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API with API token authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Cloudflare API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Cloudflare |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Cloudflare |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│ Cloudflare API    │\n│   (User Chat)   │     │   (API Token)│     │ (Zones/DNS/APIs) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Cloudflare│                       │\n         │                       │  4. Secure Token      │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │ Cloudflare│\n   │  File    │           │ Auth     │           │ Dashboard│\n   └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Cloudflare again.\"\n\n## Quick Start\n\n```bash\n# List all zones\nclawlink_call_tool --tool \"cloudflare_list_zones\" --params '{}'\n\n# List DNS records in a zone\nclawlink_call_tool --tool \"cloudflare_list_dns_records\" --params '{\"zone_id\": \"ZONE_ID\"}'\n\n# List accounts\nclawlink_call_tool --tool \"cloudflare_list_accounts\" --params '{}'\n```\n\n## Authentication\n\nAll Cloudflare tool calls are authenticated automatically by ClawLink using the user's connected Cloudflare account.\n\n**No API token is required in chat.** ClawLink stores the API token securely and injects it into every Cloudflare API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=cloudflare and connect Cloudflare.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `cloudflare` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration cloudflare\n```\n\n**Response:** Returns the live tool catalog for Cloudflare.\n\n### Reconnect\n\nIf Cloudflare tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=cloudflare\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration cloudflare`\n\n## Security & Permissions\n\n- Access is scoped to the permissions granted by the Cloudflare API token.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete zone, delete DNS record, delete WAF list) are marked as high-impact and must be confirmed.\n\n## Tool Reference\n\n### Zones\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_zones` | List zones in the account with pagination | Read |\n| `cloudflare_create_zone` | Create a new DNS zone (domain) | Write |\n| `cloudflare_update_zone` | Update zone properties (one field at a time) | Write |\n| `cloudflare_delete_zone` | Permanently delete a zone and all DNS records | Write |\n\n### DNS Records\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_dns_records` | List and search DNS records in a zone | Read |\n| `cloudflare_create_dns_record` | Create a new DNS record in a zone | Write |\n| `cloudflare_update_dns_record` | Update an existing DNS record | Write |\n| `cloudflare_delete_dns_record` | Permanently delete a DNS record | Write |\n\n### Accounts & Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_accounts` | List all Cloudflare accounts accessible to the user | Read |\n| `cloudflare_list_account_members` | List account members with roles and permissions | Read |\n\n### Load Balancers\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_monitors` | List load balancer monitors | Read |\n| `cloudflare_list_pools` | List load balancer origin pools | Read |\n\n### WAF & Rules\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_firewall_rules` | List firewall rules for a zone | Read |\n| `cloudflare_create_list` | Create a WAF custom list (IPs, hostnames, ASNs) | Write |\n| `cloudflare_get_lists` | List all WAF lists | Read |\n| `cloudflare_update_list` | Update a WAF list description | Write |\n| `cloudflare_delete_list` | Delete a WAF list | Write |\n\n### Tunnels\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_tunnels` | List Cloudflare Tunnel tunnels | Read |\n| `cloudflare_update_tunnel_configuration` | Update tunnel ingress rules (replaces full config) | Write |\n\n### Bot Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_get_bot_management_settings` | Get bot management configuration for a zone | Read |\n\n## Code Examples\n\n### List zones\n\n```bash\nclawlink_call_tool --tool \"cloudflare_list_zones\" \\\n  --params '{}'\n```\n\n### Create a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_create_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"type\": \"A\",\n    \"name\": \"api\",\n    \"content\": \"192.0.2.1\",\n    \"ttl\": 3600\n  }'\n```\n\n### Update a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_update_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"dns_record_id\": \"RECORD_ID\",\n    \"type\": \"A\",\n    \"name\": \"api\",\n    \"content\": \"192.0.2.2\",\n    \"ttl\": 1800\n  }'\n```\n\n### Delete a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_delete_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"dns_record_id\": \"RECORD_ID\"\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Cloudflare is connected.\n2. Call `clawlink_list_tools --integration cloudflare` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `cloudflare`.\n5. If no Cloudflare tools appear, direct the user to https://claw-link.dev/dashboard?add=cloudflare.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  list → get → describe → call                              │\n│                                                             │\n│  Example: List zones → List DNS records → Show results      │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE OPERATIONS (Require Confirmation)                     │\n│  list → get → describe → preview → confirm → call         │\n│                                                             │\n│  Example: Describe tool → Preview changes → User approves   │\n│           → Execute update                                 │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Zone IDs and DNS record IDs are required for all zone-scoped operations — retrieve them via list tools first.\n- Pagination: use `page` and `per_page` parameters and check `result_info.total_pages` to iterate all pages.\n- Tunnel configuration updates replace the entire configuration — fetch the current config first to avoid losing existing rules.\n- WAF lists have plan-based limits (Free: 1 list, Pro/Business: 10 lists, Enterprise: 1000 lists).\n- DNS record updates only modify provided fields.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration cloudflare`. |\n| Missing connection | Cloudflare is not connected. Direct the user to https://claw-link.dev/dashboard?add=cloudflare. |\n| `zone_not_found` | Zone does not exist or is not accessible. |\n| `dns_record_not_found` | DNS record does not exist. |\n| `InvalidArgument` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `cloudflare`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Cloudflare API Documentation](https://developers.cloudflare.com/api/)\n- [Cloudflare DNS API](https://developers.cloudflare.com/api/operations/dns-records-for-a-zone)\n- [Cloudflare Zones API](https://developers.cloudflare.com/api/operations/zones)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [AWS](https://clawhub.ai/hith3sh/aws-infrastructure) — For AWS infrastructure management\n- [GitHub](https://clawhub.ai/hith3sh/github-repos) — For GitHub CI/CD and deployments\n- [Datadog](https://clawhub.ai/hith3sh/datadog-monitoring) — For observability and monitoring\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"cloudflare-infrastructure\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1780980315850\n}\n\nFile v1.0.4:skill-card.md\n\n## Description: <br>\nManage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and infrastructure operators use this skill to inspect and manage Cloudflare zones, DNS records, workers, firewall rules, tunnels, WAF lists, and account resources from an agent workflow. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Approved Cloudflare write tools can change or delete infrastructure resources. <br>\nMitigation: Use a minimally scoped Cloudflare API token, review previews carefully, and confirm the exact target resource and intended effect before writes. <br>\nRisk: A connected Cloudflare account remains available to ClawLink while the integration is active. <br>\nMitigation: Revoke the ClawLink connection when it is no longer needed. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/cloudflare-infrastructure) <br>\n- [Publisher Profile](https://clawhub.ai/user/hith3sh) <br>\n- [Cloudflare API Documentation](https://developers.cloudflare.com/api/) <br>\n- [Cloudflare DNS Records API](https://developers.cloudflare.com/api/operations/dns-records-for-a-zone) <br>\n- [Cloudflare Zones API](https://developers.cloudflare.com/api/operations/zones) <br>\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown with inline shell commands and JSON parameters] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May produce Cloudflare tool-call guidance and previews before confirmed write operations.] <br>\n\n## Skill Version(s): <br>\n1.0.4 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.2: 3 files, 5571 bytes\n\nFiles: skill-card.md (2452b), SKILL.md (13571b), _meta.json (144b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: cloudflare-infrastructure\ndescription: Manage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. Use this skill when users want to inspect DNS records, manage zones, configure workers, or update firewall rules.\n---\n\n# Cloudflare\n\n![Cloudflare](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/cloudflare.svg)\n\nWork with Cloudflare from chat — manage zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API with API token authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Cloudflare API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Cloudflare |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Cloudflare |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│ Cloudflare API    │\n│   (User Chat)   │     │   (API Token)│     │ (Zones/DNS/APIs) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Cloudflare│                       │\n         │                       │  4. Secure Token      │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │ Cloudflare│\n   │  File    │           │ Auth     │           │ Dashboard│\n   └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Cloudflare again.\"\n\n## Quick Start\n\n```bash\n# List all zones\nclawlink_call_tool --tool \"cloudflare_list_zones\" --params '{}'\n\n# List DNS records in a zone\nclawlink_call_tool --tool \"cloudflare_list_dns_records\" --params '{\"zone_id\": \"ZONE_ID\"}'\n\n# List accounts\nclawlink_call_tool --tool \"cloudflare_list_accounts\" --params '{}'\n```\n\n## Authentication\n\nAll Cloudflare tool calls are authenticated automatically by ClawLink using the user's connected Cloudflare account.\n\n**No API token is required in chat.** ClawLink stores the API token securely and injects it into every Cloudflare API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=cloudflare and connect Cloudflare.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `cloudflare` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration cloudflare\n```\n\n**Response:** Returns the live tool catalog for Cloudflare.\n\n### Reconnect\n\nIf Cloudflare tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=cloudflare\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration cloudflare`\n\n## Security & Permissions\n\n- Access is scoped to the permissions granted by the Cloudflare API token.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete zone, delete DNS record, delete WAF list) are marked as high-impact and must be confirmed.\n\n## Tool Reference\n\n### Zones\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_zones` | List zones in the account with pagination | Read |\n| `cloudflare_create_zone` | Create a new DNS zone (domain) | Write |\n| `cloudflare_update_zone` | Update zone properties (one field at a time) | Write |\n| `cloudflare_delete_zone` | Permanently delete a zone and all DNS records | Write |\n\n### DNS Records\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_dns_records` | List and search DNS records in a zone | Read |\n| `cloudflare_create_dns_record` | Create a new DNS record in a zone | Write |\n| `cloudflare_update_dns_record` | Update an existing DNS record | Write |\n| `cloudflare_delete_dns_record` | Permanently delete a DNS record | Write |\n\n### Accounts & Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_accounts` | List all Cloudflare accounts accessible to the user | Read |\n| `cloudflare_list_account_members` | List account members with roles and permissions | Read |\n\n### Load Balancers\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_monitors` | List load balancer monitors | Read |\n| `cloudflare_list_pools` | List load balancer origin pools | Read |\n\n### WAF & Rules\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_firewall_rules` | List firewall rules for a zone | Read |\n| `cloudflare_create_list` | Create a WAF custom list (IPs, hostnames, ASNs) | Write |\n| `cloudflare_get_lists` | List all WAF lists | Read |\n| `cloudflare_update_list` | Update a WAF list description | Write |\n| `cloudflare_delete_list` | Delete a WAF list | Write |\n\n### Tunnels\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_tunnels` | List Cloudflare Tunnel tunnels | Read |\n| `cloudflare_update_tunnel_configuration` | Update tunnel ingress rules (replaces full config) | Write |\n\n### Bot Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_get_bot_management_settings` | Get bot management configuration for a zone | Read |\n\n## Code Examples\n\n### List zones\n\n```bash\nclawlink_call_tool --tool \"cloudflare_list_zones\" \\\n  --params '{}'\n```\n\n### Create a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_create_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"type\": \"A\",\n    \"name\": \"api\",\n    \"content\": \"192.0.2.1\",\n    \"ttl\": 3600\n  }'\n```\n\n### Update a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_update_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"dns_record_id\": \"RECORD_ID\",\n    \"type\": \"A\",\n    \"name\": \"api\",\n    \"content\": \"192.0.2.2\",\n    \"ttl\": 1800\n  }'\n```\n\n### Delete a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_delete_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"dns_record_id\": \"RECORD_ID\"\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Cloudflare is connected.\n2. Call `clawlink_list_tools --integration cloudflare` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `cloudflare`.\n5. If no Cloudflare tools appear, direct the user to https://claw-link.dev/dashboard?add=cloudflare.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  list → get → describe → call                              │\n│                                                             │\n│  Example: List zones → List DNS records → Show results      │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE OPERATIONS (Require Confirmation)                     │\n│  list → get → describe → preview → confirm → call         │\n│                                                             │\n│  Example: Describe tool → Preview changes → User approves   │\n│           → Execute update                                 │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Zone IDs and DNS record IDs are required for all zone-scoped operations — retrieve them via list tools first.\n- Pagination: use `page` and `per_page` parameters and check `result_info.total_pages` to iterate all pages.\n- Tunnel configuration updates replace the entire configuration — fetch the current config first to avoid losing existing rules.\n- WAF lists have plan-based limits (Free: 1 list, Pro/Business: 10 lists, Enterprise: 1000 lists).\n- DNS record updates only modify provided fields.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration cloudflare`. |\n| Missing connection | Cloudflare is not connected. Direct the user to https://claw-link.dev/dashboard?add=cloudflare. |\n| `zone_not_found` | Zone does not exist or is not accessible. |\n| `dns_record_not_found` | DNS record does not exist. |\n| `InvalidArgument` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `cloudflare`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Cloudflare API Documentation](https://developers.cloudflare.com/api/)\n- [Cloudflare DNS API](https://developers.cloudflare.com/api/operations/dns-records-for-a-zone)\n- [Cloudflare Zones API](https://developers.cloudflare.com/api/operations/zones)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [AWS](https://clawhub.ai/hith3sh/aws-infrastructure) — For AWS infrastructure management\n- [GitHub](https://clawhub.ai/hith3sh/github-repos) — For GitHub CI/CD and deployments\n- [Datadog](https://clawhub.ai/hith3sh/datadog-monitoring) — For observability and monitoring\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"cloudflare-infrastructure\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1780937125388\n}\n\nFile v1.0.2:skill-card.md\n\n## Description: <br>\nManage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and operators use this skill to inspect and manage Cloudflare infrastructure from an agent workflow, including zones, DNS records, workers, rules, firewall settings, account resources, and related Cloudflare API tasks. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Cloudflare API access can affect live infrastructure, including DNS, zones, WAF lists, tunnel configuration, and account resources. <br>\nMitigation: Use least-privilege Cloudflare API tokens, review previews carefully, and confirm exact zones, record IDs, and intended effects before allowing writes or deletes. <br>\nRisk: Destructive operations such as deleting zones, DNS records, or WAF lists can remove active resources. <br>\nMitigation: Require explicit user confirmation for write and destructive actions, and use read/list operations first to verify target resources. <br>\n\n\n## Reference(s): <br>\n- [Cloudflare API Documentation](https://developers.cloudflare.com/api/) <br>\n- [Cloudflare DNS API](https://developers.cloudflare.com/api/operations/dns-records-for-a-zone) <br>\n- [Cloudflare Zones API](https://developers.cloudflare.com/api/operations/zones) <br>\n- [ClawLink](https://claw-link.dev) <br>\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw) <br>\n- [ClawLink Verification](https://claw-link.dev/verify) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown with inline shell commands and JSON parameter examples] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [May propose Cloudflare API tool calls and configuration steps; write or destructive actions require explicit user confirmation.] <br>\n\n## Skill Version(s): <br>\n1.0.2 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.1: 3 files, 5555 bytes\n\nFiles: skill-card.md (2390b), SKILL.md (13571b), _meta.json (144b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: cloudflare-infrastructure\ndescription: Manage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. Use this skill when users want to inspect DNS records, manage zones, configure workers, or update firewall rules.\n---\n\n# Cloudflare\n\n![Cloudflare](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/cloudflare.svg)\n\nWork with Cloudflare from chat — manage zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API with API token authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Cloudflare API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Cloudflare |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Cloudflare |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│ Cloudflare API    │\n│   (User Chat)   │     │   (API Token)│     │ (Zones/DNS/APIs) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Cloudflare│                       │\n         │                       │  4. Secure Token      │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │ Cloudflare│\n   │  File    │           │ Auth     │           │ Dashboard│\n   └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Cloudflare again.\"\n\n## Quick Start\n\n```bash\n# List all zones\nclawlink_call_tool --tool \"cloudflare_list_zones\" --params '{}'\n\n# List DNS records in a zone\nclawlink_call_tool --tool \"cloudflare_list_dns_records\" --params '{\"zone_id\": \"ZONE_ID\"}'\n\n# List accounts\nclawlink_call_tool --tool \"cloudflare_list_accounts\" --params '{}'\n```\n\n## Authentication\n\nAll Cloudflare tool calls are authenticated automatically by ClawLink using the user's connected Cloudflare account.\n\n**No API token is required in chat.** ClawLink stores the API token securely and injects it into every Cloudflare API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=cloudflare and connect Cloudflare.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `cloudflare` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration cloudflare\n```\n\n**Response:** Returns the live tool catalog for Cloudflare.\n\n### Reconnect\n\nIf Cloudflare tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=cloudflare\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration cloudflare`\n\n## Security & Permissions\n\n- Access is scoped to the permissions granted by the Cloudflare API token.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete zone, delete DNS record, delete WAF list) are marked as high-impact and must be confirmed.\n\n## Tool Reference\n\n### Zones\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_zones` | List zones in the account with pagination | Read |\n| `cloudflare_create_zone` | Create a new DNS zone (domain) | Write |\n| `cloudflare_update_zone` | Update zone properties (one field at a time) | Write |\n| `cloudflare_delete_zone` | Permanently delete a zone and all DNS records | Write |\n\n### DNS Records\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_dns_records` | List and search DNS records in a zone | Read |\n| `cloudflare_create_dns_record` | Create a new DNS record in a zone | Write |\n| `cloudflare_update_dns_record` | Update an existing DNS record | Write |\n| `cloudflare_delete_dns_record` | Permanently delete a DNS record | Write |\n\n### Accounts & Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_accounts` | List all Cloudflare accounts accessible to the user | Read |\n| `cloudflare_list_account_members` | List account members with roles and permissions | Read |\n\n### Load Balancers\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_monitors` | List load balancer monitors | Read |\n| `cloudflare_list_pools` | List load balancer origin pools | Read |\n\n### WAF & Rules\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_firewall_rules` | List firewall rules for a zone | Read |\n| `cloudflare_create_list` | Create a WAF custom list (IPs, hostnames, ASNs) | Write |\n| `cloudflare_get_lists` | List all WAF lists | Read |\n| `cloudflare_update_list` | Update a WAF list description | Write |\n| `cloudflare_delete_list` | Delete a WAF list | Write |\n\n### Tunnels\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_tunnels` | List Cloudflare Tunnel tunnels | Read |\n| `cloudflare_update_tunnel_configuration` | Update tunnel ingress rules (replaces full config) | Write |\n\n### Bot Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_get_bot_management_settings` | Get bot management configuration for a zone | Read |\n\n## Code Examples\n\n### List zones\n\n```bash\nclawlink_call_tool --tool \"cloudflare_list_zones\" \\\n  --params '{}'\n```\n\n### Create a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_create_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"type\": \"A\",\n    \"name\": \"api\",\n    \"content\": \"192.0.2.1\",\n    \"ttl\": 3600\n  }'\n```\n\n### Update a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_update_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"dns_record_id\": \"RECORD_ID\",\n    \"type\": \"A\",\n    \"name\": \"api\",\n    \"content\": \"192.0.2.2\",\n    \"ttl\": 1800\n  }'\n```\n\n### Delete a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_delete_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"dns_record_id\": \"RECORD_ID\"\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Cloudflare is connected.\n2. Call `clawlink_list_tools --integration cloudflare` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `cloudflare`.\n5. If no Cloudflare tools appear, direct the user to https://claw-link.dev/dashboard?add=cloudflare.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  list → get → describe → call                              │\n│                                                             │\n│  Example: List zones → List DNS records → Show results      │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE OPERATIONS (Require Confirmation)                     │\n│  list → get → describe → preview → confirm → call         │\n│                                                             │\n│  Example: Describe tool → Preview changes → User approves   │\n│           → Execute update                                 │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Zone IDs and DNS record IDs are required for all zone-scoped operations — retrieve them via list tools first.\n- Pagination: use `page` and `per_page` parameters and check `result_info.total_pages` to iterate all pages.\n- Tunnel configuration updates replace the entire configuration — fetch the current config first to avoid losing existing rules.\n- WAF lists have plan-based limits (Free: 1 list, Pro/Business: 10 lists, Enterprise: 1000 lists).\n- DNS record updates only modify provided fields.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration cloudflare`. |\n| Missing connection | Cloudflare is not connected. Direct the user to https://claw-link.dev/dashboard?add=cloudflare. |\n| `zone_not_found` | Zone does not exist or is not accessible. |\n| `dns_record_not_found` | DNS record does not exist. |\n| `InvalidArgument` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `cloudflare`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Cloudflare API Documentation](https://developers.cloudflare.com/api/)\n- [Cloudflare DNS API](https://developers.cloudflare.com/api/operations/dns-records-for-a-zone)\n- [Cloudflare Zones API](https://developers.cloudflare.com/api/operations/zones)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [AWS](https://clawhub.ai/hith3sh/aws-infrastructure) — For AWS infrastructure management\n- [GitHub](https://clawhub.ai/hith3sh/github-repos) — For GitHub CI/CD and deployments\n- [Datadog](https://clawhub.ai/hith3sh/datadog-monitoring) — For observability and monitoring\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v1.0.1:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"cloudflare-infrastructure\",\n  \"version\": \"1.0.1\",\n  \"publishedAt\": 1780936015575\n}\n\nFile v1.0.1:skill-card.md\n\n## Description: <br>\nManage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and infrastructure operators use this skill to inspect and manage Cloudflare zones, DNS records, workers, rules, firewall settings, tunnels, and account resources from an agent chat workflow. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Cloudflare account, DNS, zone, tunnel, WAF, or firewall changes can affect live infrastructure. <br>\nMitigation: Use a least-privilege Cloudflare API token, preview changes, and confirm the target resource and intended effect before allowing writes. <br>\nRisk: Destructive Cloudflare operations can permanently remove zones, DNS records, or WAF lists. <br>\nMitigation: Require explicit confirmation for destructive actions and verify current resource IDs with read operations before execution. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/cloudflare-infrastructure) <br>\n- [Publisher Profile](https://clawhub.ai/user/hith3sh) <br>\n- [Cloudflare API Documentation](https://developers.cloudflare.com/api/) <br>\n- [Cloudflare DNS API](https://developers.cloudflare.com/api/operations/dns-records-for-a-zone) <br>\n- [Cloudflare Zones API](https://developers.cloudflare.com/api/operations/zones) <br>\n- [ClawLink](https://claw-link.dev) <br>\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown with inline bash commands and tool-call examples] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Cloudflare write operations require explicit user confirmation before execution.] <br>\n\n## Skill Version(s): <br>\n1.0.1 (source: server-resolved release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v0.1.1: 3 files, 5786 bytes\n\nFiles: skill-card.md (2907b), SKILL.md (13454b), _meta.json (144b)\n\nFile v0.1.1:SKILL.md\n\n---\nname: cloudflare-infrastructure\ndescription: Manage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. Use this skill when users want to inspect DNS records, manage zones, configure workers, or update firewall rules.\n---\n\n# Cloudflare\n\nWork with Cloudflare from chat — manage zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API with API token authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Cloudflare API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Cloudflare |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Cloudflare |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│ Cloudflare API    │\n│   (User Chat)   │     │   (API Token)│     │ (Zones/DNS/APIs) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Cloudflare│                       │\n         │                       │  4. Secure Token      │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │ Cloudflare│\n   │  File    │           │ Auth     │           │ Dashboard│\n   └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Cloudflare again.\"\n\n## Quick Start\n\n```bash\n# List all zones\nclawlink_call_tool --tool \"cloudflare_list_zones\" --params '{}'\n\n# List DNS records in a zone\nclawlink_call_tool --tool \"cloudflare_list_dns_records\" --params '{\"zone_id\": \"ZONE_ID\"}'\n\n# List accounts\nclawlink_call_tool --tool \"cloudflare_list_accounts\" --params '{}'\n```\n\n## Authentication\n\nAll Cloudflare tool calls are authenticated automatically by ClawLink using the user's connected Cloudflare account.\n\n**No API token is required in chat.** ClawLink stores the API token securely and injects it into every Cloudflare API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=cloudflare and connect Cloudflare.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `cloudflare` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration cloudflare\n```\n\n**Response:** Returns the live tool catalog for Cloudflare.\n\n### Reconnect\n\nIf Cloudflare tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=cloudflare\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration cloudflare`\n\n## Security & Permissions\n\n- Access is scoped to the permissions granted by the Cloudflare API token.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete zone, delete DNS record, delete WAF list) are marked as high-impact and must be confirmed.\n\n## Tool Reference\n\n### Zones\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_zones` | List zones in the account with pagination | Read |\n| `cloudflare_create_zone` | Create a new DNS zone (domain) | Write |\n| `cloudflare_update_zone` | Update zone properties (one field at a time) | Write |\n| `cloudflare_delete_zone` | Permanently delete a zone and all DNS records | Write |\n\n### DNS Records\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_dns_records` | List and search DNS records in a zone | Read |\n| `cloudflare_create_dns_record` | Create a new DNS record in a zone | Write |\n| `cloudflare_update_dns_record` | Update an existing DNS record | Write |\n| `cloudflare_delete_dns_record` | Permanently delete a DNS record | Write |\n\n### Accounts & Members\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_accounts` | List all Cloudflare accounts accessible to the user | Read |\n| `cloudflare_list_account_members` | List account members with roles and permissions | Read |\n\n### Load Balancers\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_monitors` | List load balancer monitors | Read |\n| `cloudflare_list_pools` | List load balancer origin pools | Read |\n\n### WAF & Rules\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_firewall_rules` | List firewall rules for a zone | Read |\n| `cloudflare_create_list` | Create a WAF custom list (IPs, hostnames, ASNs) | Write |\n| `cloudflare_get_lists` | List all WAF lists | Read |\n| `cloudflare_update_list` | Update a WAF list description | Write |\n| `cloudflare_delete_list` | Delete a WAF list | Write |\n\n### Tunnels\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_list_tunnels` | List Cloudflare Tunnel tunnels | Read |\n| `cloudflare_update_tunnel_configuration` | Update tunnel ingress rules (replaces full config) | Write |\n\n### Bot Management\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `cloudflare_get_bot_management_settings` | Get bot management configuration for a zone | Read |\n\n## Code Examples\n\n### List zones\n\n```bash\nclawlink_call_tool --tool \"cloudflare_list_zones\" \\\n  --params '{}'\n```\n\n### Create a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_create_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"type\": \"A\",\n    \"name\": \"api\",\n    \"content\": \"192.0.2.1\",\n    \"ttl\": 3600\n  }'\n```\n\n### Update a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_update_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"dns_record_id\": \"RECORD_ID\",\n    \"type\": \"A\",\n    \"name\": \"api\",\n    \"content\": \"192.0.2.2\",\n    \"ttl\": 1800\n  }'\n```\n\n### Delete a DNS record\n\n```bash\nclawlink_call_tool --tool \"cloudflare_delete_dns_record\" \\\n  --params '{\n    \"zone_id\": \"ZONE_ID\",\n    \"dns_record_id\": \"RECORD_ID\"\n  }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Cloudflare is connected.\n2. Call `clawlink_list_tools --integration cloudflare` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `cloudflare`.\n5. If no Cloudflare tools appear, direct the user to https://claw-link.dev/dashboard?add=cloudflare.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│  READ OPERATIONS (Safe)                                     │\n│  list → get → describe → call                              │\n│                                                             │\n│  Example: List zones → List DNS records → Show results      │\n└─────────────────────────────────────────────────────────────┘\n                              │\n                              ▼\n┌─────────────────────────────────────────────────────────────┐\n│  WRITE OPERATIONS (Require Confirmation)                     │\n│  list → get → describe → preview → confirm → call         │\n│                                                             │\n│  Example: Describe tool → Preview changes → User approves   │\n│           → Execute update                                 │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Zone IDs and DNS record IDs are required for all zone-scoped operations — retrieve them via list tools first.\n- Pagination: use `page` and `per_page` parameters and check `result_info.total_pages` to iterate all pages.\n- Tunnel configuration updates replace the entire configuration — fetch the current config first to avoid losing existing rules.\n- WAF lists have plan-based limits (Free: 1 list, Pro/Business: 10 lists, Enterprise: 1000 lists).\n- DNS record updates only modify provided fields.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration cloudflare`. |\n| Missing connection | Cloudflare is not connected. Direct the user to https://claw-link.dev/dashboard?add=cloudflare. |\n| `zone_not_found` | Zone does not exist or is not accessible. |\n| `dns_record_not_found` | DNS record does not exist. |\n| `InvalidArgument` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n   ```bash\n   openclaw plugins list\n   ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n   ```bash\n   openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n   openclaw gateway restart\n   ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `cloudflare`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Cloudflare API Documentation](https://developers.cloudflare.com/api/)\n- [Cloudflare DNS API](https://developers.cloudflare.com/api/operations/dns-records-for-a-zone)\n- [Cloudflare Zones API](https://developers.cloudflare.com/api/operations/zones)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [AWS](https://clawhub.ai/hith3sh/aws-infrastructure) — For AWS infrastructure management\n- [GitHub](https://clawhub.ai/hith3sh/github-repos) — For GitHub CI/CD and deployments\n- [Datadog](https://clawhub.ai/hith3sh/datadog-monitoring) — For observability and monitoring\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n![ClawLink Logo](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/logo/link_logo_black_small.png)\n\nFile v0.1.1:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"cloudflare-infrastructure\",\n  \"version\": \"0.1.1\",\n  \"publishedAt\": 1780838868668\n}\n\nFile v0.1.1:skill-card.md\n\n## Description: <br>\nManage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, site reliability engineers, and operators use this skill in OpenClaw to inspect and manage Cloudflare infrastructure through ClawLink-authenticated Cloudflare tools. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Cloudflare access depends on a ClawLink-managed credential broker and the permissions granted to the connected Cloudflare API token. <br>\nMitigation: Before installing, confirm trust in ClawLink and connect a Cloudflare token with only the minimum permissions needed. <br>\nRisk: DNS, firewall, tunnel, zone, and account changes can affect production infrastructure. <br>\nMitigation: Review previews carefully and approve only changes that exactly match the intended target resource and effect. <br>\nRisk: The available Cloudflare tools and schemas can differ from assumptions in the skill text. <br>\nMitigation: Use the live ClawLink catalog and tool descriptions before selecting or executing Cloudflare operations. <br>\nRisk: Tunnel configuration updates replace the full configuration and can remove existing ingress rules. <br>\nMitigation: Fetch the current tunnel configuration before updating and preserve required existing rules in the replacement configuration. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/cloudflare-infrastructure) <br>\n- [Cloudflare API Documentation](https://developers.cloudflare.com/api/) <br>\n- [Cloudflare DNS Records API](https://developers.cloudflare.com/api/operations/dns-records-for-a-zone) <br>\n- [Cloudflare Zones API](https://developers.cloudflare.com/api/operations/zones) <br>\n- [ClawLink](https://claw-link.dev) <br>\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw) <br>\n- [ClawLink Verification](https://claw-link.dev/verify) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Shell commands, Configuration, API Calls] <br>\n**Output Format:** [Markdown with inline bash code blocks and JSON tool parameters] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Write and destructive Cloudflare operations require explicit user confirmation; the live ClawLink tool catalog is treated as the source of truth.] <br>\n\n## Skill Version(s): <br>\n0.1.1 (source: ClawHub release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v0.1.0: 3 files, 3649 bytes\n\nFiles: skill-card.md (2886b), SKILL.md (5049b), _meta.json (144b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: cloudflare-infrastructure\ndescription: Manage Cloudflare zones, DNS, workers, rules, firewall settings, and account resources - powered by ClawLink.\n---\n\n# Cloudflare\n\nWork with Cloudflare from chat - manage zones, DNS records, workers, rules, firewall settings, and account resources.\n\nPowered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Cloudflare API access yourself.\n\n## Quick start\n\n1. Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`\n2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet\n3. If ClawLink is not configured, call `clawlink_begin_pairing`\n4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device\n5. After the user confirms approval, call `clawlink_get_pairing_status`\n6. Tell the user to connect Cloudflare at [claw-link.dev/dashboard?add=cloudflare](https://claw-link.dev/dashboard?add=cloudflare)\n7. When the user confirms Cloudflare is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `cloudflare` integration slug\n\n## Setup details\n\n### Installing the plugin\n\nIf the ClawLink plugin is not installed yet, tell the user to run:\n\n```\nopenclaw plugins install clawhub:clawlink-plugin\n```\n\nIf the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog.\n\n### Pairing ClawLink\n\nIf ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet.\n\n1. Call `clawlink_begin_pairing`.\n2. Tell the user to open the returned pairing URL in their browser.\n3. The user signs in to ClawLink if needed and approves the OpenClaw device.\n4. After the user confirms approval, call `clawlink_get_pairing_status` to finish local setup.\n\nThe resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`. The user should not paste raw credentials into chat.\n\n### Connecting Cloudflare\n\nTell the user to open https://claw-link.dev/dashboard?add=cloudflare and connect Cloudflare there. The page opens the add-connection panel filtered to Cloudflare. ClawLink's hosted page runs the provider connection flow. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `cloudflare`.\n\n## Using Cloudflare tools\n\nClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance.\n\n### Discovery\n\n1. Call `clawlink_list_integrations` to confirm Cloudflare is connected.\n2. Call `clawlink_list_tools` with integration `cloudflare`.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `cloudflare`.\n5. If no Cloudflare tools appear, direct the user to https://claw-link.dev/dashboard?add=cloudflare.\n\n### Execution\n\n1. Call `clawlink_describe_tool` before using an unfamiliar tool, before any write, or when the request is ambiguous.\n2. Use the returned schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups`.\n3. Prefer read, list, search, and get operations before writes.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user.\n5. Execute with `clawlink_call_tool`.\n6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## What you can do\n\nTypical Cloudflare tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):\n\n- List accounts, zones, and DNS records\n- Inspect zone settings and security configuration\n- Create or update DNS records after confirmation\n- Manage rules, workers, and firewall settings when available\n- Review analytics or logs exposed by the live catalog\n\n## Rules\n\n- Always use ClawLink tools for Cloudflare. Do not ask the user for separate Cloudflare credentials.\n- Do not claim a capability is missing without checking the live ClawLink catalog in the current turn.\n- Do not invent slash commands or ask the user to paste raw credentials.\n- Ask for confirmation before destructive, external-facing, or bulk write actions.\n- If Cloudflare is not connected, direct the user to https://claw-link.dev/dashboard?add=cloudflare.\n- Never echo or repeat the user's ClawLink credential.\n\n## Resources\n\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n- ClawLink Source: https://github.com/hith3sh/clawlink\n- Cloudflare API: https://developers.cloudflare.com/api/\n\nFile v0.1.0:_meta.json\n\n{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"cloudflare-infrastructure\",\n  \"version\": \"0.1.0\",\n  \"publishedAt\": 1778945631865\n}\n\nFile v0.1.0:skill-card.md\n\n## Description: <br>\nManage Cloudflare zones, DNS, workers, rules, firewall settings, and account resources - powered by ClawLink. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[hith3sh](https://clawhub.ai/user/hith3sh) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers and operators use this skill to connect an OpenClaw chat session to Cloudflare through ClawLink, discover available Cloudflare tools, and manage account resources such as zones, DNS records, workers, rules, and firewall settings. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Cloudflare operations can affect public DNS, workers, firewall rules, and other account resources. <br>\nMitigation: Use the narrowest practical Cloudflare permissions and require previews plus user confirmation before DNS, firewall, worker, destructive, external-facing, or bulk changes. <br>\nRisk: The skill depends on ClawLink for account access and tool execution. <br>\nMitigation: Install only if the user trusts the ClawLink plugin and service with the intended Cloudflare account, and verify the connected integration before use. <br>\nRisk: The available Cloudflare tools vary by connected account, permissions, scopes, and the current ClawLink catalog. <br>\nMitigation: List, search, and describe live ClawLink tools before execution, and do not claim a capability is missing without checking the current catalog. <br>\nRisk: Raw credentials or device credentials could be exposed if repeated in chat. <br>\nMitigation: Use the ClawLink pairing flow and never ask users to paste Cloudflare credentials or echo ClawLink credentials. <br>\n\n\n## Reference(s): <br>\n- [ClawLink](https://claw-link.dev) <br>\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw) <br>\n- [ClawLink Verification](https://claw-link.dev/verify) <br>\n- [ClawLink Source](https://github.com/hith3sh/clawlink) <br>\n- [Cloudflare API](https://developers.cloudflare.com/api/) <br>\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/cloudflare-infrastructure) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Shell commands, API calls, Configuration] <br>\n**Output Format:** [Markdown with inline shell commands and tool-call guidance] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Uses the live ClawLink Cloudflare tool catalog as the source of truth and asks for confirmation before destructive, external-facing, or bulk write actions.] <br>\n\n## Skill Version(s): <br>\n0.1.0 (source: server release metadata) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>","readmeExcerpt":"Skill: Cloudflare Owner: hith3sh Summary: Manage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. Use this skill when users want to insp... Tags: clawlink:0.1.0, integration:0.1.0, latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:05:30.130Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page a","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│ Cloudflare API    │\n│   (User Chat)   │     │   (API Token)│     │ (Zones/DNS/APIs) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Cloudflare│                       │\n         │                       │  4. Secure Token      │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │ Cloudflare│\n   │  File    │           │ Auth     │           │ Dashboard│\n   └──────────┘           └──────────┘           └──────────┘"},{"language":"bash","snippet":"openclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart"},{"language":"bash","snippet":"# List all zones\nclawlink_call_tool --tool \"cloudflare_list_zones\" --params '{}'\n\n# List DNS records in a zone\nclawlink_call_tool --tool \"cloudflare_list_dns_records\" --params '{\"zone_id\": \"ZONE_ID\"}'\n\n# List accounts\nclawlink_call_tool --tool \"cloudflare_list_accounts\" --params '{}'"},{"language":"bash","snippet":"clawlink_list_integrations"},{"language":"bash","snippet":"clawlink_list_tools --integration cloudflare"},{"language":"bash","snippet":"clawlink_call_tool --tool \"cloudflare_list_zones\" \\\n  --params '{}'"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: cloudflare-infrastructure\ndescription: Manage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. Use this skill when users want to inspect DNS records, manage zones, configure workers, or update firewall rules.\n---\n\n# Cloudflare\n\n![Cloudflare](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/brand-logos/cloudflare.svg?v=2)\n\nWork with Cloudflare from chat — manage zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API with API token authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=cloudflare-infrastructure) for hosted connection flows and credentials so you do not need to configure Cloudflare API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Cloudflare |\n|:---:|:---:|:---:|\n| ![Install](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/pairing/initialstep_1.gif) | ![Pair](https://raw.githubusercontent.com/ClawLink-HQ/clawlink/main/public/images/approve_process.gif) | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Cloudflare |\n\n## How It Works\n\n```\n┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐\n│   OpenClaw      │────▶│   ClawLink   │────▶│ Cloudflare API    │\n│   (User Chat)   │     │   (API Token)│     │ (Zones/DNS/APIs) │\n└─────────────────┘     └──────────────┘     └──────────────────┘\n         │                       │                       │\n         │  1. Install Plugin    │                       │\n         │  2. Pair Device       │                       │\n         │  3. Connect Cloudflare│                       │\n         │                       │  4. Secure Token      │\n         │                       │  5. Proxy Requests    │\n         │                       │                       │\n         ▼                       ▼                       ▼\n   ┌──────────┐           ┌──────────┐           ┌──────────┐\n   │  SKILL   │           │ Dashboard│           │ Cloudflare│\n   │  File    │           │ Auth     │           │ Dashboard│\n   └──────────┘           └──────────┘           └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Cloudflare again.\"\n\n## Quick Start\n\n```bash\n# List all zones\nclawlink_call_tool --tool \"cloudflare_list_zones\" --params '{}'\n\n# List DNS records in a zone\nclawlink_call_tool --tool \"cloudflare_list_dns_records"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n  \"slug\": \"cloudflare-infrastructure\",\n  \"version\": \"1.0.6\",\n  \"publishedAt\": 1780988730130\n}"},{"path":"skill-card.md","content":"## Description:\n\nManage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and operators use this skill from OpenClaw to inspect and manage Cloudflare infrastructure, including zones, DNS records, account resources, workers, rules, firewall settings, WAF lists, tunnels, and related Cloudflare API resources.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill manages high-impact Cloudflare infrastructure through a third-party ClawLink plugin that stores and uses Cloudflare credentials.\n\nMitigation: Install only if the publisher and ClawLink are trusted, use the narrowest Cloudflare permissions possible, and revoke the Cloudflare connection when it is no longer needed.\n\nRisk: Write operations can create, update, or delete zones, DNS records, WAF lists, tunnel configuration, and other account resources.\n\nMitigation: Confirm the target resource and intended effect before every write, preview tool calls where supported, and prefer read/list/describe operations before changes.\n\nRisk: Tunnel configuration updates replace the full configuration and can unintentionally remove existing ingress rules.\n\nMitigation: Fetch and review the current tunnel configuration before applying an update, then confirm that the preview preserves required rules.\n\n## Reference(s):\n\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/cloudflare-infrastructure)\n- [Cloudflare API Documentation](https://developers.cloudflare.com/api/)\n- [Cloudflare DNS API](https://developers.cloudflare.com/api/operations/dns-records-for-a-zone)\n- [Cloudflare Zones API](https://developers.cloudflare.com/api/operations/zones)\n- [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=cloudflare-infrastructure)\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)\n- [ClawLink Verification](https://claw-link.dev/verify)\n\n## Skill Output:\n\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]\n\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include Cloudflare tool names, preview guidance, confirmation prompts, and troubleshooting steps.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Manage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. Use this skill when users want to insp... Skill: Cloudflare Owner: hith3sh Summary: Manage Cloudflare zones, DNS records, workers, rules, firewall settings, and account resources via the Cloudflare API. Use this skill when users want to insp... Tags: clawlink:0.1.0, integration:0.1.0, latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:05:30.130Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page a","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1027,"uniquenessScore":51,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T10:36:47.760Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T10:36:47.760Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:57:18.676Z","emptyReason":null},"items":[{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-10T18:48:31.762Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}