Skip to content
Skills Library
DevOps & cloud · Tool integration

share-server-setup

/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.

Licence
MIT
Last repository change
20.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
9
Scripts
5
HTML comments
0
URLs in SKILL.md
4
Deprecation

No signals detected. Repository changed on 20.08.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 5 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/configure-existing-server.sh, scripts/configure-tailscale-viewer.sh, scripts/healthcheck.sh, scripts/install-launch-agent.sh, scripts/install-reference-server.sh

What it does and when to use it

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.

Original author description

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.

How it works

  1. Use this skill when
  2. Boundaries
  3. Quick decision flow
  4. Existing compatible server mode
  5. Reference implementation mode
  6. Tailscale notes
  7. Available scripts
  8. References
Original SKILL.md headings · 104 lines, 385 words
SKILL.md preview
---
name: share-server-setup
description: 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.
compatibility: Requires Bun, curl, and optionally Tailscale CLI for private tailnet exposure. macOS LaunchAgent automation is supported in v1.
---

# Share Server Setup

Set up or adopt a local share server for cross-agent HTML/static artifact sharing.

## Use this skill when

- the user wants to share generated HTML reports or static previews in a browser
- the user wants a reusable local share server, not a one-off ad hoc file server
- the user wants optional private viewing over Tailscale
- `share-html` cannot run because the share server is not configured yet

## Boundaries

This skill may:
- inspect local config and server health
- install the Heart of Gold reference share server
- write/update `~/.agent-share/config.json`
- configure a macOS LaunchAgent for long-running use
- optionally configure `tailscale serve` for the viewer listener

This skill may not:
- expose the publish API remotely
- enable Funnel/public internet access by default
- assume Tailscale is required for local usage

## Quick decision flow

1. Check current health:
   ```bash
   bash scripts/healthcheck.sh
   ```
2. If a compatible server already exists, keep it and update config if needed.
3. If no compatible server exists, install the reference server:
   ```bash
   bash scripts/install-reference-server.sh
   ```
4. For macOS long-running usage, install the LaunchAgent:
   ```bash
   bash scripts/install-launch-agent.sh
   ```
5. If the user wants browser access from another tailnet device, configure Tailscale for the **viewer** listener only:
   ```bash
   bash scripts/configure-tailscale-viewer.sh --public-base-url "https://<machine>.<tailnet>.ts.net"
   ```

## Existing compatible server mode

If the user already has a compatible local share server, write the config without reinstalling:

```bash
bash scripts/configure-existing-server.sh \
  --api-url "http://127.0.0.1:4815" \
  --viewer-url "http://127.0.0.1:4816" \
  --public-base-url "https://<machine>.<tailnet>.ts.net" \
  --provider existing
```

Then verify:

```bash
bash scripts/healthcheck.sh
```

## Reference implementation mode

Install the reference server files, initialize config, and verify health:

```bash
bash scripts/install-reference-server.sh
bash scripts/healthcheck.sh
```

On macOS, set up long-running mode:

```bash
bash scripts/install-launch-agent.sh
```

## Tailscale notes

Tailscale is optional.

If used, expose only the **viewer** listener. The publish/admin API remains localhost-only.

This skill's Tailscale helper configures:
- local viewer listener on `127.0.0.1:4816`
- `tailscale serve --bg 4816`
- config update for `publicBaseUrl`

## Available scripts

- `scripts/healthcheck.sh` — check config and `GET /health`
- `scripts/install-reference-server.sh` — install the reference server and initialize config
- `scripts/install-launch-agent.sh` — configure macOS LaunchAgent persistence
- `scripts/configure-existing-server.sh` — point config at an already-running compatible server
- `scripts/configure-tailscale-viewer.sh` — expose viewer listener over `tailscale serve` and update config

## References

- `docs/setup.md`
- `docs/existing-server.md`
- `docs/troubleshooting.md`
Files in this package (9)
  • SKILL.md 3 KB
  • docs/existing-server.md 1 KB
  • docs/setup.md 1 KB
  • docs/troubleshooting.md 1 KB
  • scripts/configure-existing-server.sh 1 KB
  • scripts/configure-tailscale-viewer.sh 2 KB
  • scripts/healthcheck.sh 1 KB
  • scripts/install-launch-agent.sh 1 KB
  • scripts/install-reference-server.sh 1 KB

Versions

The database has no other skills named share-server-setup.

Database snapshot: 13.11.2026 · package version cf4fafaa610e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100share-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.
  • 100share-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.
  • 100wterm
    Web terminal server: manage the wterm-server daemon for browser-based shell access (local or remote via Tailscale). This skill should be used when checking wterm status, listing or creating terminal sessions, killing sessions, or managing the wterm LaunchAgent. Trigger on:…
  • 100tailscale-app-serve
    Use when a user wants to expose or test a local web app through Tailscale Serve, needs a tailnet-only HTTPS link, or asks for remote access without deploying the app.
  • 90setup-remote
    Set up remote access to approval reports and previews from another device such as a phone, and send footage to the workspace. Use doctor to assess Tailscale, guide installation and login (human actions), expose the preview server (default 4567) and approval report helper over…
  • 100tailscale
    tailscale-rmcp MCP server — query and manage your Tailscale network from Claude. Use this skill whenever the user mentions Tailscale devices, tailnet status, VPN nodes, MagicDNS, Tailscale ACL, access control policy, subnet routes, tailnet members, API keys, or wants to…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.