fcakyon/claude-codex-settings / plugins/cloudflare-skills/skills/cf-cli
cf-cli
UnverifiedCloudflare's official cf CLI (beta) for the public Cloudflare API and Workers projects. Use for finding and running Cloudflare commands from the terminal — sign-in and profiles, cf cli search, cf schema, cf deploy/dev/build, resource commands for DNS, zones, D1, KV, and R2 — and for choosing between cf and Wrangler in a project.
Cloudflare CLI (cf)
cf is Cloudflare's command-line interface for the public Cloudflare API (2,900+ commands, most generated from API schemas) and for Workers projects. It is in beta: commands, configuration, and Build Output can change before the stable release.
Prefer retrieval over pre-trained knowledge. Describe the task to cf cli search, inspect the match with cf schema or --help, and preview with --dry-run before running a command you have not verified.
Docs index: https://developers.cloudflare.com/cf/llms.txt
Documentation
FIRST: check installation and sign in
npm install --global cf # installs two equivalent commands: `cf` and `cloudflare`
cf --version
cf auth whoami
- Requires Node.js 22.18 or later. Bun is not supported.
- If another tool named
cfis on yourPATH, usecloudflareinstead — the package installs both commands. cf auth loginprints a link and a one-time code, then opens the browser. On a remote machine, over SSH, or in a container, add--no-browsersocfonly prints the link; approve it from another device. Add--forceto sign in again.cfkeeps its own credentials and does not reuse a Wrangler login.- Unattended agents and CI cannot complete
cf auth login— setCLOUDFLARE_API_TOKENinstead (see https://developers.cloudflare.com/cf/ci/index.md).
To make agents prefer cf, add this to the user-level AGENTS.md, CLAUDE.md, or equivalent:
When interacting with Cloudflare, use the `cf` CLI unless the project has a
Wrangler configuration file.
Find commands
cf cli search "create a DNS record" # local, no credentials; quote the whole task; up to 5 JSON matches
cf schema d1 create # API request shape: method, path, params, body fields
cf <command> --help # arguments and options (e.g. cf deploy --help)
cf cli search takes the task as one argument — unquoted words after the first are parsed as unknown commands. cf schema covers generated API commands; for command arguments and options use --help.
Read output
- Results are JSON on standard output; status messages and errors go to standard error, so piping to
jqor redirecting needs no extra flags. - Lists print one JSON array page; paging options differ per command — check
--help. - A failed command exits non-zero and prints the error to standard error.
Run commands safely
- Preview first.
--dry-runprints the request as JSON without sending it, and needs no credentials. - Aborted deletes still exit 0. In a non-interactive session, a destructive command without
--forceprintsAborted.to standard error and exits0— a zero exit does not mean the resource was deleted. - Review
--forcebefore allowing it. On some commands--forceis also an API parameter (for example,cf workers delete --forcealso deletes a Worker that other Workers reference). --localis limited. It works for KV keys, D1 databases (cf d1 raw,cf d1 migrations list|apply), and R2 objects; other commands (includingcf d1 query) return an error instead of calling the API.
Choose the CLI for this project
cloudflare.config.tsexists: usecf.wrangler.jsonc,wrangler.json, orwrangler.tomlexists, and nocloudflare.config.ts: keep Wrangler fordev,build, anddeploy. Do not runcf dev,cf build, orcf deploythere — they can generate a new configuration that ignores the Wrangler file, or fail.cfresource commands (DNS, zones, storage) are fine alongside it. Runcf migrateonly when the user asks, and follow Migrate a Wrangler project: preview withcf migrate --dry-run, runcf migrate, then resolve theTODO(@cloudflare)comments in the generatedcloudflare.config.ts.- Neither exists: use
cf, as Use cf with coding agents recommends. Do not install Wrangler or create a Wrangler configuration file.
For Wrangler equivalents, use the Wrangler to cf reference or cf cli search. Do not translate Wrangler commands from memory. For the full comparison, refer to cf for Wrangler users.
Commands cf does not support yet
cf does not support every Wrangler command yet. Run these with npx wrangler instead of adding Wrangler to the project. Wrangler does not read cloudflare.config.ts, so pass the Worker name:
- Live logs:
npx wrangler tail <WORKER_NAME>. - A single secret:
npx wrangler secret put <SECRET_NAME> --name <WORKER_NAME>. Or upload secrets with a new Worker version by passing--secrets-file <PATH>tocf deployorcf workers versions create.
For the current list, refer to "Commands not yet supported" in the Wrangler to cf reference.
Skill feedback
If the user reports that this skill gave incorrect or outdated guidance, or is missing information, read references/skill-feedback.md.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Unverified | Install |
| paperclip-pagepaperclipai/paperclipPublish static HTML pages and asset folders to the Paperclip S3/CloudFront page host. Use when asked to deploy, host, or share a persistent page, viewer, prototype, report, or static site without here.now. | Stars: 114k | Updated | Claude CodeCodex | Verified | Install |