# Publish Content Instantly to brewpage.app

Sharing files or sites usually requires setting up hosting, accounts, and configuration. This skill publishes text, files, and entire sites to brewpage.app with a single command, returning a public URL ready to share.

## Install

```bash
npx skillstore add kochetkov-ma/brewpage-publish
```

## Metadata

- - Slug: kochetkov-ma-brewpage-publish
- - Version: 1.0.0
- - Author: kochetkov-ma
- - GitHub username: kochetkov-ma
- - License: MIT
- - Repository: https://github.com/kochetkov-ma/claude-brewcode/tree/main/skills/brewpage-publish/
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: low
- - Risk factors: network, external\_commands, filesystem
- - Quality score: 77
- - Quality tier: bronze
- - Public page: https://skillstore.pages.dev/skills/kochetkov-ma-brewpage-publish
- - Manifest: https://skillstore.pages.dev/api/skills/kochetkov-ma-brewpage-publish/manifest

## Capabilities

- Publishes text and markdown to brewpage.app as rendered HTML pages
- Uploads JSON documents to public or password-protected URLs
- Uploads individual files \(images, PDFs, binaries\) with preserved MIME types
- Zips and publishes entire static site directories as multi-file sites
- Generates human-readable namespace slugs from content context
- Stores owner tokens securely in a local history file for later deletion

## Use Cases

- Share a quick report with a teammate: A developer needs to share a markdown report with a colleague. They invoke the skill, get a public URL, and send the link — no email attachments or file transfers needed.
- Deploy a static site for review: A designer finishes a static site build and wants client feedback. They point the skill at the dist/ directory, set a password for privacy, and share the URL.
- Host a JSON API mock or data file: A frontend developer needs a public JSON endpoint for testing. They publish a JSON file to brewpage.app and use the URL as a mock API in their frontend code.

## Prompt Templates

### Publish simple text content

```
Publish "Hello, world! This is my first brewpage post." to brewpage.app
```

### Publish a markdown file

```
Publish ./README.md to brewpage.app with a 7-day TTL
```

### Deploy a built static site

```
Publish my ./dist directory as a site to brewpage.app, use namespace "my-project" and password-protect it
```

### Upload a file with custom TTL

```
Upload ./screenshot.png to brewpage.app, set TTL to 1 day, namespace "screenshots"
```

## Limitations

- Only publishes to brewpage.app — cannot use custom hosting providers
- Maximum TTL is 30 days — content is temporary by design
- Site uploads require built static output \(dist/, build/, etc.\) — not project sources
- Site URLs cannot be verified with curl alone — require a real browser

## Best Practices

- Always point site uploads at built output directories \(dist/, build/, out/\) — never at project sources
- Keep .claude/brewpage-history.md out of version control — it contains owner tokens for deletion
- Use password protection when publishing drafts or previews that should not appear in the public gallery

## Anti Patterns

- Do not publish raw project source trees with package.json or src/ — the skill will warn or fail to protect you from leaking source code
- Do not share owner tokens in conversation or commit them to version control — they allow deletion of your published content
- Do not append a trailing slash to site URLs — this routes to brewpage.app's landing page and breaks the link

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-02T12:56:56.809\+00:00
- - Summary: The skill is a legitimate publishing tool for brewpage.app. All network requests target the documented brewpage.app API endpoints. External commands use standard tools \(curl, jq, zip, mktemp\) for content upload. The skill implements security safeguards: it excludes .env, .git, node\_modules, and other sensitive paths from site uploads, never prints owner tokens in conversation, and stores them in a private file. The static scanner flagged many false positives because the skill's core function inherently requires network access and command execution. No malicious intent detected.

## Stats

- - Views: 0
- - Downloads: 0
- - Favorites: 0
- - Popularity score: 0