SCRIPT=$(cat <<'PS' | base64 -w0
$roots = @("C:\Program Files", "C:\Program Files (x86)")
$names = @("Altium", "OrCAD", "Cadence", "EAGLE", "DipTrace", "Eplan")
foreach ($r in $roots) {
  Get-ChildItem $r -Directory -ErrorAction SilentlyContinue |
    Where-Object { $n = $_.Name; $names | Where-Object { $n -like "*$_*" } } |
    ForEach-Object { "INSTALLED: $($_.FullName)" }
}
Get-Process -ErrorAction SilentlyContinue |
  Where-Object { $p = $_.ProcessName; $names | Where-Object { $p -like "*$_*" } } |
  ForEach-Object { "RUNNING: $($_.ProcessName)" } | Select-Object -Unique
PS
)
adom-bridge-cli run_script "{\"interpreter\":\"powershell\",\"scriptB64\":\"$SCRIPT\"}"

---
name: hydrogen-eda-discovery-windows
description: >
  Windows companion to hydrogen-eda-discovery: the ready-to-run probe for detecting
  EDA tools that have NO bridge (Altium, OrCAD, Cadence/Allegro, EAGLE, DipTrace,
  Eplan) on a Windows host via install-path scans and process listing through
  adom-bridge-cli run_script. The generic discovery playbook (branching, the
  community pitch, etiquette) lives in hydrogen-eda-discovery. Trigger words:
  detect altium windows, detect orcad windows, program files scan, eda probe
  windows, no-bridge eda detection, powershell eda probe.
---

# EDA discovery on Windows: the no-bridge probe

The generic playbook is `hydrogen-eda-discovery`. KiCad and Fusion 360 are detected
through their bridge verbs on every platform; this skill is only the Windows probe
for tools with no bridge.

## Install-path + process probe (run from the workspace)

Scan the standard install roots and the process list via a PowerShell `run_script`
(base64 the script so no quoting gets mangled):

```bash
SCRIPT=$(cat <<'PS' | base64 -w0
$roots = @("C:\Program Files", "C:\Program Files (x86)")
$names = @("Altium", "OrCAD", "Cadence", "EAGLE", "DipTrace", "Eplan")
foreach ($r in $roots) {
  Get-ChildItem $r -Directory -ErrorAction SilentlyContinue |
    Where-Object { $n = $_.Name; $names | Where-Object { $n -like "*$_*" } } |
    ForEach-Object { "INSTALLED: $($_.FullName)" }
}
Get-Process -ErrorAction SilentlyContinue |
  Where-Object { $p = $_.ProcessName; $names | Where-Object { $p -like "*$_*" } } |
  ForEach-Object { "RUNNING: $($_.ProcessName)" } | Select-Object -Unique
PS
)
adom-bridge-cli run_script "{\"interpreter\":\"powershell\",\"scriptB64\":\"$SCRIPT\"}"
```

Notes:

- Treat EMPTY output as a timeout or probe failure, not a negative result
  (unknown is not "none"). Say so plainly and ask the user if unsure.
- Some vendors install under the user profile or a custom drive; a miss on
  `Program Files` is evidence, not proof. The RUNNING lines are the stronger
  signal when the user has the tool open.
- `run_script` interpreters on Windows: `bash`, `cmd`, `powershell`.

## Related skills

- `hydrogen-eda-discovery` (base): the full discovery and onboarding playbook
- `hydrogen-adom-desktop-windows`: Windows host specifics for run_script and installs