Brewpage Publish

Instantly deploy text, JSON, files, or full static sites to brewpage.app with zero configuration.

Install
cmdop skills install agensi-brewpage-publish

Brewpage Publish is a skill that lets an AI agent deploy content directly to brewpage.app without any hosting setup. It accepts four content types: static site directories containing HTML, CSS, and JavaScript; markdown documents; raw HTML text; formatted JSON payloads; and single file assets uploaded via multipart upload. The skill detects the content type automatically and selects the appropriate deployment path, so the agent does not need to branch on format itself.

For static site directories, the skill zips the directory, detects the entry point (such as index.html), and strips sensitive files including .env and .git before uploading. Deployments can be made public or password-protected, and they can be assigned to custom namespaces for internal organization. A TTL (Time-To-Live) value can be set to make deployments temporary. Owner tokens are saved locally to .claude/brewpage-history.md, which allows the agent to delete or update a deployment programmatically at a later time.

Built-in safeguards prevent accidental publication of node_modules, source code, or environment secrets. This makes it suitable for agent workflows that generate UI previews, documentation pages, or data reports that need to be shared quickly without involving a cloud provider account or a deployment pipeline. It is not a general-purpose hosting service and does not support server-side runtimes or databases.

Use cases

  • Deploy an agent-generated static UI preview to a shareable URL without configuring AWS or Vercel
  • Publish a markdown report or documentation page to a temporary public link with a TTL
  • Share a formatted JSON data payload at a stable URL for downstream tooling to consume
  • Host an internal draft behind password protection using a private namespace
  • Programmatically delete or update a prior deployment using the saved owner token
  • Upload a single file asset via multipart upload for quick distribution

When to use it

  • An agent needs to produce a live, shareable URL from generated HTML, markdown, JSON, or a static site directory
  • The workflow requires temporary deployments with automatic expiry via TTL
  • Internal drafts must be kept behind password protection without a separate auth layer
  • No cloud provider credentials or deployment pipeline are available in the agent environment

When not to use it

  • The site requires server-side code execution, APIs, or a database backend
  • The deployment target must be a custom domain outside of brewpage.app
  • Long-lived, production-grade hosting with SLA guarantees is required
  • The content includes dynamic server-rendered pages rather than static assets