Skill

share-html

Publish a local HTML file or static site directory to a configured local share server and return a browser-viewable URL. Use when the user wants to open coding-agent output in a browser on the same machine or another device over a private tailnet.

npx claudepluginhub ondrej-svec/heart-of-gold-toolkit --plugin marvin

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Publish browser-viewable artifacts to the local share server.

Supporting Assets

docs/troubleshooting.mddocs/usage.mdscripts/healthcheck.shscripts/publish.sh

SKILL.md

Similar Skills

share-server-setup

Set up a local share server for coding-agent HTML/static artifacts, or connect portable share skills to an existing compatible server. Use when the user wants local browser-share infrastructure, Tailscale-backed viewing, or reusable artifact publishing across coding agents.

8 files

marvin

edgeone

119

Deploys HTML or text content to EdgeOne Pages and returns a public URL. No login or API key required. Useful for quick static page sharing or prototypes via npx mcporter.

aahl-skills

brewdoc:publish

Publishes text, markdown, JSON, or files to brewpage.app. Detects type via Bash, prompts for namespace and password using AskUserQuestion, sets TTL, returns public URL.

2 files4 tools

brewdoc

Stats

Parent Repo Stars11

Parent Repo Forks1

Last CommitApr 14, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Share HTML

Publish browser-viewable artifacts to the local share server.

Use this skill when

the user generated an HTML report, preview, or visualization and wants a stable URL

the user wants to open output in a browser on another device

the user wants a share flow that works across coding agents

another shared skill produced HTML as a derived artifact and now needs publication

Supported inputs

a single .html file

a directory containing index.html

Common producers include:

handcrafted HTML reports

static-site outputs

HTML mind maps or structured document previews generated from brainstorms, plans, or architecture docs

If the server is not configured yet, stop and run share-server-setup first.

Default workflow

Verify health:

bash scripts/healthcheck.sh

Publish the artifact:

bash scripts/publish.sh <path>

Return the final URL to the user.

Available scripts

scripts/healthcheck.sh — check server config and health before publishing

scripts/publish.sh — publish a single HTML file or static site directory

Output expectations

The publish script prints structured JSON to stdout. Use the returned url as the primary browser URL. If both url and viewerUrl are present, prefer url when it is a tailnet/browser-facing URL.

Failure handling

Missing config → stop and use share-server-setup

Unhealthy server → surface the health error clearly

Unsupported artifact shape → explain the expected file/directory rules

Missing index.html in a directory → reject rather than guess

References

docs/usage.md

docs/troubleshooting.md

Share HTML

Publish browser-viewable artifacts to the local share server.

Use this skill when

the user generated an HTML report, preview, or visualization and wants a stable URL
the user wants to open output in a browser on another device
the user wants a share flow that works across coding agents
another shared skill produced HTML as a derived artifact and now needs publication

Supported inputs

a single .html file
a directory containing index.html

Common producers include:

handcrafted HTML reports
static-site outputs
HTML mind maps or structured document previews generated from brainstorms, plans, or architecture docs

If the server is not configured yet, stop and run share-server-setup first.

Default workflow

Verify health:
```
bash scripts/healthcheck.sh
```
Publish the artifact:
```
bash scripts/publish.sh <path>
```
Return the final URL to the user.

Available scripts

scripts/healthcheck.sh — check server config and health before publishing
scripts/publish.sh — publish a single HTML file or static site directory

Output expectations

Failure handling

Missing config → stop and use share-server-setup
Unhealthy server → surface the health error clearly
Unsupported artifact shape → explain the expected file/directory rules
Missing index.html in a directory → reject rather than guess

References

docs/usage.md
docs/troubleshooting.md