plugins/bridgey-deploy/skills/remote-status/SKILL.md
Check the health and status of the remote agent deployment. Use when the user says "remote status", "check remote", "is my agent running", "server status", or runs /remote-status.
npx skillsauth add kickinrad/bridgey remote-statusInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Check the health of the remote agent deployment. Connection details are read from bridgey-deploy.config.json in the agent's root directory.
Read bridgey-deploy.config.json to get:
tailscale_host — the Tailscale hostname of the remote serverremote_path — the path on the remote servercontainer_name — the Docker container nameIf bridgey-deploy.config.json doesn't exist, ask the user for connection details.
Run these commands via SSH and report results:
ssh {tailscale_host} "docker ps --filter name={container_name} --format '{{.Status}}'"
Report: running/stopped, uptime.
Check if the bridgey daemon is responding inside the container:
ssh {tailscale_host} "docker exec {container_name} curl -sf http://localhost:3000/.well-known/agent.json 2>/dev/null && echo 'daemon: healthy' || echo 'daemon: not running or not responding'"
Report: daemon healthy/unhealthy, agent card details if available.
ssh {tailscale_host} "df -h {remote_path} | tail -1"
Report: used/available space.
ssh {tailscale_host} "find {remote_path}/user/memory -name '*.md' -printf '%T@ %p\n' 2>/dev/null | sort -rn | head -1"
Report: last memory file modification time (proxy for last agent activity).
ssh {tailscale_host} "docker logs {container_name} --tail 10 2>&1"
Report: last 10 lines of container output.
Present as a concise status report:
testing
This skill should be used when the user asks to "set up bridgey", "configure bridgey", "initialize bridgey", "bridgey setup", "check bridgey status", "show bridgey agents", "is bridgey running", "bridgey health", "show connected agents", "add a bridgey agent", "connect to another agent", "register a remote agent", "add remote agent", "configure tailscale for bridgey", "scan tailnet for bridgey", or runs `/bridgey:setup`, `/bridgey:status`, `/bridgey:add-agent`, `/bridgey:tailscale-setup`, `/bridgey:tailscale-scan`. Lifecycle surface for the bridgey A2A daemon — first-time setup, health dashboard, remote-agent registration, and Tailscale mesh discovery.
data-ai
First-time Tailscale mesh network configuration for bridgey. Updates daemon binding for tailnet access and runs initial peer scan.
data-ai
Manually scan the Tailscale network for bridgey agents. Shows discovered, new, and removed agents.
testing
This skill should be used when the user asks to "check bridgey status", "show bridgey agents", "is bridgey running", "bridgey health", "show connected agents", runs "/bridgey:status", or wants to see the state of the bridgey daemon and connected agents.