From marvin
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/marvin:share-server-controlThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Control the local share server after it has been set up.
Control the local share server after it has been set up.
This skill may:
This skill may not:
bash scripts/status.sh
bash scripts/start.sh
bash scripts/stop.sh
bash scripts/restart.sh
bash scripts/enable-viewer.sh --public-base-url "https://<machine>.<tailnet>.ts.net"
bash scripts/disable-viewer.sh
heart-of-gold share-server delete <slug>
heart-of-gold share-server delete --alias <alias> --onlyAlias
share-server-setup first.status.sh is the safest first command because it shows LaunchAgent state, health, and Tailscale Serve status together.scripts/status.sh — show LaunchAgent, health, and viewer exposure statusscripts/start.sh — load the LaunchAgent and start the local share serverscripts/stop.sh — unload the LaunchAgent and stop the local share serverscripts/restart.sh — restart the LaunchAgent cleanlyscripts/enable-viewer.sh — enable private Tailscale Serve exposure for the viewer listenerscripts/disable-viewer.sh — turn off private Tailscale Serve exposureheart-of-gold share-server delete <slug> — remove a published artifact, its aliases, and its metadata entriesheart-of-gold share-server delete --alias <alias> --onlyAlias — remove only an alias pointerdocs/usage.mddocs/troubleshooting.mdnpx claudepluginhub ondrej-svec/heart-of-gold-toolkit --plugin marvinSet 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.
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.
Guides deployment of TunPilot server on Linux via SSH script, CLI connection with health checks, updates, and initial setup detection.