node-connect

Diagnose Brikko Studio node-to-gateway connection and pairing failures across network topologies.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/brikkoAI/brikko-studio --skill node-connect-brikkoai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-connect
Source: https://github.com/brikkoAI/brikko-studio/tree/main/packages/core/skills/node-connect
Command: npx skills add https://github.com/brikkoAI/brikko-studio --skill node-connect-brikkoai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the frustration of failed Brikko Studio node connections by providing a structured, topology-first approach to diagnose and fix pairing, routing, and authentication issues for Android, iOS, and macOS nodes, no guesswork required.

Core Features & Use Cases

  • Topology-first diagnosis: Automatically distinguishes between local USB, same Wi-Fi, Tailscale tailnet, and public URL network setups to avoid misapplied fixes.
  • Targeted error resolution: Addresses common failure points including loopback-only gateway binding, expired bootstrap tokens, unauthorized access denials, and pending device approval issues.
  • Use case: For example, if your mobile Brikko Studio app shows "pairing required" after scanning a QR code, this Skill guides you to verify the correct gateway route and approve the pending device in seconds.

Quick Start

Use the node-connect skill to diagnose why your Brikko Studio mobile app cannot connect to the gateway after scanning the setup QR code.

Frequently Asked Questions about node-connect

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

FAQPage Schema
How do I fix Brikko Studio node pairing errors after scanning the QR code?

Brikko Studio node pairing errors are resolved by diagnosing the network topology and verifying gateway configuration via canonical CLI commands. This targets expired bootstrap tokens or pending device approvals to restore connectivity.

Why does my Brikko Studio mobile app show unauthorized access denied on Tailscale?

Unauthorized access denials on Tailscale happen when advertised routes or device approvals are misconfigured. Running Brikko Studio CLI commands to verify gateway status and approve the pending node within the tailnet resolves the issue.

How do I troubleshoot an expired bootstrap token for Brikko Studio device pairing?

To troubleshoot an expired bootstrap token, run canonical Brikko Studio CLI commands to verify the gateway configuration and re-establish the device pairing. This refreshes the connection credentials across local or Tailscale networks.

Does Brikko Studio node connection troubleshooting work for both iOS and macOS?

Brikko Studio node connection troubleshooting supports Android, iOS, and macOS platforms. It systematically diagnoses pairing and routing failures across local, LAN, Tailscale, and public URL network topologies for these operating systems.

What is the best way to resolve pending device approval issues in Brikko Studio?

Resolving pending device approval issues involves verifying advertised routes and gateway binding using Brikko Studio CLI commands. This confirms the device is visible on the correct LAN or Tailscale topology for final approval.

Why is my Brikko Studio node connection not working over local Wi-Fi?

Brikko Studio node connections fail over local Wi-Fi when the gateway is bound to loopback only. Verifying gateway configuration and advertised routes via CLI commands ensures the node achieves proper LAN visibility.