cloudflare-wrangler_skill

Overview

This skill manages Cloudflare Workers, KV, D1, R2, and secrets using the Wrangler CLI. It centralizes common wrangler commands, R2 configuration patterns, lifecycle rules, and Pages deployment tips to streamline development and deployment workflows. Use it to deploy workers, manage storage and databases, tail logs, and handle secrets safely.

How this skill works

The skill documents how to authenticate Wrangler with an API token and where credentials are stored (~/.openclaw/secrets.json). It provides concrete wrangler CLI commands for worker lifecycle, KV namespaces, D1 databases and migrations, R2 object storage and presigned URLs, secrets management, queues, and Pages deployments. It also explains config file precedence (JSON vs TOML) and common troubleshooting steps.

When to use it

• Deploy or rollback Cloudflare Workers and tail live logs during incidents.
• Manage KV namespaces and perform bulk key operations for caching or feature flags.
• Provision and run D1 databases, run migrations, export backups, or execute SQL locally.
• Store, lifecycle-manage, and generate presigned URLs for objects in R2.
• Configure Pages deployments when wrangler auth is limited or a direct API upload is required.

Best practices

• Store Cloudflare tokens and R2 credentials in ~/.openclaw/secrets.json and export CLOUDFLARE_API_TOKEN for CLI use.
• Choose one config format (wrangler.json/jsonc OR wrangler.toml); JSON takes precedence if both exist.
• Use R2 lifecycle rules to auto-delete short-lived uploads (minimum granularity is 1 day).
• Keep Node.js updated to v20+ for Wrangler compatibility and use npx wrangler for project-scoped installs.
• Set secrets with wrangler secret put (or bulk upload from JSON) rather than embedding sensitive values in config files.

Example use cases

• Deploy a production worker and immediately tail logs to verify runtime behavior.
• Create a KV namespace for session data and bulk-load initial keys from JSON.
• Create a D1 database, apply migrations, and export a backup before a schema change.
• Upload user file to R2, generate a short presigned URL for download, and rely on lifecycle rules to auto-clean.
• Deploy a static site to Pages using env vars and direct multipart upload when wrangler auth fails.