publish

brewdoc:publish

Publishes HTML/Markdown, JSON, files and multi-file sites to brewpage.app (free, no sign-up) and returns the URL.

Prompt contract

$ARGUMENTS is one free-form RU/EN prompt; the content (text, file/dir/zip path) and the flags --ttl N, --entry <filename>, --delivery-mode path|subdomain may sit anywhere in it.

1. Mode: the content type of what is published — detected in Step 2, scored by the keyword table there.
2. Scope: a sentence naming a file/dir resolves to that file/dir (e.g. "publish my report.md" -> content_arg = report.md, resolved against cwd). Never guess, never silently fall back to an empty HTML page. Fired by Claude mid-task (Skill tool), its args is the prompt: the path, or the exact text to publish, never a summary of it.
3. Ask: a sentence with no path and no inline text/JSON has nothing to publish -> ONE AskUserQuestion asking what to publish. Namespace and password -> the two dedicated AskUserQuestion calls in Steps 4-5; nothing else asks. Headless or unanswered -> the Step 4-5 defaults; nothing blocks.

Print once, before the first tool action, including filesystem probes and questions (labels literal, values in the conversation language). Use unresolved for type/namespace/password until determined; report resolved stats in Step 3.

PLAN — brewdoc:publish
INPUT:  <arguments verbatim, or "(empty)">
MODE:   <detected type — SITE|MARKDOWN|FILE|JSON|HTML> — <matched extension/shape | prose-resolved path>
SCOPE:  namespace=<ns>; ttl=<days>; password=<set|none>; delivery-mode=<server-default|path|subdomain>
DO:     <2-5 imperative bullets>
RESULT: <published URL>

Running commands

Every shell step is ONE command of the exact shape in the fences below: the single allowed-tools rule pre-approves exactly that shape, so the skill never prompts, headless included.

• Fill each '{…}' slot with the raw value and write every ' inside it as '\''; nothing else is escaped. Never wrap a value in double quotes. An empty slot stays '' (= omitted).
• Never quote the script path, prefix or chain the command (cd, VAR=…, ;, &&, |, $(…)): any other shape falls back to the normal permission prompt.
• Keep every command under 8,000 characters (longer ones are always refused); longer text goes through stage (Step 6).
• The script prints one decisive line: OK {url} or OK {url} | Files: N (then any NOTICE: … lines: what the server skipped or adjusted), CONFIRM: … (exit 2, nothing uploaded) or FAILED: … (server reason HTTP <status>: <message>). It removes its private run directory on every exit.