cloudshare
Share a local file (HTML, image, PDF, or directory) as a token-gated URL on
the user's personal Cloudflare Pages subdomain.
When to use this skill
- User asks to share a local file or directory
- User wants a private link with token gating
- User mentions "Cloudflare Pages", "shareable URL", or "publish this"
- User asks to manage past shares: list, delete, rotate token
Architecture (one-liner)
One Cloudflare Pages project per user (chosen at first-run setup). Each share
lands at
under that project, with its own random token stored in
the project's
env var. Middleware validates the token
before serving any path under
.
Companion scripts (in this skill's dir)
- — share a file or directory
- — list past shares
- — delete one share
- — rotate token on one share
resources/lib/{auth,tokens,clipboard}.sh
- — reference templates (already copied into user's mirror at setup time)
When invoking these scripts, use the absolute path of the skill directory.
Different agents place skills in different locations — locate this SKILL.md
file and resolve relative paths from its directory.
First-run setup is run by the user, not the agent
The setup wizard is interactive (token paste, account selection, project
name pick) and lives at the repo root, decoupled from the skill install
path. Do not try to run it from inside the agent — it requires a real TTY.
If
~/.config/cloudshare/config.env
does not exist (the share scripts will
return exit code 2 with a clear message), tell the user to paste this into
their terminal:
curl -fsSL https://raw.githubusercontent.com/alanho/cloudshare-skills/main/setup.sh | bash
The setup script will:
- Prompt for a Cloudflare API token (custom token with
Account: Cloudflare Pages: Edit
Account: Account Settings: Read
- Detect the account (or prompt to pick if multiple).
- Suggest a friendly subdomain (e.g. ); user can accept or override.
- Create the Cloudflare Pages project, initialize the local mirror at
~/.config/cloudshare/projects/<name>/
- Save credentials to
~/.config/cloudshare/config.env
After setup, all shares from any agent (Claude Code, Codex, OpenCode, etc.)
read the same
~/.config/cloudshare/config.env
and target the same project.
Prerequisites check
Before invoking any share script, optionally verify:
bash
command -v openssl >/dev/null || { echo "openssl required"; exit 1; }
command -v node >/dev/null || { echo "node required (https://nodejs.org/)"; exit 1; }
command -v curl >/dev/null || { echo "curl required"; exit 1; }
is invoked via
— no global install needed.
Share workflow
bash
bash <SKILL_DIR>/resources/deploy.sh <absolute-path-to-file-or-dir>
The script:
- Loads config from
~/.config/cloudshare/config.env
- If config missing, exits 2 with a setup instruction. Relay the setup
command verbatim to the user.
- Generates a slug from the filename (e.g. ).
- Generates a 32-hex-char token.
- Stages content into the local mirror.
- Updates via the Cloudflare API.
- Redeploys via
npx wrangler@latest pages deploy
- Prints the canonical URL on a single line starting with :
URL: https://<project>.pages.dev/r/<slug>/?token=<hex>
- Copies URL to clipboard.
- Appends to
~/.config/cloudshare/shares.log
After running, present the URL prominently. Mention the clipboard copy. Note
that anyone with the URL has access — treat it like a password.
Subcommands
bash
bash <SKILL_DIR>/resources/list.sh # list past shares
bash <SKILL_DIR>/resources/delete.sh <slug> # revoke + delete a share
bash <SKILL_DIR>/resources/rotate.sh <slug> # rotate token; old → 401
All three exit 2 with the same setup instruction if config is missing.
Output format
Lead with the URL on its own line, then a short success block. Example:
https://purple-tiger-42.pages.dev/r/trip-options-9f3a/?token=4b7c8d2e1a9f1234
✓ Shared `trip-options.html` (copied to clipboard).
Limits and security
- Cloudflare Pages free tier: 500 deploys / month, 25 MB / file, 100 MB / deploy total.
- Each share is gated by a unique random token in the URL query string.
Referrer-Policy: no-referrer
- Whoever has the URL has access. The link is the credential.
- To revoke: (URL → 404) or (URL → 401, new URL printed).
Common failure modes
- Scripts exit 2 with "not set up yet" → user has not run the curl-pipe setup. Ask them to.
- Token verification fails during setup → user pasted a token without correct scopes; instruct them to recreate at https://dash.cloudflare.com/profile/api-tokens.
- Project name taken → wizard loops, ask user for a different name.
- Source > 90 MB → Cloudflare's per-deploy limit. Ask user to slim the input.
- env var update returns 5xx → Cloudflare API hiccup; retry once before surfacing.
- fails → check that the API token has , not just Read.