Adom USB
Public Unreviewedby John Lauer
See every USB device across the entire Adom ecosystem — laptop, WSL2, cloud container, Azure VM, workcells — in one dashboard, and mount / unmount / reset / test / force-class / sniff any of them. USB/IP slingshot for the whole mesh.
Skills
The skills this repo ships, by tier, each with a quick health read. Install the user skills with:
adom-wiki skills install john/adom-usbdev-skills/ or publish-skills/, so a contributor (or their AI) has no in-repo guide to build, debug, or publish it. Consider adding them; they stay source-only and never ship in the tarball.How to publish or republish adom-usb and its plugins to the Adom Wiki (wiki.adom.inc). Carries the naming + hero + publish-order conventions for the whole Adom USB family so they travel with the repo. Use when: release adom-usb, publish adom-usb, cut an adom-usb version, publish an adom-usb plugin, add a new USB sniffer/firmware plugin to the wiki, fix an adom-usb hero, rename a plugin title. Trigger words: publish adom-usb, release adom-usb, bump adom-usb, adom-usb plugin publish, adom-usb wiki, adom-usb hero, name an adom-usb plugin.
USB device mesh dashboard. See every USB device across the whole Adom ecosystem — your laptop, its WSL2 / Hydrogen Desktop, this cloud container, the Azure VM and its WSL2, and workcells — in one Hydrogen webview, with Local/Cloud filters and per-device mount/unmount/reset/test/force-class/sniff. Trigger words: usb, usb devices, usb dashboard, list usb, mount usb, unmount usb, attach usb, usbip, usb/ip, slingshot usb, mount my dev board, rp2040 to wsl2, mount device to container, usb mesh, where is my usb device, force hid, force mass storage, sniff usb, usb passthrough, plug in dev board.
No dev skills in this repo.
How to build, debug, and test this app. Source-only (dev-skills/), never shipped in the tarball.
No publish skills in this repo.
The app-to-wiki publish glue. Source-only (publish-skills/), never shipped in the tarball.
Health: the size chip is green when right-sized, yellow when getting long, red when the model likely skims it. A green check is a passed preamble/structure signal; an amber mark is a gentle nudge, not a hard failure.