agentleFS
tjg37tjg37/ironclaw/.claude/skills/add-remote-access/SKILL.md

add-remote-access

Skill1 starsChanged 7 months agoMITView on GitHub

Set up remote access to IronClaw via Tailscale (private VPN)

  • Reads credentials
  • Installs packages

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 6 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check if Tailscale is installed:

    line 12
  2. Distinctive:

    If not installed, tell the user:

    line 17
  3. Distinctive:

    If not connected, tell the user to open the Tailscale menu bar app and sign in.

    line 27
  4. Very specific:

    Check if IRONCLAW_WEB_PASSWORD is set in the web package's env:

    line 33
  5. Distinctive:

    If not set, use AskUserQuestion to ask the user to enter a password.

    line 38
  6. Very specific:

    Update the root .env with the Tailscale IP for CORS:

    line 55
  7. Very specific:

    Update packages/web/.env.local so the web app connects to the gateway via the Tailscale IP:

    line 60
  8. Distinctive:

    Ask the user to confirm they can:

    line 75
  9. Distinctive:

    If the web app loads but WebSocket fails (connected indicator shows red):

    line 81
  10. Very specific:

    Check that CORS_ALLOWED_ORIGIN in .env matches http://<TAILSCALE_IP>:3000

    line 82
  11. Very specific:

    Check that NEXT_PUBLIC_GATEWAY_TOKEN in packages/web/.env.local matches GATEWAY_WS_TOKEN in .env

    line 83
  12. Very specific:

    If the Tailscale IP changes, re-run /add-remote-access to update the config

    line 96

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

/add-remote-access — Remote Access Setup

Set up remote access so you can use the IronClaw web app from your phone or other devices while it runs locally on your machine. Uses Tailscale — a private mesh VPN that's free for personal use.

Step 1: Check Prerequisites

Check if Tailscale is installed:

which tailscale 2>/dev/null || ls /Applications/Tailscale.app 2>/dev/null && echo "INSTALLED" || echo "NOT_INSTALLED"

If not installed, tell the user:

  • Download from https://tailscale.com/download/mac (installs as a menu bar app)
  • On iPhone/Android: search "Tailscale" in the App Store / Play Store
  • Note: brew install tailscale does NOT work — must download from the website

Check if connected:

/Applications/Tailscale.app/Contents/MacOS/Tailscale status 2>/dev/null | head -5 || tailscale status 2>/dev/null | head -5

If not connected, tell the user to open the Tailscale menu bar app and sign in. Both devices (Mac and phone) must be signed into the same Tailscale account.

Step 2: Ensure Web Authentication is Enabled

CRITICAL: Remote access without authentication means anyone on your tailnet can access your agent.

Check if IRONCLAW_WEB_PASSWORD is set in the web package's env:

grep -q "^IRONCLAW_WEB_PASSWORD=." packages/web/.env.local 2>/dev/null && echo "SET" || echo "NOT_SET"

If not set, use AskUserQuestion to ask the user to enter a password. Then add it:

printf "\nIRONCLAW_WEB_PASSWORD=%s\n" "USER_PASSWORD" >> packages/web/.env.local

Also ensure the root .env has GATEWAY_WS_TOKEN set (should already be from /setup):

grep -q "^GATEWAY_WS_TOKEN=." .env 2>/dev/null && echo "SET" || echo "NOT_SET"

Step 3: Get Tailscale IP and Configure

Get the Tailscale IP:

/Applications/Tailscale.app/Contents/MacOS/Tailscale ip -4 2>/dev/null || tailscale ip -4 2>/dev/null

Update the root .env with the Tailscale IP for CORS:

grep -q "^CORS_ALLOWED_ORIGIN=" .env && sed -i '' "s|^CORS_ALLOWED_ORIGIN=.*|CORS_ALLOWED_ORIGIN=http://<TAILSCALE_IP>:3000|" .env || echo "CORS_ALLOWED_ORIGIN=http://<TAILSCALE_IP>:3000" >> .env

Update packages/web/.env.local so the web app connects to the gateway via the Tailscale IP:

grep -q "^NEXT_PUBLIC_GATEWAY_URL=" packages/web/.env.local && sed -i '' "s|^NEXT_PUBLIC_GATEWAY_URL=.*|NEXT_PUBLIC_GATEWAY_URL=ws://<TAILSCALE_IP>:18789|" packages/web/.env.local || echo "NEXT_PUBLIC_GATEWAY_URL=ws://<TAILSCALE_IP>:18789" >> packages/web/.env.local

Replace <TAILSCALE_IP> with the actual IP from the command above.

Tell the user:

  1. Restart IronClaw: pnpm start:all
  2. On their phone: install Tailscale, sign into the same account
  3. Open http://<TAILSCALE_IP>:3000 in the browser
  4. Log in with their password

Step 4: Verify Connectivity

Ask the user to confirm they can:

  1. Open http://<TAILSCALE_IP>:3000 from their phone
  2. See the login page
  3. Log in successfully
  4. Send a chat message and receive a response

If the web app loads but WebSocket fails (connected indicator shows red):

  • Check that CORS_ALLOWED_ORIGIN in .env matches http://<TAILSCALE_IP>:3000
  • Check that NEXT_PUBLIC_GATEWAY_TOKEN in packages/web/.env.local matches GATEWAY_WS_TOKEN in .env

Step 5: Confirm

Show a summary:

  • Tailscale IP: <IP>
  • Web app URL: http://<IP>:3000
  • Gateway URL: ws://<IP>:18789
  • Authentication: enabled

Remind the user:

  • Access is private to their Tailscale account — no one else can reach it
  • Both devices must stay connected to Tailscale
  • If the Tailscale IP changes, re-run /add-remote-access to update the config

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.