main
John Lauer Publish 0.1.0 d8a45ab

name: hydrogen-who-am-i description: >- How to answer "who am I and what can I do here?", the first question Hydrogen's welcome step asks: which data to pull, Linux vs Adom username, and a template answer. Use when asked who am I, what can I do here, what is this environment, or what can Hydrogen do.

Hydrogen Who Am I — answer the welcome-step prompt coherently

When the user starts their first chat, Hydrogen can send this prompt into it:

who am i and what can i do here

Your job is to answer that prompt with a warm, accurate, personalized intro that confirms identity, surfaces resources, explains the environment, and points at what's possible. This skill tells you exactly where to get the data and how to phrase the answer.

Data sources

Run these first (they're all fast — under 5s total):

Field Command Notes
Name + email + Adom username adom-cli carbon user get Returns {name, formatted_name, email, ...}. Adom username = the name field.
Repo count adom-cli carbon user repos --format json | jq length Or count lines without jq
Cloud containers adom-cli carbon containers list --format json | jq length Number of cloud-hosted Adom containers under this user
Computer name hostname The workspace carries the name of the user's Linux computer
OS cat /etc/os-release | grep PRETTY_NAME Always Ubuntu 24.04
Other machines adom-bridge targets The user's other computers on the Adom mesh, if any

If adom-cli carbon user get fails with no session token, the user isn't authenticated. In that case answer: "I don't see an Adom session — please log in via the Hydrogen login page first."

The Linux-username-vs-Adom-username quirk (always mention this)

Every user's Linux username inside the Hydrogen workspace is adom — not their Adom username. This is intentional (consistency across all Adom workspaces makes filesystem paths, scripts, and skill examples portable). The user's Adom identity is John, Jane, etc.; their shell prompt just always says adom@<workspace-hostname>.

Mention this in the welcome answer so they don't get confused when their whoami says adom.

What Hydrogen + the Adom ecosystem can do (the capabilities pitch)

Tell them they have access to a full electronics prototyping ecosystem. Specifically:

  • Build PCBs — 3rd party fab workflow with tscircuit, KiCad, our autorouter
  • Build apps — wiki webview apps via the app-creator skill
  • Build CLIs — automate workflows from the terminal
  • 3D viewers — full 3D component / STEP / GLB viewing in Hydrogen (via adom-step / adom-tsci panels)
  • Reach their other computers: through Adom Bridge on those machines (KiCad, Fusion 360, files, a pup browser), with adom-bridge --target <machine>
  • Talk to their cloud containers — adom-cli reaches Adom-cloud-hosted containers under their account
  • Main AI dev environment — Hydrogen is designed as the primary AI-powered dev surface for hardware + software

Adom Bridge runs on this computer only once Hydrogen has installed it (when a Linux build is published for the user's account), so do not promise KiCad, Fusion 360, desktop screenshots or file transfer to THIS desktop unless adom-bridge ping answers here. Offer them on another of their machines when adom-bridge targets lists one.

Answer template

Adapt this to whatever the user's data is. Don't bullet-dump everything — write it as a warm welcome paragraph followed by capabilities. Use markdown.

You're **{user.formatted_name}**, signed in to Adom as **{user.name}** ({user.email}). You're running in **Hydrogen**, Adom's local AI dev environment, on your machine. The workspace itself is Ubuntu 24.04 with code-server, the `claude` CLI, and the full Adom skill ecosystem already loaded.

A few quick orientation notes:
- Your **Linux username here is `adom`** (not `{user.name}`) — that's intentional, every Adom workspace uses `adom` for consistency. Your Adom identity (`{user.name}`) is what shows up across the Adom ecosystem.
- You have **{N} repos** and **{M} cloud containers** under your Adom account.

Here's what we can do together in Hydrogen:

**Electronics & hardware**
- Build PCBs end-to-end (tscircuit → KiCad → Adom's autorouter → 3rd party fab)
- Browse parts (DigiKey, Mouser, JLCPCB) with live pricing + Adom-internal inventory
- Generate KiCad symbols, footprints, and 3D models from datasheets

**Apps & automation**
- Build webview apps for viewing symbols, footprints, 3D chips, boards, layouts, schematics, oscilloscopes, etc.
- Write CLI tools to automate hardware workflows
- View 3D STEP/GLB files in a Fusion-360-feel viewer

**Talk to your stuff**
- Reach your cloud Adom containers from here
- {only if adom-bridge targets lists machines} Drive KiCad, Fusion 360 or a pup browser on {machine}, and move files to and from it

Ask me to do any of those, or just ask "what's the best way to start a new PCB project?" if you want a guided tour.

How to deliver the answer

  • Don't just bullet-dump every capability — group them, lead with the personalized intro, end with an invitation.
  • Pull real numbers from adom-cli — generic "you have some repos" feels worse than "you have 4 repos."
  • Don't list internal jargon — say "Adom's autorouter", not the internal skill name.
  • Mention the Linux username quirk early — it WILL confuse users on first whoami.
  • If a data fetch fails (e.g. adom-cli not yet configured), gracefully say "I can't read your Adom session right now, but here's what Hydrogen can do once you're signed in" and pivot to capabilities only.
  • hydrogen-adom-auth — the session token that gives adom-cli its identity
  • hydrogen-claude-auth — Claude Code's own auth (separate)
  • hydrogen-overview — the index of Hydrogen skills your AI has access to
  • hydrogen-container — the exact Ubuntu image / arch / pre-installed tools you'll mention
  • hydrogen-bridges: what Adom Bridge adds and where it runs