메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Set up the Discord bot — configure token, daemon URL, guild channels. Use when user says "configure discord", "set discord token", "discord setup", "discord bot setup".
This skill should be used when the user asks to "set up bridgey", "check bridgey status", "add a bridgey agent", or "scan the tailnet for bridgey". Lifecycle surface for the bridgey A2A daemon — first-time setup, health dashboard, remote-agent registration, and Tailscale mesh discovery.
Deploy an agent to a remote server as a Docker container with Tailscale SSH access, optional Coolify integration, and bidirectional sync. Walks through server setup, hardening, Tailscale, Docker, deployment, and post-install tooling. Use when the user asks to deploy an agent remotely, set up a remote server, run an agent 24/7, or make an agent headless.
Sync agent files between local and remote server. Use when the user says "sync", "push to remote", "pull from remote", "sync agent", or runs /sync.
Manage Discord sender access — allow/deny senders, set DM policy. Use when user says "discord access", "allow discord user", "deny discord user", "discord pairing".
| name | remote-status |
| description | 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. |
Check the health of the remote agent deployment. Connection details are read from bridgey-deploy.config.json in the agent's root directory. The container check applies to both deployment models; the daemon-health check is Tier-B only — for a Tier-A deployment the live Channels session is the health signal, so treat the daemon probe as skippable.
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-card.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: