From tailscale
Configure a local dev server for access from Tailscale-connected devices.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tailscale:dev-server-accessThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Configure a local dev server for access from Tailscale-connected devices.
Configure a local dev server for access from Tailscale-connected devices.
tailscale status
tailscale status --self --json | jq '.Self.DNSName, .TailscaleIPs[0]'
Deno/Fresh:
await server.listen({ hostname: "0.0.0.0", port: 8000 });
Node/Vite/Next:
vite --host 0.0.0.0
next dev -H 0.0.0.0
| Method | Format |
|---|---|
| MagicDNS | http://<machine-name>:<port>/ |
| FQDN | http://<name>.<tailnet>.ts.net:<port>/ |
| IP | http://<tailscale-ip>:<port>/ |
| Issue | Fix |
|---|---|
| Connection refused | Bind to 0.0.0.0, not 127.0.0.1 |
| Port in use | lsof -i :<port> → kill <pid> |
| Can't resolve name | Enable MagicDNS in admin console |
| Device offline | Activate Tailscale VPN on target |
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
npx claudepluginhub kecbigmt/cc-plugins --plugin tailscale