Agent skill · writing content · aiskillstore
brewpage-publish
Publish content to brewpage.app — text, markdown, JSON, file, or multi-file site. Asks namespace and password, returns public URL. Triggers: publish, share link, upload to brewpage, host page, brewpage, publish site, upload site, upload directory, deploy site, сделай публичную ссылку, опубликуй.
Why this skill is useful
Adds specific API commands and workflows for publishing content to brewpage.app that the AI wouldn't reliably generate on its own.
What it needs
Requires brewpage account access. About 7k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
brewpage-publish Publish content to brewpage.app — free instant hosting for HTML pages, JSON documents, files, and multi-file sites. No sign-up required. Workflow Step 1: Parse Arguments Extract from $ARGUMENTS: --ttl N → TTL in days (default: 15) --entry <filename> → entry file for SITE uploads (default: auto-detect) Remaining text → contentarg Step 2: Detect Content Type Input Type API ------- ------ ----- contentarg is a directory (test -d) SITE POST /api/sites (dir auto-zipped — primary path) contentarg ends with .zip AND file exists (test -f) SITE POST /api/sites (pre-built archive upload) contentarg is a file path AND file exists (test -f) FILE POST /api/files (multipart) contentarg starts with { or [ JSON POST /api/json Anything else HTML POST /api/html (format=markdown) Mode rule: directory/ZIP → SITE. Single file → FILE. POST /api/sites accepts ONLY a multipart archive=@file.zip — there is no raw-folder upload, so a directory is auto-zipped on the fly (the robust default; archive sealing keeps relative paths intact). Stats per type — SITE (dir): HTML count, total size, entry file. SITE (ZIP): file size, entry override. FILE: size + MIME via file --mime-type -b. TEXT/JSON: char count. Step 3: Show Pre-Publish Stats For HTML/JSON/FILE: For SITE: detect entry file using priority: 1) --entry flag, 2) index.html exists, 3) first .html file alphabetically. Built-static guard (run BEFORE zipping). Publish BUILT output, never project sources: If the directory contains no .html file at all → FAIL with an explicit error: "No .html found — build the site first, then point at the build output directory." Do not guess an entry. If the directory looks like un-built sources (has package.json + src/ but no top-level .html) → warn and ask the user to point at the build output instead (dist/, build/, out/, site/, or public/). Do not zip the source tree. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/brewpage-publish