Run any Skill in Manus with one click

publish-html-page

Stars4

Forks0

UpdatedJuly 14, 2026 at 12:20

Publish a self-contained HTML file to a shareable encrypted Cloudflare-hosted artifact URL using html-artifact-publisher. Use when asked to upload, publish, share, or host a generated HTML page/artifact/explainer via artifacts.craftdesign.group or the HTML artifact publisher.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

danmestas

danmestas/wardrobe

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	publish-html-page
version	1.0.0
type	skill
targets	["claude-code","codex","gemini","pi"]
category	{"primary":"integrations"}
description	Publish a self-contained HTML file to a shareable encrypted Cloudflare-hosted artifact URL using html-artifact-publisher. Use when asked to upload, publish, share, or host a generated HTML page/artifact/explainer via artifacts.craftdesign.group or the HTML artifact publisher.

publish-html-page

Publish a self-contained HTML file to a shareable encrypted URL. The Worker stores encrypted HTML bytes; metadata such as title, source name, expiry, and slug remains plaintext. The decryption key lives only in the URL #fragment and never reaches the server.

Use when

Use after generating a standalone HTML explainer, report, prototype, or artifact file that should be viewable by URL. Confirm the file is self-contained first: inline assets are preferred; external URLs may leak referrer data or fail offline.

Implementation location

Run the colocated publisher from the wardrobe repo root (Node 22+ required):

node skills/publish-html-page/scripts/publish-html.mjs [options] <file.html>

Required environment:

HTML_PUBLISHER_URL=https://artifacts.craftdesign.group
HTML_PUBLISHER_TOKEN=<bearer token>

Never print, persist, or pass the bearer token in a way that exposes it in logs.

CLI reference

node skills/publish-html-page/scripts/publish-html.mjs [options] <file.html>

  --title <text>     Human-readable title (default: filename)
  --ttl <duration>   1h | 6h | 24h | 7d | 30d | never  (default: 7d)
  --slug <slug>      Optional vanity slug
  --delete-local     Delete local HTML only after confirmed successful upload
  --json             Machine-readable JSON output only
  --copy             Copy viewer URL to clipboard even with --json
  --no-clipboard     Never attempt clipboard copy

Workflow

Confirm the target file starts with <!doctype html or <html.
Prefer --json when running as an agent so stdout is parseable.
Set HTML_PUBLISHER_URL and HTML_PUBLISHER_TOKEN through the tool environment, not inline in prose.
Run the publisher with a useful --title and appropriate --ttl.
Return only viewerUrl unless the user needs deletion/revocation details.
Preserve and report warningMessages; external-resource warnings matter.

Example:

HTML_PUBLISHER_URL=https://artifacts.craftdesign.group \
HTML_PUBLISHER_TOKEN="$HTML_PUBLISHER_TOKEN" \
node skills/publish-html-page/scripts/publish-html.mjs /path/to/page.html --title "Artifact title" --ttl 30d --json

Rules

Share the full viewerUrl, including the #fragment; without it the browser cannot decrypt.
Treat viewerUrl as a secret-bearing link: anyone with the full URL can read the artifact.
Do not expose deleteToken unless the user may need to revoke the artifact early.
Use --delete-local only for files generated in the current session and only after upload succeeds.
Never delete the source file manually before upload completes.
If upload fails, leave the file untouched and report the exact error.
Clipboard copy is best-effort; failure does not mean upload failed.

Success output

{
  "id": "abc123",
  "viewerUrl": "https://artifacts.craftdesign.group/v/abc123#<base64url-key>",
  "blobUrl": "https://artifacts.craftdesign.group/blob/abc123",
  "expiresAt": "2026-07-23T00:00:00.000Z",
  "deleteToken": "deadbeef…",
  "warnings": 0,
  "warningMessages": []
}

More from this repository

same repository

helland

danmestas/wardrobe

The Pat Helland lens: treat durable data as immutable, append-only facts that carry their own identity and version; and design across service, machine, or org boundaries assuming you cannot have distributed transactions — only idempotent, at-least-once messages that must be reconciled. Apply this on in-place updates and overwrites, "just UPDATE the row," two-phase commit or distributed transactions at scale, exactly-once delivery assumptions, shared mutable state across services, and any data that crosses a boundary of service, machine, org, or time. Trigger even when Helland isn't named — the smell is mutation-in-place and pretending distributed systems can be transactional.

2026-07-184

hickey

danmestas/wardrobe

The Rich Hickey lens: pursue simple (un-braided, one role) over easy (familiar, near-at-hand), decomplect concerns that got tangled together, and separate value, identity, state, and time. Apply this whenever "easy," "convenient," or "it's what we already use" is doing the work of justifying a design; when state is braided into logic, policy into mechanism, or data into behavior; when object-soup would be plainer as data; and when a hard design decision is being made at the keyboard under time pressure instead of thought through first. Trigger even when Hickey isn't named — the smell is complecting, and confusing "easy" with "simple."

2026-07-184

carmack

danmestas/wardrobe

The John Carmack lens: minimize the mutable state you have to reason about, do the simple thing before the clever one, and treat correctness tooling — static analysis, warnings-as-errors, determinism — as non-negotiable. Apply this on sprawling mutable state, "we'll clean it up later," debugging by print- statement whack-a-mole, silenced compiler warnings, nondeterministic or non-reproducible behavior, premature abstraction, perf work that skips measurement, and any "what should we actually work on" prioritization call. Trigger even when Carmack isn't named — the smell is code whose full set of states you can't hold in your head, and effort that isn't ruthlessly focused.

2026-07-184

bellard

danmestas/wardrobe

The Fabrice Bellard lens: build the smallest self-contained thing that fully does the job, get performance from insight instead of hardware, and reuse existing machinery instead of reinventing it. Apply this whenever code is growing dependencies, frameworks, services, or infrastructure to solve a problem that a smaller, sharper implementation could handle — or whenever someone says a thing needs a cluster, a big framework, or a rewrite. Use for size/complexity audits, "do we really need this dependency/service?" questions, performance work where the reflex is to add hardware or caching, green-field "should this be one file or a platform?" decisions, and any moment the answer is trending toward "that's impractical, you'd need X." Trigger even when the user doesn't name Bellard — the smell is scope inflation and reaching for resources over insight.

2026-07-184

vault-autoresearch

danmestas/wardrobe

Use when iteratively researching a topic and filing the synthesis into an Obsidian vault for later ingestion. Output goes to `<vault>/raw/` (NOT directly into wiki pages) so that `vault-ingest` can process it on its own schedule. Triggers: '/vault-autoresearch', 'autoresearch [topic]', 'research [topic] into the vault', 'deep dive into [topic]', 'find everything about [topic] for the vault', 'research and stage'.

2026-07-144

vault-ingest

danmestas/wardrobe

Ingest sources into the Obsidian wiki vault. Reads a source, extracts entities and concepts, creates or updates wiki pages, cross-references, and logs the operation. Supports files, URLs, and batch mode. Triggers on: ingest, process this source, add this to the wiki, read and file this, batch ingest, ingest all of these, ingest this url.

2026-07-144

name	publish-html-page
version	1.0.0
type	skill
targets	["claude-code","codex","gemini","pi"]
category	{"primary":"integrations"}
description	Publish a self-contained HTML file to a shareable encrypted Cloudflare-hosted artifact URL using html-artifact-publisher. Use when asked to upload, publish, share, or host a generated HTML page/artifact/explainer via artifacts.craftdesign.group or the HTML artifact publisher.

publish-html-page

Use when

Implementation location

Run the colocated publisher from the wardrobe repo root (Node 22+ required):

node skills/publish-html-page/scripts/publish-html.mjs [options] <file.html>

Required environment:

HTML_PUBLISHER_URL=https://artifacts.craftdesign.group
HTML_PUBLISHER_TOKEN=<bearer token>

Never print, persist, or pass the bearer token in a way that exposes it in logs.

CLI reference

node skills/publish-html-page/scripts/publish-html.mjs [options] <file.html>

  --title <text>     Human-readable title (default: filename)
  --ttl <duration>   1h | 6h | 24h | 7d | 30d | never  (default: 7d)
  --slug <slug>      Optional vanity slug
  --delete-local     Delete local HTML only after confirmed successful upload
  --json             Machine-readable JSON output only
  --copy             Copy viewer URL to clipboard even with --json
  --no-clipboard     Never attempt clipboard copy

Workflow

Confirm the target file starts with <!doctype html or <html.
Prefer --json when running as an agent so stdout is parseable.
Set HTML_PUBLISHER_URL and HTML_PUBLISHER_TOKEN through the tool environment, not inline in prose.
Run the publisher with a useful --title and appropriate --ttl.
Return only viewerUrl unless the user needs deletion/revocation details.
Preserve and report warningMessages; external-resource warnings matter.

Example:

HTML_PUBLISHER_URL=https://artifacts.craftdesign.group \
HTML_PUBLISHER_TOKEN="$HTML_PUBLISHER_TOKEN" \
node skills/publish-html-page/scripts/publish-html.mjs /path/to/page.html --title "Artifact title" --ttl 30d --json

Rules

Share the full viewerUrl, including the #fragment; without it the browser cannot decrypt.
Treat viewerUrl as a secret-bearing link: anyone with the full URL can read the artifact.
Do not expose deleteToken unless the user may need to revoke the artifact early.
Use --delete-local only for files generated in the current session and only after upload succeeds.
Never delete the source file manually before upload completes.
If upload fails, leave the file untouched and report the exact error.
Clipboard copy is best-effort; failure does not mean upload failed.

Success output

{
  "id": "abc123",
  "viewerUrl": "https://artifacts.craftdesign.group/v/abc123#<base64url-key>",
  "blobUrl": "https://artifacts.craftdesign.group/blob/abc123",
  "expiresAt": "2026-07-23T00:00:00.000Z",
  "deleteToken": "deadbeef…",
  "warnings": 0,
  "warningMessages": []
}