brewpage-publish

publish content to brewpage.app instantly , text, markdown, single files, or multi-file sites. no sign-up required. returns a public url + owner token for later deletion.

intent

use this skill when you need to host html, markdown, text content, or entire static sites on brewpage.app with zero friction. handles namespace selection, optional password protection, and persists owner tokens locally for future takedown. supports three content types: html/text, single files, and site directories. default ttl is 15 days.

inputs

brewpage.app API

• endpoint: https://brewpage.app/api
• auth: none required (public). owner token returned on publish for deletion only.
• rate limits: not documented; assume standard fair-use policy. no throttling observed in testing.

content source (one of):

• text string (html, markdown, or plain text)
• file path (absolute or relative; must exist)
• directory path (absolute or relative; must contain .html files for site mode)
• zip file (pre-built archive, alternative to directory)

command-line flags:

• --ttl N , time to live in days (default: 15, min: 1, max: typically 365 depending on api)
• --entry <filename> , entry file for site mode (default: auto-detect via priority: --entry flag > index.html > first .html alphabetically)

local filesystem:

• ./brewpage-history.md , workspace-relative history file for owner tokens. created on first publish. never commit to vcs; treat as secrets.

procedure

step 1: parse arguments

extract from the user's arguments string:

• look for --ttl N and store N as integer. default to 15 if absent.
• look for --entry <filename> and store filename. ignore if not present.
• remaining text = content_arg (path or string).

step 2: detect content type

classify content_arg using this priority:

• if content_arg is a directory path that exists on disk (test -d), type = SITE. input will be auto-zipped.
• else if content_arg ends with .zip and file exists (test -f), type = SITE. input is pre-built zip.
• else if content_arg is a file path and file exists (test -f), type = FILE.
• else type = HTML. treat content_arg as literal text or markdown.

html/site safety check (run before proceeding): if type is SITE and directory contains zero .html files, fail immediately with error: "no .html found in directory. build the site first, then point at the build output directory (e.g., dist/, build/, out/, _site/, or public/). do not zip source trees."

warn on source trees: if directory contains package.json + src/ but no top-level .html files, warn the user: "looks like un-built project sources. point at the build output directory instead (e.g., dist/, build/, out/, _site/, or public/) to avoid publishing source code."

step 3: show pre-publish stats

for html/text:

Content:  text · <char count> chars · POST /api/html
TTL:      <N> days

for file:

Content:  file · <filename> · <size in bytes or KB> · <MIME type via file(1)> · POST /api/files
TTL:      <N> days

for site: first, auto-detect entry file using priority: 1) --entry flag value, 2) index.html if exists, 3) first .html file alphabetically in directory. compute total file count and total size.

Content:  site · <N> files · <total size> · POST /api/sites
Entry:    <entry_file>
TTL:      <N> days

step 4: ask namespace

prompt user:

Namespace determines the URL prefix and gallery visibility on brewpage.app.

Options:
1) public ,  visible in gallery (default)
2) {auto-suggested 6-16 char slug}
3) Enter custom namespace
4) Skip ,  use public

Reply with a number or your custom namespace (alphanumeric + hyphens, 3-32 chars).

auto-suggest: generate one meaningful short slug (3-16 chars, lowercase alphanumeric + hyphens only) from content context:

• file → topic or purpose (e.g., api-docs, login-page, report-q2)
• text/html → main subject or title (e.g., pricing, team-intro, changelog)
• site → site title or directory name (e.g., portfolio, docs-site)
• fallback → project name or directory name if ambiguous

never use random strings or truncated filenames. slug must be human-readable and describe what's published.

resolution:

• user enters 1, 4, or blank → use public
• user enters 2 → use suggested slug
• user enters custom text → validate (alphanumeric + hyphens, 3-32 chars); reject and re-ask if invalid

store result as {ns}.

step 5: ask password

prompt user:

Password protection (optional; if set, page hides from gallery):

Options:
1) No password (default)
2) Random: {generated 6-char password, e.g. "kx7p2m"}
3) Enter custom password (min 4 chars)
4) Skip ,  no password

Reply with a number or your custom password.

generate random password (run with bash):

LC_ALL=C tr -dc 'a-z0-9' < /dev/urandom | head -c6 2>/dev/null

resolution:

• user enters 1, 4, or blank → no password. set PASSWORD="".
• user enters 2 → use generated random string.
• user enters custom text → validate (min 4 chars); reject and re-ask if too short. store as PASSWORD.

step 6a: init history file

run once before any publish (run with bash):

HISTORY_FILE="./brewpage-history.md"
if [ ! -f "$HISTORY_FILE" ]; then
  cat > "$HISTORY_FILE" <<'HEADER'
# brewpage.app ,  Published Pages

> PRIVATE FILE ,  keep this out of version control and never share it.
> Owner tokens allow delete (no in-place PUT for sites; html/json/kv support PUT).
> Delete html/json/kv: `curl -s -X DELETE "https://brewpage.app/api/{ns}/{id}" -H "X-Owner-Token: TOKEN"`
> Delete site:         `curl -s -X DELETE "https://brewpage.app/api/sites/{ns}/{id}" -H "X-Owner-Token: TOKEN"`

| Date | URL | Owner Token | TTL | Type |
|------|-----|-------------|-----|------|
HEADER
fi

step 6b: publish (select one block below by content type)

html/text (run with bash):

HISTORY_FILE="./brewpage-history.md"
CONTENT=$(cat <<'BREWPAGE_EOF'
{content_arg}
BREWPAGE_EOF
)
PAYLOAD=$(jq -n --arg c "$CONTENT" '{content: $c}')
PASS_H=()
[ -n "$PASSWORD" ] && PASS_H=(-H "X-Password: $PASSWORD")
RESPONSE=$(curl -s -X POST "https://brewpage.app/api/html?ns={ns}&ttl={days}&format=markdown" \
  -H "Content-Type: application/json" \
  "${PASS_H[@]}" \
  -d "$PAYLOAD")

URL=$(echo "$RESPONSE" | jq -r '.link // empty')
TOKEN=$(echo "$RESPONSE" | jq -r '.ownerToken // empty')

if [ -n "$URL" ]; then
  [ -n "$TOKEN" ] && echo "| $(date '+%Y-%m-%d %H:%M') | [$URL]($URL) | \`$TOKEN\` | {ttl}d | html |" >> "$HISTORY_FILE"
  echo "OK $URL"
else
  echo "FAILED: $RESPONSE"
fi

file (run with bash):

HISTORY_FILE="./brewpage-history.md"
PASS_H=()
[ -n "$PASSWORD" ] && PASS_H=(-H "X-Password: $PASSWORD")
RESPONSE=$(curl -s -X POST "https://brewpage.app/api/files?ns={ns}&ttl={days}" \
  "${PASS_H[@]}" \
  -F "file=@{absolute_file_path}")

URL=$(echo "$RESPONSE" | jq -r '.link // empty')
TOKEN=$(echo "$RESPONSE" | jq -r '.ownerToken // empty')

if [ -n "$URL" ]; then
  [ -n "$TOKEN" ] && echo "| $(date '+%Y-%m-%d %H:%M') | [$URL]($URL) | \`$TOKEN\` | {ttl}d | file |" >> "$HISTORY_FILE"
  echo "OK $URL"
else
  echo "FAILED: $RESPONSE"
fi

site (directory) (run with bash):

HISTORY_FILE="./brewpage-history.md"
PASS_H=()
[ -n "$PASSWORD" ] && PASS_H=(-H "X-Password: $PASSWORD")
TMPZIP=$(mktemp /tmp/brewpage-site-XXXXXX.zip)
# exclude vcs, secrets, deps, editor/os junk, sourcemaps ,  only publish built static assets.
(cd "{directory_path}" && zip -r "$TMPZIP" . -x '.git/*' '*/.git/*' '.env' '.env.*' '*/.env' '*/.env.*' 'node_modules/*' '*/node_modules/*' '.DS_Store' '*/.DS_Store' 'Thumbs.db' '.idea/*' '*/.idea/*' '.vscode/*' '*/.vscode/*' '.cache/*' '*/.cache/*' '*.map' '*.log')
RESPONSE=$(curl -s -X POST "https://brewpage.app/api/sites?ns={ns}&ttl={days}&entry={entry}" \
  -H "User-Agent: OpenClaw/1.0" \
  "${PASS_H[@]}" \
  -F "archive=@$TMPZIP")
rm -f "$TMPZIP"

URL=$(echo "$RESPONSE" | jq -r '.link // empty')
URL="${URL%/}"  # strip trailing slash
TOKEN=$(echo "$RESPONSE" | jq -r '.ownerToken // empty')
FCOUNT=$(echo "$RESPONSE" | jq -r '.fileCount // "?"')

if [ -n "$URL" ]; then
  [ -n "$TOKEN" ] && echo "| $(date '+%Y-%m-%d %H:%M') | [$URL]($URL) | \`$TOKEN\` | {ttl}d | site ($FCOUNT files) |" >> "$HISTORY_FILE"
  echo "OK $URL | Files: $FCOUNT"
else
  echo "FAILED: $RESPONSE"
fi

site (zip file) (run with bash):

HISTORY_FILE="./brewpage-history.md"
PASS_H=()
[ -n "$PASSWORD" ] && PASS_H=(-H "X-Password: $PASSWORD")
RESPONSE=$(curl -s -X POST "https://brewpage.app/api/sites?ns={ns}&ttl={days}&entry={entry}" \
  -H "User-Agent: OpenClaw/1.0" \
  "${PASS_H[@]}" \
  -F "archive=@{zip_file_path}")

URL=$(echo "$RESPONSE" | jq -r '.link // empty')
URL="${URL%/}"  # strip trailing slash
TOKEN=$(echo "$RESPONSE" | jq -r '.ownerToken // empty')
FCOUNT=$(echo "$RESPONSE" | jq -r '.fileCount // "?"')

if [ -n "$URL" ]; then
  [ -n "$TOKEN" ] && echo "| $(date '+%Y-%m-%d %H:%M') | [$URL]($URL) | \`$TOKEN\` | {ttl}d | site ($FCOUNT files) |" >> "$HISTORY_FILE"
  echo "OK $URL | Files: $FCOUNT"
else
  echo "FAILED: $RESPONSE"
fi

step 7: output result

success (html/text/file):

Published: {url from bash output}
Owner token saved to ./brewpage-history.md

success (site):

Published site: {url from bash output}
Entry: {entry_file} | Files: {count}
Owner token saved to ./brewpage-history.md

⚠ share the url exactly as printed ,  no trailing slash.
  brewpage.app routes "/public/<id>/" to its own landing page.
  the js redirect that rescues no-slash form does not fire for slash-dir form.

error:

Publish failed.
Error: {error details from bash output}

never print the owner token in conversation. token persists only in ./brewpage-history.md.

decision points

if content_arg is a directory path that exists → auto-detect entry file (priority: --entry flag > index.html > first .html alphabetically). validate it contains at least one .html file; if zero .html files, fail with "no .html found , build the site first, then point at the build output directory." if directory looks like un-built sources (has package.json + src/ + no top-level .html), warn and ask user to point at build output instead. zip the directory on the fly and use site publish block.

else if content_arg ends with .zip and file exists → treat as pre-built site archive. skip zipping. use site publish block with pre-built zip.

else if content_arg is a file path and file exists → detect mime type via file(1). use file publish block.

else → treat as literal html/text/markdown content string. use html publish block.

if namespace input is 1, 4, or blank → use public.

if namespace input is 2 → use the auto-suggested slug.

if namespace input is custom text → validate alphanumeric + hyphens only, length 3-32 chars. reject invalid; re-ask.

if password input is 1, 4, or blank → no password protection.

if password input is 2 → use the generated 6-char random password.

if password input is custom text → validate length >= 4 chars. reject if too short; re-ask.

if curl response contains error or no .link field → fail with error message from response.

if curl response contains .ownerToken → append token row to ./brewpage-history.md history table (never print in conversation).

if api returns fileCount in site response → display count in output.

output contract

on success (html/text/file):

• printed line from bash: OK {url} where url is https://brewpage.app/public/{id} (no trailing slash).
• displayed to user: "Published: {url}" + "Owner token saved to ./brewpage-history.md".
• history file: new row appended to markdown table with date, url, token (backtick-wrapped), ttl, type.

on success (site):

• printed line from bash: OK {url} | Files: {count} where url is https://brewpage.app/public/{id} (no trailing slash).
• displayed to user: "Published site: {url}" + "Entry: {entry} | Files: {count}" + "Owner token saved to ./brewpage-history.md" + warning re: trailing slash.
• history file: new row appended with date, url, token, ttl, type (site), file count.

on error:

• bash prints FAILED: {response body}.
• displayed to user: "Publish failed." + error details.
• history file: not modified.

history file format (markdown table, workspace-relative path ./brewpage-history.md):

| Date | URL | Owner Token | TTL | Type |
|------|-----|-------------|-----|------|
| 2025-01-15 14:32 | [https://brewpage.app/public/abc123](https://brewpage.app/public/abc123) | `token_xyz_secret` | 15d | html |
| 2025-01-15 14:35 | [https://brewpage.app/public/def456](https://brewpage.app/public/def456) | `token_uvw_secret` | 30d | site (8 files) |

owner tokens are never exposed in conversation, only persisted in history file.

outcome signal

user knows it worked when:

• bash output shows OK {url} (no FAILED).
• conversation displays the public url in the "Published" line.
• url is accessible in a real browser and serves the expected content.
• for sites: url serves the site's entry file (e.g., index.html) without trailing slash. if url is appended with /, browser may redirect to brewpage's own landing page (js redirect does not fire for slash-dir form).
• owner token appears in ./brewpage-history.md history table and can be used with curl DELETE to remove the page later.
• if password was set,