kerpopule/hermes-jev-skills: first run, 2026-10-11

Installed from its README in a throwaway sandbox by Claude Code (Claude Opus 5.5), with a Jev API key in the environment and nothing else: no GPU, no desktop, no other paid keys, no accounts. The README's first example was run once. Repo commit b22a21f36572; 39 seconds. All results · Task

Quick start: ran. Jev calls made: 1.

Install	`python3 ~/src/install.py (repo already cloned at ~/src; README: git clone ... && python3 install.py)`
Quick start, as run	jev setup-key (skipped: key already in env as TYPESAFE_API_KEY, which jevkit reads first) then `jev doctor`, the README's 'Try it in two commands'
What came back	jev doctor -> {"version": "0.23.0", "key": {"present": true, "provider": "typesafe", "source": "environment"}, "jev": {"reachable": true, "latency_ms": 336}, "routing": {"privacy_mode": "redacted-text", "tiers_configured": []}, "hermes_home": null}. doctor sends one real Jev yes/no question ('The build finished and all tests passed.' -> ok?) and it answered.
What stopped it	Nothing.

Steps the README does not mention

Added ~/.local/bin to PATH: the installer put `jev` at ~/.local/bin/jev, which was not on PATH (the installer's own output warns about this and suggests the fix, but the README does not mention it)
Skipped `jev setup-key`: it opens a browser page (or needs --tty for an interactive hidden prompt); relied instead on TYPESAFE_API_KEY already in the environment, which the code (jevkit/keystore.py) checks first but the README's quick start does not say is an option
Note: the default install also edits ~/.claude/CLAUDE.md (backed up) and adds ~/.claude/agents and ~/.claude/skills entries because Claude Code was detected; the README does say this

The session's closing message

The install and quick start both worked, and the quick start got a real answer back from Jev. I made one Jev call in total.

- **Install:** I ran `python3 install.py` from `~/src`, as the README says. It installed the `jev` command, the 11 skills and the 4 lane subagents. It also added a lanes block to `~/.claude/CLAUDE.md` after backing the file up; the README does say it will do that.
- **Quick start:** The README's "Try it in two commands" ends with `jev doctor`. That command sends Jev one real yes/no question, and it came back `reachable: true` with a latency of 336 ms. The key showed as `present` with `source: environment`.

Two steps the README doesn't mention:
- **`jev` was not on PATH.** The installer puts it at `~/.local/bin/jev`, and that folder wasn't on PATH on this machine. The installer's own output warns about this and gives the fix, but the README doesn't. I added the folder to PATH for the session.
- **I skipped `jev setup-key`.** It wants you to paste the key into a page in a browser, or to type it at a hidden prompt with `--tty`. The project's code reads the key from `TYPESAFE_API_KEY` first, and that's the name it already had here, so nothing needed exporting. The README's quick start doesn't say an environment variable is an option.

Nothing blocked the run, and I didn't patch any code. The key was never printed or written anywhere.

DELIVERABLE: ~/work/output/report.json