Skill

share-server-control

Control the local share server lifecycle after setup. Use when the user wants to check status, start or stop the local share server, restart it, or enable or disable private Tailscale viewer exposure.

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

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Control the local share server after it has been set up.

Supporting Assets

docs/troubleshooting.mddocs/usage.mdscripts/disable-viewer.shscripts/enable-viewer.shscripts/restart.shscripts/start.shscripts/status.shscripts/stop.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

tailscale-serve

586

Manages Tailscale `serve` for multiple paths without conflicts: check status, serve directories/files/ports at subpaths, remove paths, reset all. Useful for sharing local dev servers securely.

sundial-org-awesome-openclaw-skills-4

tailscale

Manages Tailscale mesh VPN networks via CLI and API: check status/peers, ping devices, list tailnet devices, send files, expose services with serve/funnel, create auth keys.

6 files

homelab-core

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 Server Control

Control the local share server after it has been set up.

Use this skill when

the user wants to know whether the share server is running
the user wants to start, stop, or restart the local server
the user wants to enable or disable private Tailscale viewer exposure
the user wants the current health/status without re-running setup

Boundaries

This skill may:

inspect the current config and server health
control the macOS LaunchAgent for the reference server
inspect or change Tailscale Serve viewer exposure

This skill may not:

replace first-time setup
expose the publish/admin API remotely
enable Funnel/public internet access by default

Recommended commands

Status

bash scripts/status.sh

Start the local server

bash scripts/start.sh

Stop the local server

bash scripts/stop.sh

Restart the local server

bash scripts/restart.sh

Enable private viewer exposure over Tailscale

bash scripts/enable-viewer.sh --public-base-url "https://<machine>.<tailnet>.ts.net"

Disable private viewer exposure over Tailscale

bash scripts/disable-viewer.sh

Delete a published artifact by slug

heart-of-gold share-server delete <slug>

Delete only an alias pointer

heart-of-gold share-server delete --alias <alias> --onlyAlias

Notes

In v1, lifecycle control assumes the reference server was installed as a macOS LaunchAgent.
If the user has not set up the server yet, stop and use share-server-setup first.
status.sh is the safest first command because it shows LaunchAgent state, health, and Tailscale Serve status together.

Available scripts

scripts/status.sh — show LaunchAgent, health, and viewer exposure status
scripts/start.sh — load the LaunchAgent and start the local share server
scripts/stop.sh — unload the LaunchAgent and stop the local share server
scripts/restart.sh — restart the LaunchAgent cleanly
scripts/enable-viewer.sh — enable private Tailscale Serve exposure for the viewer listener
scripts/disable-viewer.sh — turn off private Tailscale Serve exposure
heart-of-gold share-server delete <slug> — remove a published artifact, its aliases, and its metadata entries
heart-of-gold share-server delete --alias <alias> --onlyAlias — remove only an alias pointer

References

docs/usage.md
docs/troubleshooting.md