cloudflare-workers-publish_skill

This skill deploys static HTML to Cloudflare Workers using 1Password for credentials, enabling seamless, secure static site hosting.

TypeScript

14

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill terrylica/cc-skills --skill cloudflare-workers-publish

SKILL.md12.0 KB

Overview

This skill deploys static HTML files to Cloudflare Workers using the Static Assets feature and manages Cloudflare credentials via 1Password. It is designed for static-only sites (workers.dev) such as Bokeh charts, dashboards, and large HTML reports. The workflow automates credential retrieval, wrangler deploy, and basic deploy hygiene for reproducible static hosting. Dynamic Workers, R2, and custom domains are intentionally out of scope.

How this skill works

The skill reads Cloudflare account ID and API token from a pre-provisioned 1Password item and exports them as CLOUDFLARE_ACCOUNT_ID and CLOUDFLARE_API_TOKEN environment variables. It runs npx wrangler deploy from a configured publish directory that contains a minimal wrangler.toml and static assets. Deploy scripts auto-generate an index.html, verify common failure modes, and return the workers.dev URL discovered via wrangler output.

When to use it

Publish large static HTML outputs (charts, dashboards, reports) to a public workers.dev URL
Bootstrap a new Cloudflare Workers static site with repeatable scripts and task wrappers
Add or update static files in an existing published site and redeploy
Rotate Cloudflare API tokens centrally using 1Password
Troubleshoot failed static deploys with focused checks (wrangler.toml, credentials, LFS)

Best practices

Pre-provision the 1Password item manually (service accounts can only read items)
Keep wrangler.toml minimal: name, compatibility_date, and [assets] directory
Store only account_id (text) and credential (concealed, revealed with --reveal) in 1Password
Verify workers.dev subdomain is enabled in Cloudflare dashboard before first deploy
Use git LFS for very large HTML files and run git lfs pull before deploy
Keep deploy logic in standalone bash scripts and call them from a mise task

Example use cases

First-time setup: create API token, provision 1Password item, create publish dir and deploy script
Add files: copy generated HTML into results/published/... and run the deploy script to publish
New worker/project: create a new wrangler.toml, parameterize a deploy script, deploy and record the workers.dev URL
Rotate token: update the credential in 1Password, run deploy to validate, then revoke the old token

FAQ

No. This skill is intentionally static-only. It does not manage dynamic Worker scripts, R2 storage, or custom domain setups.

What 1Password permissions are required?

The skill requires read access to a pre-created 1Password item. Use a manual or biometric flow to create the item; the service account only needs read permission at runtime.

How do I discover my workers.dev URL?

Workers dev slugs are discovered at deploy time. Run npx wrangler whoami or inspect wrangler output after deploy; the subdomain is not predictable in advance.