How do I install the Tailshare skill?

Run npx skillmds@latest add kellymears/tailshare in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Tailshare safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tailshare?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tailshare free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Tailshare?

kellymears (@kellymears) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tailshare by kellymears — Agent Skill

Name: Tailshare
Author: kellymears

Tailshare

Publish static files (HTML pages, reports, demos, build output) to the tailnet with the `tailshare` CLI. Use when the user says "tailshare this", "host this on the tailnet", "put this on cachy", "share this page", "publish this html", or wants a shareable https URL for a local directory. Also covers listing and removing existing shares. Not for GitHub gists (use /gist) or Claude Artifacts.

kellymears 2406ed4 3.0 KB Updated Sep 17, 2026

File contents

tailshare

tailshare is a home-brewed CLI that serves directories over HTTPS on the Tailscale node's hostname. Shares live under share/ and get a URL like https://cachy.tail46c968.ts.net/share/<name>/.

Quick reference

tailshare list                                  # what is published, sizes, URLs
tailshare publish --src <dir> --dist share/<path>   # publish (prints the URL)
tailshare rm share/<path>                       # unpublish
tailshare where                                 # config + data paths
tailshare funnel status                         # is it also on the public internet?

Publishing

--src is a directory, never a file. To share a single page, put it in its own directory as index.html first (a scratch dir is fine — tailshare copies the contents, it does not symlink).
--dist must start with share/. Anything else is rejected with "destination must be below share/". Use two levels — share/<project>/<page> — so related pages group in tailshare list (existing convention: share/cake/cost-scaling-estimate, share/cachy/keys).
The command prints the final URL. Relay it to the user verbatim.
Republishing to the same --dist replaces the contents in place; the URL is stable.

mkdir -p /tmp/keys && cp cheatsheet.html /tmp/keys/index.html
tailshare publish --src /tmp/keys --dist share/cachy/keys

HTML that will be served raw

Unlike the Artifact tool, tailshare does no wrapping. A page needs its own <!doctype html>, <html>, <head> (charset, viewport, <title>), and <body>. When converting an Artifact-style fragment, wrap it before publishing. Keep assets self-contained (inline CSS/JS, data-URI images) or place them in the same --src directory with relative paths.

Removing

tailshare rm share/<path> is immediate and irreversible. Confirm with the user before removing a share you did not create in the current session.

Visibility

Shares are reachable by anyone on the tailnet. If tailshare funnel status reports the Funnel is running, they are reachable by anyone on the internet at the same URL — say so before publishing anything sensitive, and never publish secrets, tokens, or private customer data.

Service plumbing (rarely needed)

tailshare stack — control the container stack behind the server
tailshare service — manage the user systemd units
tailshare api — loopback metadata endpoint used by the share widget
tailshare init — first-time config; already done on cachy

If publish fails with a connection error, check tailshare service / stack status before retrying.

---name: tailsharedescription: Publish static files (HTML pages, reports, demos, build output) to the tailnet with the `tailshare` CLI. Use when the user says "tailshare this", "host this on the tailnet", "put this on cachy", "share this page", "publish this html", or wants a shareable https URL for a local directory. Also covers listing and removing existing shares. Not for GitHub gists (use /gist) or Claude Artifacts.---# tailshare`tailshare` is a home-brewed CLI that serves directories over HTTPS on the Tailscalenode's hostname. Shares live under `share/` and get a URL like`https://cachy.tail46c968.ts.net/share/<name>/`.## Quick reference```bashtailshare list # what is published, sizes, URLstailshare publish --src <dir> --dist share/<path> # publish (prints the URL)tailshare rm share/<path> # unpublishtailshare where # config + data pathstailshare funnel status # is it also on the public internet?```## Publishing1. **`--src` is a directory, never a file.** To share a single page, put it in its own directory as `index.html` first (a scratch dir is fine — tailshare copies the contents, it does not symlink).2. **`--dist` must start with `share/`.** Anything else is rejected with "destination must be below share/". Use two levels — `share/<project>/<page>` — so related pages group in `tailshare list` (existing convention: `share/cake/cost-scaling-estimate`, `share/cachy/keys`).3. The command prints the final URL. Relay it to the user verbatim.4. Republishing to the same `--dist` replaces the contents in place; the URL is stable.```bashmkdir -p /tmp/keys && cp cheatsheet.html /tmp/keys/index.htmltailshare publish --src /tmp/keys --dist share/cachy/keys```## HTML that will be served rawUnlike the Artifact tool, tailshare does no wrapping. A page needs its own`<!doctype html>`, `<html>`, `<head>` (charset, viewport, `<title>`), and `<body>`.When converting an Artifact-style fragment, wrap it before publishing. Keep assetsself-contained (inline CSS/JS, data-URI images) or place them in the same `--src`directory with relative paths.## Removing`tailshare rm share/<path>` is immediate and irreversible. Confirm with the userbefore removing a share you did not create in the current session.## VisibilityShares are reachable by anyone on the tailnet. If `tailshare funnel status` reportsthe Funnel is running, they are reachable by **anyone on the internet** at the sameURL — say so before publishing anything sensitive, and never publish secrets, tokens,or private customer data.## Service plumbing (rarely needed)- `tailshare stack` — control the container stack behind the server- `tailshare service` — manage the user systemd units- `tailshare api` — loopback metadata endpoint used by the share widget- `tailshare init` — first-time config; already done on cachyIf `publish` fails with a connection error, check `tailshare service` / `stack`status before retrying.

Frequently asked questions