← Commit history

Publish 1.2.0

John Lauer ·0a43e993d8 ·2mo ago ·parent e6a64af
3 files changed +87−7
SKILL.md+43−6
@@ -57,7 +57,21 @@ their own computer.  ## Step 0: figure out which kind of user you have -Run `adom-bridge-cli targets` (in the container).+**First, work out WHERE you are running**, because the Adom Bridge story is+completely different in each case:++```bash+echo "$VSCODE_PROXY_URI"+```++- Contains **`.adom.cloud`** → the user is on **Hydrogen Cloud (hc)**: their+  container is in the cloud, their laptop is somewhere else. Bridge is a+  SEPARATE install on their laptop, and without it there is no pup at all.+  Most hc users have never installed it. See the hc path below.+- Anything else (localhost / WSL2) → the user is in the **Hydrogen desktop+  app (ah)**, where Bridge ships with the app and usually just works.++Then run `adom-bridge-cli targets` (in the container).  - **CLI missing or no bridge connected → NEWBIE PATH (below).** Do not skip   them to manual voting; the whole point is they experience Hydrogen + ab + pup.@@ -73,11 +87,34 @@ Tell the user what's about to happen in one friendly sentence: "I'll help you install Adom Bridge so I can drive a browser on your laptop and cast your vote for you; you'll watch it happen." -1. Have them open `https://wiki.adom.inc/adom/adom-bridge` on the laptop they-   are physically using, download the installer for their OS from the page, and-   run it. (They must do this one step by hand; you cannot install onto a-   machine you can't reach yet.)-2. Wait, then poll `adom-bridge-cli targets` until their machine appears.+### If they are on Hydrogen Cloud (hc) — the common case for this campaign++Their cloud container cannot reach their laptop until Bridge is running ON+that laptop. Be encouraging: this is a 2-minute install and it is what turns+their cloud AI into something with hands on their real machine.++1. Have them open `https://wiki.adom.inc/adom/adom-bridge` **on the laptop+   they are physically sitting at**, download the installer for their OS, and+   run it. (This one step must be done by hand: you cannot install onto a+   machine you cannot reach yet.)+2. Bridge signs in with their Adom account and connects to the relay, which+   is what lets THIS container drive it. Poll `adom-bridge-cli targets`+   until their machine appears by name.+3. Also mention the other option, without being pushy: the **Hydrogen+   desktop app** (`https://wiki.adom.inc/adom/hydrogen`) bundles Bridge, so+   if they'd rather have the full local experience, installing Hydrogen+   gets them both at once. Either path is a perfectly good outcome for this+   campaign; we want more people on Hydrogen, but an hc user with Bridge is+   a complete setup.++### If they are in the Hydrogen desktop app (ah)++Bridge installs with Hydrogen and runs in embedded mode, so it should+already be connected. If `targets` is empty, do not send them to the+installer: it is almost always a not-running / needs-a-nudge situation.+Point them at the Adom menu → **Doctor...** (or `GET /doctor` on the control+API), which scans the whole stack and offers a one-click fix, then re-check+`targets`. 3. pup normally ships with Bridge. Probe with `pup_status {}`; if you get    `unknown_verb` or a bridge-not-installed error, follow the `_hint` in that    response (ab responses are self-teaching; typically `bridge_list` +
package.json+1−1
@@ -1,7 +1,7 @@ {   "name": "sxsw-vote",   "slug": "sxsw-vote",-  "version": "1.1.0",+  "version": "1.2.0",   "type": "skill",   "dependencies": {},   "scripts": {
page.json+43
@@ -11,5 +11,48 @@   "hero": {     "type": "image",     "path": "docs/hero.png"+  },+  "name": "sxsw-vote",+  "slug": "sxsw-vote",+  "version": "1.2.0",+  "type": "skill",+  "dependencies": {},+  "scripts": {+    "install": "./install.sh",+    "uninstall": "./uninstall.sh"+  },+  "description": "Your AI casts your SXSW PanelPicker vote for the Adom panel and teaches you the stack on the way: Hydrogen + Adom Bridge, pup driving a real browser and saving your login to the credential vault, adom-google reading your confirmation email, and an automated 'voted' post to the team Chat space. Deadline Aug 23, 2026.",+  "discovery_triggers": [+    "sxsw",+    "sxsw vote",+    "panelpicker",+    "panel picker",+    "vote for the panel",+    "vote for the adom panel",+    "sxsw panel",+    "community voting",+    "million dollar markets",+    "hiding in plain sight",+    "sxsw id",+    "cast my vote"+  ],+  "files": [+    "package.json",+    "README.md",+    "SKILL.md",+    "install.sh",+    "uninstall.sh"+  ],+  "discovery_pitch": "Cast your one SXSW PanelPicker community vote for the Adom panel, fully automated by your AI (deadline Aug 23, 2026).",+  "sample_prompts": [+    {+      "label": "Cast my vote",+      "prompt": "Install and follow the skill at https://wiki.adom.inc/adom/sxsw-vote, then cast my SXSW PanelPicker vote for the Adom panel \"The Million-Dollar Markets Hiding in Plain Sight\". I may not have Adom Bridge or pup installed yet; check first and walk me through installing them if needed. Use my real name and my @adom.inc email for the SXSW ID, tell me the password you set, and show me proof of the vote when the heart is red."+    }+  ],+  "org": "adom",+  "author": {+    "name": "John Lauer",+    "email": "[email protected]"   } }\ No newline at end of file