agentleFS
diriendirien/yet-another-agent-harness/.claude/skills/tailscale-install/SKILL.md

tailscale-install

Skill19 starsChanged 8 months agoMITView on GitHub

Install and configure Tailscale across platforms. Detects OS, distro, and environment (including WSL2 and containers). Verifies existing installations, performs platform-appropriate install, and guides initial connection. Use when setting up Tailscale on a new machine, onboarding a server to a tailnet, or verifying an existing install.

  • Pipes a download into a shell
  • Installs packages

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 9 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before installing, check if Tailscale is already present:

    line 59
  2. Very specific:

    Check daemon status: sudo systemctl status tailscaled (Linux).

    line 68
  3. Distinctive:

    Stop here unless the user requests a reinstall or upgrade.

    line 70
  4. Distinctive:

    If not installed, proceed to installation.

    line 72
  5. Distinctive:

    When WSL2 is detected:

    line 86
  6. Distinctive:

    Check for Windows host Tailscale:

    line 88
  7. Very specific:

    If found — report version and verify with tailscale.exe status.

    line 94
  8. Very specific:

    If not found — instruct the user to install on the Windows host using WinGet, Chocolatey, or MSI (see …

    line 95
  9. Very specific:

    Verify tailscale.exe is accessible from WSL2.

    line 97
  10. Distinctive:

    After installation, verify three things:

    line 125
  11. Distinctive:

    If not found, check PATH or restart the terminal session.

    line 133
  12. Distinctive:

    If the device is not yet authenticated, proceed to initial connection.

    line 152
  13. Distinctive:

    Do not silently skip a failed installation.

    line 177

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Copyright 2025-2026 Richard Shade. Licensed under Apache-2.0. --><!-- SPDX-License-Identifier: Apache-2.0 -->

Tailscale Install

Install Tailscale and connect a device to a tailnet. Handles platform detection, installation, verification, and initial authentication.

What this skill does

  1. Detects the platform (OS, distro, WSL2, container).
  2. Checks for an existing Tailscale installation.
  3. Installs Tailscale using the appropriate package manager.
  4. Verifies the installation and daemon status.
  5. Guides initial connection to the tailnet.

Platform detection

Detect the environment before selecting an install method. Check WSL2 first to avoid installing the Linux package inside a WSL2 instance.

1. Check WSL2 (but not containers running on WSL2)
   ├─ grep -qi microsoft /proc/version 2>/dev/null
   ├─ AND [ ! -f /.dockerenv ] (not a container)
   ├─ WSL2 → go to "WSL2 special case"
   └─ Not WSL2 (or container) → continue

2. Check OS
   ├─ uname -s → Linux → detect distro
   ├─ uname -s → Darwin → macOS
   └─ OS is Windows → PowerShell commands

3. Detect Linux distro
   ├─ . /etc/os-release && echo $ID
   ├─ debian, ubuntu → apt
   ├─ fedora, rhel, centos, amzn → dnf/yum
   ├─ arch, manjaro → pacman
   ├─ alpine → apk
   ├─ opensuse*, sles → zypper
   └─ other → curl one-liner fallback

Existing install check

Before installing, check if Tailscale is already present:

tailscale version 2>/dev/null

If installed:

  • Report the current version.
  • Check daemon status: sudo systemctl status tailscaled (Linux).
  • Check connection: tailscale status.
  • Stop here unless the user requests a reinstall or upgrade.

If not installed, proceed to installation.

WSL2 special case

WSL2 shares the Windows host network stack. Installing Tailscale inside WSL2 creates conflicting WireGuard tunnels. Do not install the Linux package in WSL2.

Detection (exclude containers running on WSL2 hosts):

grep -qi microsoft /proc/version 2>/dev/null && [ ! -f /.dockerenv ] && echo "WSL2 detected"

When WSL2 is detected:

  1. Check for Windows host Tailscale:

    tailscale.exe version 2>/dev/null
  2. If found — report version and verify with tailscale.exe status.
  3. If not found — instruct the user to install on the Windows host using WinGet, Chocolatey, or MSI (see references/platform-install-commands.md).
  4. Verify tailscale.exe is accessible from WSL2. If not, check that appendWindowsPath = true in /etc/wsl.conf under [interop].

Installation

Linux (most distros)

curl -fsSL https://tailscale.com/install.sh | sh

macOS

brew install --cask tailscale

Windows

winget install tailscale.tailscale

For distro-specific repo setup (apt, dnf, pacman, apk, zypper), Docker, Chocolatey, and MSI, see references/platform-install-commands.md.

Post-install verification

After installation, verify three things:

1. Binary is available

tailscale version

If not found, check PATH or restart the terminal session.

2. Daemon is running

# Linux (systemd)
sudo systemctl enable --now tailscaled
sudo systemctl status tailscaled

# macOS — open Tailscale from Applications
# Windows — check: Get-Service Tailscale

3. Connection status

tailscale status

If the device is not yet authenticated, proceed to initial connection.

Initial connection

Interactive (desktop/laptop)

sudo tailscale up

This prints an authentication URL. Open it in a browser to sign in.

Headless (server)

Generate an auth key in the admin console (Settings > Keys), then:

sudo tailscale up --authkey=tskey-auth-<key>

For tags, subnet routes, exit nodes, and all tailscale up flags, see references/post-install-checklist.md.

Error handling

Do not silently skip a failed installation. Report the error with specific remediation steps.

  • Permission denied — prefix with sudo or run as administrator.
  • Package not found — Tailscale repo not configured. Use the curl one-liner or add the repo manually (see references).
  • Network error — check internet connectivity and DNS resolution.
  • Daemon not starting — check logs with sudo journalctl -u tailscaled --no-pager -n 50. Verify no other VPN is bound to the same port.
  • Auth failure — expired auth key (regenerate in admin console), SSO misconfiguration, or device limit reached.

References

  • references/platform-install-commands.md — exhaustive per-platform install commands
  • references/post-install-checklist.md — verification steps, auth key options, common flags, and first-run troubleshooting

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.