wzrrd-publish
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/.
What this skill does
# 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. ## Review page and diagram defaults - Default to black text on white or near-white paper, compact hero, modest H1, sane letter spacing, and paragraphs over card grids. - Use boxes sparingly. Reserve them for receipts, controls, and data that truly needs a boundary. - For workflow, lifecycle, triage, approval, runtime, or operator-report graphics, prefer tall vertical D2 flowcharts rendered as static SVG. Use `direction: down` and let labels breathe. - Avoid crushed wide diagrams. If the chart explains how work moves, vertical flow is usually more readable on wzrrd pages and pi-notes surfaces. - Add cache-busting query params to regenerated SVGs when republishing a wzrrd page so stale browser cache does not show the old chart. - For reusable report pages, prefer SvelteKit rendering MDSvX with reusable components for flowcharts, marginalia, stat lines, paragraph lists, tables, and receipts. - Prefer Tufte-style marginalia for footnotes, source notes, privacy notes, and link context. Collapse marginalia into a left-rule note on mobile. - Use Shiki with a Catppuccin theme for code blocks when the page includes source snippets. ## 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`
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.