Skip to content
Back to skills

Bridge Explorer

ASecurity

Bridge visualizations: ecosystem map (repos, workspaces, skills, infra), repo layout (CORE/USER split), and constellation (information flow). Trigger: "/bridge-explorer", "explorer", "show ecosystem", "repo layout", "where do files live", "constellation".

  • 10 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 5, 2026
ai-agentspythonnode

Works with

  • cli

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 26, 2026

npx -y skills add bks-lab/open-bridge --skill bridge-explorer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Bridge Explorer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Bridge Explorer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bks-lab-bridge-explorer/badge)](https://www.skillsdirectory.com/skills/bks-lab-bridge-explorer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: bridge-explorer
description: >-
  Bridge visualizations: ecosystem map (repos, workspaces, skills, infra), repo
  layout (CORE/USER split), and constellation (information flow). Trigger:
  "/bridge-explorer", "explorer", "show ecosystem", "repo layout", "where do
  files live", "constellation".
metadata:
  scope: core
---

# Bridge Explorer

Visualize Bridge state as interactive HTML dashboards.
Read the referenced file ONLY when triggered.

## Decision Tree

```
User wants to...
├── Ecosystem visualization            → Read references/workflow.md
├── CORE/USER repo split visual        → Read references/repo-layout.md
│   (triggers: "repo layout", "core/user", "where do files live",
│    "repo structure"; pick variant v1–v4 or c-prime, see below)
├── Information flow / network         → Render + open the network variant
│   (triggers: "network diagram", "constellation", "how is everything linked",
│    "how does the bridge distribute information", "layers")
└── Questions about ecosystem          → Read ecosystem.yaml directly
```

## Repo-layout variants

All variants render the same CORE/USER + cluster-wrapper split, sourced from
`docs/repo-layout/regions.yaml` (single source of truth — edit there, all
variants pick up on regenerate).

**Constellation (`network`) is generated, not hand-edited.** Its nodes/edges/flows
live in `regions.yaml` under `constellation:` (schema v3). After editing them run:

```
python3 docs/repo-layout/build-constellation.py
```

This injects the JS data block into `network.html` between the `CONSTELLATION-DATA`
markers and bumps the version badge. **Precondition:** `network.html` must have been
rendered first — the script refreshes the data block of an existing rendered file;
on a fresh clone there is no `network.html` yet, so render it via this skill first.
Wire it into your deploy pipeline so the served HTML never drifts from
`regions.yaml` by hand.

| Variant | Lens |
|---------|------|
| c-prime | Editorial cluster/top-level map (primary, dense) |
| network | **Constellation** — 5-ring information network (hub → brain → synapses → memory → state → world), 4 sectors (Meta · Operations · CustomerA · Identity), bundled edges, named flows |
| v1 | Hemispheric brain (CORE left, USER right) — static SVG |
| v2 | Brain with anatomical region labels + side panel |
| v3 | Interactive brain — click region for drill-down |
| v4 | Minimal two-column schematic — dense, print-friendly |

User-facing MOC: [`docs/repo-layout.md`](../../docs/repo-layout.md).

Files in this skill

  • SKILL.md2.8 KB
  • references/repo-layout.md17.3 KB
  • references/workflow.md3.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.