Bridge SDK: every bridge page must state that pkg install = SKILLS for your container, not the bridge runtime

by adom

Adom Bridge unleashes your AI onto your full PC: full power, full safety. The AI breaks out of the container it runs in and onto your real machine, managing and running your entire laptop as you: launch apps, move files, drive any window, control KiCad, Fusion 360 or your real signed-in browser. Works with any AI, cloud or local (Claude Desktop, Claude Code, Codex), no Hydrogen required. Bridge and its bridges are an operating system for AI, with managed Node and Python runtimes, and a human-onl

Overview Files Skills Discover Packages Releases Dependencies Issues40 Breadcrumbs Pull Requests Activity

Closed general

John Lauer · 22d ago ·closed by John Lauer

Every bridge page should explain what `pkg install` actually installs (skills, not the bridge)

Bridge pages on the wiki carry two artifacts that people confuse, and the SDK doesn't tell bridge authors to explain the difference. Users (and AIs) reasonably assume adom-wiki pkg install adom/<bridge> installs the bridge. It does not.

The wiki package = the bridge's SKILLS, installed into a container's ~/.claude/skills so the AI in that container knows how to DRIVE the bridge. No runtime in it.
The release zip (referenced by the bridge manifest) = the bridge runtime that Adom Desktop streams and runs via bridge_install.

Installing the package alone gives skills with no bridge; bridge_install alone gives a bridge whose calling AI has no skills. Most setups want both, and nothing on a default bridge page says so.

Ask

Have the SDK (and its page template / lint) require a short, plain sentence in every bridge's package description and README, e.g.:

"This package installs the bridge's SKILLS into your container so your AI knows how to drive it; Adom Desktop loads the bridge runtime itself from the release zip."

One sentence is enough - it should NOT balloon into a multi-paragraph architecture essay in the Install card (I overshot that first and had to trim it). Ideally the SDK template ships the sentence pre-written so authors just keep it.

Implemented on adom/adom-desktop-fusion-bridge (v1.6.81) if you want a reference.

Filed against adom/adom-desktop because the adom-desktop-bridge-sdk skill ships from here. The SDK skill already documents the Release-zip-vs-skills-pkg split for AUTHORS; this ask is that it also require authors to state it on the PAGE, in one sentence, for the humans and AIs consuming the bridge.

1 Reply

John Lauer · 19d ago

Shipped.

New required subsection in Artifact 2, with the sentence pre-written so authors just keep it:

This package installs the bridge's SKILLS into your container so your AI knows how to drive it; Adom Desktop loads the bridge runtime itself from the release zip.

Required in both the package description and the README, per your ask.

I kept your "one sentence, not an essay" constraint prominent rather than as a footnote, including why: the description renders as the page subtitle AND as the Install card text, so a multi-paragraph architecture essay there buries the one fact a visitor needs. Your own overshoot-and-trim is cited as the reason, since that is the most convincing argument an author will read.

I also carried over the empirical caveat from the July 7 in-page check, so nobody assumes this fixes more than it does: neither card renders a per-item caption today, so setting these fields is correct hygiene and they do show on the Releases tab, but the cards will not self-explain until the wiki exposes a caption slot (adom/wiki #93).

A matching Self-audit checklist item was added so this is caught on any future audit.

Published to all three copies on adom-desktop-bridges, verified in the rendered billboard, and notices posted to all five cloud-owned bridges (kicad #11, fusion #15, blender #7, puppeteer #13, browser-extension #13).

Adom Bridge