Temporary shares

slew share publishes a throwaway page to an expiring URL — no project, no setup, no cleanup. It exists for pages that don't deserve a project: an HTML plan a coding agent just wrote, a one-off report, a prototype for a colleague.

slew share plan.html
slew ──┐ sharing plan.html
          └────
Shared 1 file at https://quiet-harbor-lantern.slew.cloud
Expires Fri, 17 Jul 2026 22:01:36 GMT.

Usage

Command	Effect
slew share <file>	Publish a single file, served as index.html at /
slew share <directory>	Publish a whole static build
slew share <path> --ttl <days>	Expire after 1–30 days (default 7)
slew share <path> --password <pw>	Gate the share behind a password
slew shares	List your live shares with their expiry
slew shares rm <name-or-url>	Delete a share now — the URL stops serving immediately

A share behaves like any deployed site — CDN, TLS, immutable asset caching — until it expires. Expired shares stop serving immediately and a background reaper deletes their files and records within the hour. There is nothing to clean up manually — but if a page should disappear sooner than its TTL, delete it with slew shares rm (the URL or the three-word name both work) or the Delete button in the web console.

Naming

Shares get generated three-word names like quiet-harbor-lantern.slew.cloud: easy to read aloud and retype, with enough combinations that a URL is effectively unlisted. Treat the URL as a shareable link, not a secret — put nothing on a share that would hurt to leak.

HTTP API

Both endpoints require a CLI token (Authorization: Bearer slew_…).

Endpoint	Effect
POST /shares?ttl=<days>	Body is a tar.gz (Content-Type: application/gzip). Creates the share, uploads, and activates in one request. Returns { deployment_id, url, expires_at }.
GET /shares	Your live shares: { shares: [{ name, url, expires_at, … }] }.
DELETE /shares/:name	Delete a live share: files and records, effective immediately.

Shares never appear in GET /projects — they are a separate surface, and the web console lists them under Temporary shares.

The agent skill

Coding agents generate HTML plans constantly; the missing piece is a URL you can open. A ready-made skill teaches Claude Code (or any agent with a skills directory) to publish pages through slew share whenever you ask for a link. Install it from the skills registry with the CLI:

slew skill install slew-share --global   # → ~/.claude/skills/, every project

Or copy it by hand — a skill is just markdown:

mkdir -p ~/.claude/skills/slew-share
curl -fsSL https://skills.slew.cloud/skills/slew-share/SKILL.md \
  -o ~/.claude/skills/slew-share/SKILL.md

From then on, "share this plan" ends with a link like quiet-harbor-lantern.slew.cloud in the chat. The skill needs the slew CLI and a login (slew login, or SLEW_TOKEN in CI). Read it before installing, and browse the other skills, at skills.slew.cloud.