# Publish and Update Content on BrewPage

Publishing a file or site also means tracking who can update it. BrewPage Publish Safe sends approved content and keeps ownership records for later updates.

## Install

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

## Metadata

- Status: approved
- Slug: kochetkov-ma-brewpage-publish-safe
- Skillstore revision: r2
- Version status: missing
- Tree hash: d429f662a3b5c154943051c59e8ed36076f80440deac5a1ed5ac3aff3121c1d6
- Author: kochetkov-ma
- GitHub username: kochetkov-ma
- License: MIT
- Repository: https://github.com/kochetkov-ma/claude-brewcode/tree/f6817faf3aa640a22723dd5918cfda759cb9509b/skills/brewpage-publish-safe
- Ref: d0711bf661230a71e66e40843f2ab3bb938327ae
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, filesystem, external\_commands, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/kochetkov-ma-brewpage-publish-safe
- Manifest: https://skillstore.pages.dev/api/skills/kochetkov-ma-brewpage-publish-safe/manifest

## Capabilities

- Publish approved HTML, Markdown, JSON, individual files, or static sites to the BrewPage REST API.
- Build a ZIP from a selected site directory or inspect a supplied ZIP. Return a manifest and require digest approval for flagged archives.
- Check selected inputs for common credential formats, exclude known private paths, and reject opaque nested archives.
- Set an expiration at creation and optionally select password protection from an owner-only file.
- Retain anonymous owner proof in private per-workspace state and use it to update the exact saved publication.
- Report pending creates and recover saved ownership or record an independently verified outcome.

## Use Cases

- Share a review draft: Publish a reviewed Markdown draft without requesting public listing. Share only the reader link with reviewers.
- Publish a static site build: Package a dedicated build directory and review its files and entry point before approving an upload.
- Replace a published status page: Use the original workspace and exact saved reader link to update the page without creating a replacement.

## Prompt Templates

### Inspect a local file

```
Probe the selected draft locally and report its file type and size. Do not contact BrewPage or publish anything.
```

### Publish a reviewed draft

```
Publish the reviewed Markdown draft to BrewPage under the specified non-public namespace for seven days. Use fresh anonymous ownership and no password.
```

### Update the same reader link

```
In the original workspace, update the exact saved reader link with my approved replacement. Keep the existing access settings and expiration. Do not create another publication.
```

### Review a static site release

```
Review the dedicated site build and its entry file without uploading. Check all selected content and archive metadata. Ask me to approve the final archive before uploading.
```

## Limitations

- Requires Bash, Python 3.8 or newer, Node.js, curl, and jq on macOS or Linux. ZIP workflows also need zip and unzip.
- Credential checks are limited to recognizable patterns. They do not cover every encoded secret or all ZIP metadata.
- This edition does not provide connected account ownership, private receipt delivery, or custom reader domain management.
- Updates require saved owner proof in the original workspace and preserve the current visibility, password, and expiration.

## Best Practices

- Review the exact files, page state, and archive metadata before authorizing an external write.
- Choose fresh anonymous ownership or expressly approve reuse. Keep owner tokens, management links, and passwords out of prompts and transcripts.
- Use the original workspace and exact saved reader link for updates. Resolve uncertain creates before authorizing another one.

## Anti Patterns

- Do not publish an entire workspace when only a build output is intended.
- Do not treat a link-only publication as private. Anyone with the link can view it unless it is password protected.
- Do not approve a changed archive with an old review digest or turn a failed update into a new publication.

## Security Audit

- Audited at: 2026-11-20T10:37:40.951\+00:00
- Summary: Most static alerts are documentation, validation, or fixed local operations. Confirmed exposure includes first-party transfers, reusable plaintext owner proof, and executable lookup through unverified PATH directories. Review also found incomplete ZIP metadata checks and implicit owner reuse; no evidence of author prompt injection or undisclosed external destinations was found.

## Stats

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