skills.rest
enclawed
enclawedCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

node-connect

Diagnose Enclawed node connection and pairing failures across Android, iOS, and macOS routes.

2|Updated May 23, 2026
Search Tags:#ios#macos#android#tailscale#node#gateway#pairing
One-click install
npx skills add https://github.com/enclawed/enclawed-oss --skill node-connect-enclawed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: node-connect
Source: https://github.com/enclawed/enclawed-oss/tree/main/skills/node-connect
Command: npx skills add https://github.com/enclawed/enclawed-oss --skill node-connect-enclawed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill diagnoses why an Enclawed companion app cannot connect or pair with the node, especially when the route, authentication, or bootstrap setup is mismatched.

Core Features & Use Cases

  • Route Diagnosis: Distinguishes between same-machine, local LAN, Tailscale tailnet, and public URL setups so fixes target the real network path.
  • Pairing and Auth Checks: Guides you through setup codes, pending device approval, expired bootstrap tokens, and authorization mismatches.
  • Configuration Verification: Checks gateway bind mode, remote URL, Tailscale settings, and QR output to confirm the gateway is advertising the correct endpoint.

Quick Start

Ask the assistant to inspect the connection failure, identify the intended route, verify the gateway and pairing settings, and give the single concrete fix that matches the exact error message.

Frequently Asked Questions about node-connect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix Enclawed companion app pairing failures on iOS and Android?▼

Enclawed node connection failures are diagnosed by identifying the intended route, verifying gateway bind mode, and checking pairing settings to isolate the exact connection path. This process isolates whether the failure stems from network path mismatches or gateway advertising issues.

How do I troubleshoot Enclawed manual connect or QR setup errors?▼

Troubleshoot Enclawed QR setup and manual connect errors by verifying the QR output confirms the correct endpoint and checking the gateway remote URL configuration. This ensures the gateway is actively advertising the correct route for device authorization.

Does Enclawed companion app connection work with Tailscale tailnet routing?▼

Enclawed companion app connection supports Tailscale tailnet routing by verifying Tailscale settings alongside gateway bind mode to confirm the correct endpoint. Route diagnosis distinguishes Tailscale setups from same-machine, LAN, and public URL configurations to target the real network path.

Why does my Enclawed node connection fail over a public URL?▼

Enclawed node connection fails over a public URL when the gateway remote URL configuration is mismatched or the gateway is not advertising the correct endpoint. Verifying the public URL route and gateway bind mode isolates the connection path failure.

What is the best way to diagnose an Enclawed gateway advertising mismatch?▼

The best way to diagnose an Enclawed gateway advertising mismatch is to inspect the gateway bind mode, remote URL, and QR output to confirm the gateway is advertising the correct endpoint. This isolates the correct connection path for companion apps.

Related Skills

Explore More Software Engineering Skills→
jonaschenjonaschen
40

connectivity-network-expert

Diagnose Android connectivity failures by comparing ConnectivityService policy with netd routing behavior.

Community
Advanced
qianleigoodqianleigood
30

node-connect

Diagnose CrawClaw node pairing failures across Android, iOS, and macOS.

Community
Intermediate
vut08905vut08905

node-connect

Diagnose and repair node-to-gateway pairing and routing failures.

Community
Advanced
ryukyagamilightryukyagamilight
1

network-tools

Diagnose Linux network issues with command-line tools for connectivity, ports, and traffic.

Community
Intermediate