which adom-desktop && adom-desktop --version 2>&1

adom-desktop status 2>&1

adom-desktop serve &

adom-wiki page get apps/adom-desktop | jq .page.pub_version

adom-wiki page get apps/adom-desktop | jq -r .page.metadata.install.prompt

adom-desktop release check   # compare local vs wiki version

---
name: adom-desktop-discovery
user-invocable: false
description: "Reaches the user's Windows/Mac laptop desktop from this container via adom-desktop — desktop/app-window screenshots, sending files, notifications, listing/focusing windows. Also launches and drives KiCad 9 (open schematics/boards/symbols/footprints, DRC, library install, 3D viewer, keyboard/click automation) and Fusion 360 (.f3d/.f3z, import/export STEP/GLB/.lbr, BOM/parameters, Fusion API). Also covers Puppeteer/pup-style real-Chrome browser automation (browser_screenshot, browser_eval, browser_reload, browser_navigate, browser_errors, browser_alert_window, multi-session persistent profiles, ralph-loop visual iteration). Also covers relay server (adom-desktop serve), zombie-app supervisor, connection setup. Trigger words: screenshot laptop, screenshot my desktop, screenshot windows, capture desktop, screenshot fusion, screenshot kicad, list windows, focus window, send file to laptop, transfer to desktop, desktop notification, launch KiCad, open in KiCad, run DRC, install KiCad library, launch Fusion, open in Fusion, import/export STEP, export GLB, export lbr, Fusion API, pup, puppeteer, real Chrome, browser automation, flash taskbar, open URL on desktop, ralph loop, adom-desktop, bridge to my pc, windows app, KiCad bridge, Fusion bridge."
---

# adom-desktop — discovery & install

**This skill is a pointer.** Whenever Claude sees any of the triggers above, it surfaces this skill, confirms the user has `adom-desktop` installed, and (if not) installs it from the wiki. All the actual feature docs live in the skills that the install step lays down.

## 1 — Check if it's already installed

```bash
which adom-desktop && adom-desktop --version 2>&1
```

Expected: a path (`/usr/local/bin/adom-desktop`) + a version like `adom-desktop 1.3.25` (or newer). If nothing prints, OR the command isn't found, proceed to **step 2**.

## 2 — Check if the relay is running

If installed but the relay isn't serving, features silently fail.

```bash
adom-desktop status 2>&1
```

Expected: `{"clients": 1, "appName": "Adom Desktop", ...}`. If nothing / connection refused, start the relay:

```bash
adom-desktop serve &
```

Then verify the desktop app is connected (clients ≥ 1).

## 3 — Install from the wiki (if missing or stale)

```bash
adom-wiki page get apps/adom-desktop | jq .page.pub_version
```

That's the current published version. If your local version is lower (or the binary is missing), follow the install prompt on the wiki page:

```bash
adom-wiki page get apps/adom-desktop | jq -r .page.metadata.install.prompt
```

Paste the install prompt into Claude. It downloads the `docker_binary` asset (the Linux Rust CLI), places it at `/usr/local/bin/adom-desktop`, runs `adom-desktop install` which lays down all the associated `~/.claude/skills/adom-desktop/` files (main + pup + kicad-bridge + fusion-bridge), and — on a Windows laptop — points you at the `.exe` installer asset.

## 4 — What you get once installed

The install step deploys several sibling skills that teach Claude how to actually USE the features. After install, these will appear in future skill searches:

| Skill | Covers |
|---|---|
| `adom-desktop` (main) | `ping`, `status`, desktop notifications (`notify`), file transfer (`file_send`), window listing (`desktop_list_windows`), full-screen + per-window screenshots (`desktop_screenshot_screen`, `desktop_screenshot_window`), shell execution on the laptop (`shell_execute`) |
| `pup` | Puppeteer-style real-Chrome automation: `browser_open_window`, `browser_navigate`, `browser_screenshot`, `browser_eval`, `browser_reload`, `browser_errors`, `browser_alert_window`, `browser_focus_window`, multi-session Chrome profiles |
| `kicad-bridge` | Launch KiCad 9, open schematics/boards/symbols/footprints, sym-lib-table / fp-lib-table install, DRC, 3D viewer, window-info + per-window screenshots, `kicad_send_key`, `kicad_click` |
| `fusion-bridge` | Launch Fusion 360, open `.f3d` / `.f3z`, import STEP, export STEP / GLB / `.lbr`, read BOM + parameters, run Fusion API commands, Fusion screenshots, symbol library import/export |

See `apps/adom-desktop` on the wiki for the current authoritative list and install prompt.

## 5 — If the binary is present but stale

```bash
adom-desktop release check   # compare local vs wiki version
```

If local is older: re-run the install prompt from the wiki — it replaces the binary and the sibling skills atomically.

## 6 — Why this skill exists

Desktop integration is its own repo (adom-inc/adom-desktop) with its own release cadence. Putting the feature docs here in gallia means every rebuild of adom-desktop would force a gallia release too. This skill is the stable, always-present entry point; the actual docs move with the binary.