bridge-dashboard

Stars8

Forks2

UpdatedJuly 18, 2026 at 17:14

Generates the Bridge Control Center — a single-file HTML dashboard that bundles Fleet (infra/remotes/), Work Board, Calendar (next 24h), Channels, Git activity, optional Bridge-Deck /metrics, and upstream drift into one view. Stands alone; the pixel-art Bridge-Deck renderer it can complement is not yet public (coming soon). Trigger: "/bridge-dashboard", "bridge dashboard", "control center", "ops dashboard", "open dashboard", "show me everything at a glance".

Installation

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.

Source

bks-lab

bks-lab/open-bridge

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Web DevelopersComputer and Mathematical Occupations·SOC 15-1254

File Explorer

2 files

SKILL.md

readonly

name	bridge-dashboard
description	Generates the Bridge Control Center — a single-file HTML dashboard that bundles Fleet (infra/remotes/), Work Board, Calendar (next 24h), Channels, Git activity, optional Bridge-Deck /metrics, and upstream drift into one view. Stands alone; the pixel-art Bridge-Deck renderer it can complement is not yet public (coming soon). Trigger: "/bridge-dashboard", "bridge dashboard", "control center", "ops dashboard", "open dashboard", "show me everything at a glance".
metadata	{"scope":"core"}

Bridge Dashboard

What it does

A Python generator — scripts/bridge-dashboard.py, a shared repo-root utility shipped with the Bridge repo itself (not inside this skill's own directory), stdlib + PyYAML only — aggregates the entire Bridge state in parallel and renders a self-contained HTML:

Tile	Source	Parallel probe
Fleet	`infra/remotes/*.yaml` + ICMP ping (Tailscale > LAN)	yes, 8 workers
Work Board	`work/board.md` (doing/backlog/done)	yes
Calendar 24h	`workflow/calendars/entries.yaml` + RRULE expander	yes
Channels	`infra/channels/*.yaml`	yes
Bridge-Deck (optional)	HTTP `http://homeserver:8791/metrics` — tile shows "offline" when absent	yes, 1.5s timeout
Git Activity	all repos from `ecosystem.yaml` via `git log --since=24h`	yes, 6 workers
Upstream	`HEAD..development`	yes
Events	last 10 lines from `work/log.md`	yes

Design: dark theme, cyan/amber, responsive 12-column grid. Sticky header with live counters. Auto-refresh every 30s via meta tag.

Usage

# Generate once → work/dashboard.html
python3 scripts/bridge-dashboard.py

# Generate and open in the browser
python3 scripts/bridge-dashboard.py --open

# Continuous mode: server on :8790, regenerate every 30s
python3 scripts/bridge-dashboard.py --serve

Serve mode is suited for launchd/cron on homeserver. A plist template lives in skills/bridge-dashboard/references/com.example.bridge-dashboard.plist.

Relationship to Bridge-Deck (optional — not yet public, coming soon)

	Bridge-Deck :8791	Bridge Dashboard :8790
Purpose	Ambient pixel-art office view	Ops-grade situational awareness
Tech	Node/React/Pixi + WS live	Python → HTML, 30s refresh
Runs where	homeserver (launchd, always on)	on-demand or launchd (optional)
Scope	Agents/Channels/Calendar	Fleet + Board + integrations-ready + Git

Both read the Bridge's YAML data read-only. No duplicate source.

Decision Tree

User wants to...
├── Quick morning check                  → python3 scripts/bridge-dashboard.py --open
├── Permanently on a 2nd monitor         → --serve + keep a browser tab open
├── Fleet status right now               → generate dashboard, top left
├── Integrate an integration tile (e.g. cloud-function health) → add a tile in scripts/bridge-dashboard.py (Phase 2 — planned)
└── Customize the dashboard              → edit scripts/bridge-dashboard.py

Data Sources & Invariants

Read-only: The script writes exclusively to work/dashboard.html. No changes to YAML/log/board.
Fail-soft: If a source is missing (e.g. bridge-deck offline), the tile shows "offline". Other tiles still run.
Timeouts: Ping 800ms, HTTP 1.5s, Git 3s per repo — the whole dashboard builds in <4s.
No secrets: The HTML contains only paths and metrics, no tokens.

Roadmap (non-blocking)

Integration tile: cloud-function health + log-error count via provider CLI.
Mail tile: unread mail from Microsoft Graph (via an org-overlay mail skill, if your bridge has one).
Telegram/Signal unread count.
Weekly sparkline: commits/day, log events/day.
Dark/light toggle.
PWA manifest for full-screen kiosk on iPad.

More from this repository

same repository

bridge-contribute

bks-lab/open-bridge

Contribute features and improvements from your Bridge back to the open-bridge OSS upstream (or your org overlay) as a fork-based pull request. Scans your user branch for upstream-worthy files, classifies them by scope, adapts org-specific content, runs the MANDATORY two-layer content-safety gate (leak scanner + per-repo blocklist, refuses on PII/customer hits), and opens the cross-fork PR with DCO sign-off — no upstream push access needed. Trigger: "/contribute", "contribute", "upstream contribution", "contribute to upstream", "contribute upstream", "submit improvement", "share my skill", "send this to open-bridge", "PR to upstream", "PR to overlay", "give back", "submit a feature".

2026-07-188

bridge-leak-check

bks-lab/open-bridge

Content-leak scanner with categorized classification. Different from a raw blocklist grep: each hit is sorted into legitimate-self-reference, legitimate-sister-repo, personal-PII (always leak), or internal-vocabulary hardcoded (OSS-strict only). Use after a sync to verify the destination is actually clean — catches pre-existing leaks the source-side scan won't see. Also runs OSS-strictness vocabulary checks (e.g. "scope: bks" hardcoded in OSS-shipped skill docs that should use "scope: org" placeholder). Trigger: "/bridge-leak-check", "leak scan", "leak check", "OSS readiness", "pre-existing leaks", "cleanliness check", "is this OSS clean".

2026-07-188

bridge-onboard

bks-lab/open-bridge

New user onboarding and reconfiguration — discovery-driven setup with permission-gated system scan, evidence-based feature suggestions, and a read-only catalogue of what else Bridge can do. Six-phase wizard (Identity / Discovery / Suggestions / Quick-Wins / Catalog / Validate) with re-entry modes for targeted later activation. Works without GitHub. Upstreams stay empty by default and wire later when the OSS upstream or your own upstream is live. Trigger: "/bridge-onboard", "onboard", "setup", "configure bridge", "new user", "ecosystem scan", "set up bridge", "reconfigure", "reconfigure bridge", "setup wizard".

2026-07-188

bridge-overlay

bks-lab/open-bridge

Subscribe a Bridge to an ORG OVERLAY — a git repo an organisation publishes that ships its shared config (contexts, projects, mandants, accounts, org skills/agents/standing-orders, an ecosystem fragment) as a flat mirror tree. /overlay add <git-url> sparse-clones the overlay, validates its manifest, previews a per-file plan with risk flags, and materializes COPIES into your repo under a lockfile — never block-merging your config, never clobbering your edits (3-way merge), never touching CORE. sync/apply/status/diff/remove/list manage the subscription over time. The overlay is the LOWER layer; your user files always win. Trigger: "/overlay", "org overlay", "subscribe to overlay", "materialize org config", "pull org overlay", "unsubscribe overlay", "add org config by git url", "list overlays", "overlay status", "overlay diff".

2026-07-188

bridge-promote

bks-lab/open-bridge

Promote CORE changes from your user branch to upstream (Scope-Routing per scope: core → OSS upstream, org → your org overlay, user → local). Analyzes commits, categorizes by CORE/USER/ORG path+frontmatter rules, runs mandatory content-safety checks per repo (leak scanner + blocklist, refuses on PII/customer hits), and creates fork-based PRs to upstream repos — no upstream push access needed. For file-level community contributions with adaptation, use the bridge-contribute skill (/contribute) instead. Trigger: "/bridge-promote", "promote", "cherry-pick", "push to upstream", "promote to upstream", "promote commits".

2026-07-188

bridge-status

bks-lab/open-bridge

Bridge health dashboard — shows branch, config, theme, ecosystem, agents, standing orders, work system, and repo status. Flags missing files, KW drift, and configuration problems. Includes documentation health and link checking. Trigger: "/bridge-status", "bridge status", "bridge health", "health check", "docs health", "link check", "documentation quality", "pre-release gate". (Bare "bridge" and bare "status" are intentionally NOT triggers — too broad, would collide with bridge-sync/bridge-dashboard/briefing.)

2026-07-188

name	bridge-dashboard
description	Generates the Bridge Control Center — a single-file HTML dashboard that bundles Fleet (infra/remotes/), Work Board, Calendar (next 24h), Channels, Git activity, optional Bridge-Deck /metrics, and upstream drift into one view. Stands alone; the pixel-art Bridge-Deck renderer it can complement is not yet public (coming soon). Trigger: "/bridge-dashboard", "bridge dashboard", "control center", "ops dashboard", "open dashboard", "show me everything at a glance".
metadata	{"scope":"core"}

Bridge Dashboard

What it does

Tile	Source	Parallel probe
Fleet	`infra/remotes/*.yaml` + ICMP ping (Tailscale > LAN)	yes, 8 workers
Work Board	`work/board.md` (doing/backlog/done)	yes
Calendar 24h	`workflow/calendars/entries.yaml` + RRULE expander	yes
Channels	`infra/channels/*.yaml`	yes
Bridge-Deck (optional)	HTTP `http://homeserver:8791/metrics` — tile shows "offline" when absent	yes, 1.5s timeout
Git Activity	all repos from `ecosystem.yaml` via `git log --since=24h`	yes, 6 workers
Upstream	`HEAD..development`	yes
Events	last 10 lines from `work/log.md`	yes

Design: dark theme, cyan/amber, responsive 12-column grid. Sticky header with live counters. Auto-refresh every 30s via meta tag.

Usage

# Generate once → work/dashboard.html
python3 scripts/bridge-dashboard.py

# Generate and open in the browser
python3 scripts/bridge-dashboard.py --open

# Continuous mode: server on :8790, regenerate every 30s
python3 scripts/bridge-dashboard.py --serve

Serve mode is suited for launchd/cron on homeserver. A plist template lives in skills/bridge-dashboard/references/com.example.bridge-dashboard.plist.

Relationship to Bridge-Deck (optional — not yet public, coming soon)

	Bridge-Deck :8791	Bridge Dashboard :8790
Purpose	Ambient pixel-art office view	Ops-grade situational awareness
Tech	Node/React/Pixi + WS live	Python → HTML, 30s refresh
Runs where	homeserver (launchd, always on)	on-demand or launchd (optional)
Scope	Agents/Channels/Calendar	Fleet + Board + integrations-ready + Git

Both read the Bridge's YAML data read-only. No duplicate source.

Decision Tree

User wants to...
├── Quick morning check                  → python3 scripts/bridge-dashboard.py --open
├── Permanently on a 2nd monitor         → --serve + keep a browser tab open
├── Fleet status right now               → generate dashboard, top left
├── Integrate an integration tile (e.g. cloud-function health) → add a tile in scripts/bridge-dashboard.py (Phase 2 — planned)
└── Customize the dashboard              → edit scripts/bridge-dashboard.py

Data Sources & Invariants

Read-only: The script writes exclusively to work/dashboard.html. No changes to YAML/log/board.
Fail-soft: If a source is missing (e.g. bridge-deck offline), the tile shows "offline". Other tiles still run.
Timeouts: Ping 800ms, HTTP 1.5s, Git 3s per repo — the whole dashboard builds in <4s.
No secrets: The HTML contains only paths and metrics, no tokens.

Roadmap (non-blocking)

Integration tile: cloud-function health + log-error count via provider CLI.
Mail tile: unread mail from Microsoft Graph (via an org-overlay mail skill, if your bridge has one).
Telegram/Signal unread count.
Weekly sparkline: commits/day, log events/day.
Dark/light toggle.
PWA manifest for full-screen kiosk on iPad.