Menu
Show Bridge IDE system status — health, active agents, open tasks, and server info. Use when checking system health or asking "what's running?".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Browser automation for protected sites. This skill should be used when navigating websites with advanced protection layers (Cloudflare, DataDome, Akamai), performing browser automation that requires natural interaction patterns, or when standard Playwright fails due to compatibility issues. Covers Camoufox, CDP, Patchright, fingerprint management, captcha handling, and natural behavior simulation.
Core skill for all Bridge IDE agents. This skill should be used for bridge communication, task management, agent coordination, and understanding the Bridge IDE platform. Covers bridge_register, bridge_send/receive, task lifecycle, approval gates, and team coordination patterns.
Restart a Bridge IDE agent by ID. Use when an agent is stuck, crashed, or needs to be restarted. Accepts agent ID as argument (e.g. /agent-restart backend).
Deploy Bridge IDE — Server-Restart mit Health-Check und Agent-Benachrichtigung. Use when deploying changes, restarting the server, or applying backend updates.
Use when completing any task via bridge_task_done, claiming work is finished, or about to report task results on the Bridge platform - requires concrete verification evidence with command output before any completion claim
PFLICHT vor jeder externen Aktion. Wird automatisch geladen wenn ein Agent mit externen Services interagiert, Browser-Aktionen durchfuehrt, Accounts verwaltet, APIs aufruft, Dateien auf fremden Systemen aendert, oder Credentials benoetigt. Erzwingt systematische Analyse VOR dem Handeln. IMMER laden wenn: Login, Signup, API-Call, Browser-Aktion, Deployment, Account-Management, DNS-Aenderung, Domain-Verwaltung, Payment, oder jede andere Interaktion mit der Aussenwelt.
| name | bridge-status |
| description | Show Bridge IDE system status — health, active agents, open tasks, and server info. Use when checking system health or asking "what's running?". |
| allowed-tools | Bash, Read |
Vollstaendiger System-Ueberblick in einem Aufruf.
curl -s http://127.0.0.1:9111/health | python3 -m json.tool
curl -s http://127.0.0.1:9111/agents | python3 -c "
import json, sys
data = json.load(sys.stdin)
agents = data.get('agents', [])
online = [a for a in agents if a.get('online')]
offline = [a for a in agents if not a.get('online') and a.get('active', True)]
print('=== ONLINE AGENTS ===')
for a in online:
engine = a.get('engine', '?')
print(f\" {a['id']:20s} {a.get('role',''):40s} [{engine}]\")
print(f\"\n Total online: {len(online)}\")
if offline:
print('\n=== OFFLINE (aber active in team.json) ===')
for a in offline:
print(f\" {a['id']:20s} {a.get('role','')}\")
"
curl -s http://127.0.0.1:9111/activity | python3 -c "
import json, sys
data = json.load(sys.stdin)
for act in data.get('activities', []):
idle = ' [IDLE]' if act.get('idle') else ''
print(f\" {act.get('agent_id','?'):20s} {act.get('action',''):15s} {act.get('target','')}{idle}\")
"
curl -s 'http://127.0.0.1:9111/task/queue?state=created' | python3 -c "
import json, sys
data = json.load(sys.stdin)
tasks = data.get('tasks', [])
print(f'=== OFFENE TASKS ({len(tasks)}) ===')
for t in tasks:
assigned = t.get('assigned_to', 'unassigned')
print(f\" [{t.get('priority','?')}] {t['title'][:60]:60s} → {assigned}\")
"
curl -s http://127.0.0.1:9111/status | python3 -c "
import json, sys
data = json.load(sys.stdin)
uptime = data.get('uptime_seconds', 0)
hours = int(uptime // 3600)
mins = int((uptime % 3600) // 60)
print(f\"Server: {data.get('status','?')} | Port: {data.get('port','?')} | Uptime: {hours}h {mins}m | Messages: {data.get('messages_total', 0)}\")
"
Der Skill liefert eine strukturierte Zusammenfassung:
Server: running | Port: 9111 | Uptime: 2h 30m | Messages: 1847
Online: 5 agents | Offline: 2 agents | Tasks: 3 open