Publish static files or directories to wzrrd.sh. Use for sharing agent-built pages, demos, receipts, docs, diagrams, or static artifacts at https://<slug>.wzrrd.sh/.
64 stars
0 votes
0 copies
4 views
Added May 28, 2026
researchbashdebuggingapi
Works with
cli
api
mcp
Security analysis
C71/100
criticalPipes output to a shell interpreter
mediumUses curl or wget to download content
criticalDownloads and executes remote scripts — classic supply chain attack
Installs into .claude/skills of the current project.
Are you the author of Wzrrd Publish?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/joelhooks-wzrrd-publish)
---
name: wzrrd-publish
description: Publish static files or directories to wzrrd.sh. Use for sharing agent-built pages, demos, receipts, docs, diagrams, or static artifacts at https://<slug>.wzrrd.sh/.
---
# wzrrd publish
Use `wzrrd` to publish static files and directories to `https://<slug>.wzrrd.sh/`.
Public CLI and skill distribution repo: `wzrrd-sh/wzrrd-cli`.
## Install
If `wzrrd` is missing:
```bash
curl -fsSL https://wzrrd.sh/install.sh | bash
```
If `~/.local/bin` is not on PATH, add it or call `~/.local/bin/wzrrd` directly.
## Publish immediately
```bash
wzrrd publish --file ./site --slug demo
```
- `--file` can be a single HTML file or a directory with `index.html` at the root.
- Anonymous publishes work without login.
- Anonymous publishes are ephemeral and expire after 24 hours.
- Anonymous responses include `claimUrl`; share/open it if the user wants the URL to become permanent.
## Expiring authenticated publishes
The live site advertises expiring authenticated publishes:
```bash
wzrrd publish --file ./site --slug demo --expires-in 7d
```
Duration aliases include `1h`, `24h`, `7d`, and `month` (30 days).
Compatibility check: only use `--expires-in` after `wzrrd publish --help` lists it. Local CLI `0.3.0` currently rejects this flag.
## Permanent publishing
```bash
wzrrd login
wzrrd publish --file ./site --slug demo
```
`wzrrd login` runs a device approval flow and stores a scoped agent token at `~/.config/wzrrd/auth.json`.
## Configured publishing
Projects can add `wzrrd.config.json` with `site.slug` and `publish.source` so agents can run `wzrrd publish` without guessing. Schema: `https://wzrrd.sh/schema/config.json`.
## Safety defaults
- The CLI is non-interactive by default for agents.
- Published sites are `noindex` by default.
- Only add `--index` when the user explicitly wants search indexing.
- Prefer small static artifacts. Current anonymous limits are aggressive: 5 MB total, 1 MB per file, 50 files, 10 anonymous publishes per IP/hour.
## Diagnostics
Before debugging, run:
```bash
wzrrd doctor && wzrrd auth-status
```
## Return format
Always give the user the live URL. If the publish was anonymous, also include the `claimUrl` and remind them it expires in 24 hours unless claimed.
## Current joelclaw compatibility notes
- As of 2026-05-19, local `wzrrd --version` reports `0.3.0`.
- The live site skill advertises `--expires-in`, but local CLI `0.3.0` rejects it with `Received unknown argument: '--expires-in'`.
- The live site exposes machine-readable discovery at:
- `https://wzrrd.sh/llms.txt`
- `https://wzrrd.sh/index.md`
- `https://wzrrd.sh/.well-known/agent-configuration`
- `https://wzrrd.sh/.well-known/api-catalog`
- `https://wzrrd.sh/.well-known/agent-skills/index.json`
- `https://wzrrd.sh/.well-known/mcp/server-card.json`
- `https://wzrrd.sh/.well-known/agent-card.json`
