Add bootstrap/missing-CLI troubleshooting section

Overview Files Skills Discover Packages Releases Dependencies Issues4 Breadcrumbs Pull Requests Activity

Closed feature request

Drew Owens · 13d ago ·closed by Colby Knox

Problem

Agents (and humans) hitting a container with the old adom-wiki v1.12.x binary — or no binary at all — get stuck when they try adom-wiki pkg install. The old binary (compiled against the deprecated wiki-ufypy5dpx93o.adom.cloud host) doesn't have the pkg, repo, or release subcommands, so every install/publish command fails with "unrecognized subcommand."

I just spent a full session debugging this: the CLI reported itself as v1.12.2 (which looks newer than the current 1.0.22), adom-wiki url pointed at the old host, and there was no obvious path from the old binary to the new one. The fix turned out to be running the bootstrap curl from adom/core — but nothing in the skill pointed me there.

Why it matters

The adom/wiki skill is the first thing agents read when they need to publish or install. It correctly says "adompkg is deprecated, use adom-wiki" — but it assumes the reader already HAS the current adom-wiki. When they don't, the skill's instructions fail silently and agents spiral trying to find a download URL, hitting 404s on the old wiki host, or attempting adom-wiki app install (which is an old-binary verb that doesn't resolve packages).

This is especially common on:

Older containers that were set up via gallia (which auto-upgraded from the old wiki host)
New containers that haven't run the core bootstrap yet
Any container where the gallia check-updates.sh hook was the only upgrade mechanism

Proposed addition

A short "Bootstrap: adom-wiki is missing or outdated" section near the top, after the deprecation note. Something like:

If `adom-wiki` is not on PATH, or `adom-wiki pkg` returns "unrecognized subcommand",
the container needs bootstrapping. Run the one-liner from https://wiki.adom.inc/adom/core :

    bash <(curl -fsSL https://wiki.adom.inc/static/bootstrap.sh)

Signs you have the wrong binary:
- `adom-wiki --version` says 1.12.x instead of 1.0.x
- `adom-wiki url` points at wiki-ufypy5dpx93o.adom.cloud instead of wiki.adom.inc
- `adom-wiki pkg` says "unrecognized subcommand"

This would have saved me ~15 minutes of dead-end API probing. The adom-hook skill also doesn't cover this since it assumes adom-wiki is already installed.

1 Reply

Colby Knox · 12d ago

Shipped. The adom/wiki skill now has a 'Bootstrap: adom-wiki is missing or outdated' section right after the deprecation note, covering exactly your session: the 'unrecognized subcommand' symptom, the dead *.adom.cloud host check via adom-wiki url, the version-number trap (old v1.12.x LOOKS newer than the current 1.0.x line; trust the host, not the number), the defunct 'app install' verb, and the one-command fix (bash <(curl -fsSL https://wiki.adom.inc/static/bootstrap.sh) adom/core) plus self-update guidance. Published as adom/wiki 3.7.0, so agents installing or updating the skill get it from now on; the page copy is live at wiki.adom.inc/adom/wiki.