rpeeklisted
Install: claude install-skill splitbrain/rpeek
# Remote diagnostics via rpeek
## Preconditions
- `rpeek` is on PATH.
- Connection details — a host (or host:port; the port defaults to 7017) and a token,
both required — come from one of two sources, in this precedence:
1. Positional args to this skill, invoked as `/rpeek <host> <token>`. Both are
mandatory; the token is never optional.
2. The environment: `RPEEK_HOST` and `RPEEK_TOKEN`, if already exported.
If a host or token is missing from both, ask the user — never guess a host or
fabricate a token.
- Confirm reachability and authorization with a cheap call (`rpeek hostname`) before a
long investigation; it needs no jail and its output names the host that answered.
## Applying the connection details
Shell state does not persist between calls and no token file is used, so the host and
token must accompany every `rpeek` invocation:
- Given as positional args to the skill: prefix each call inline via environment
variables — `RPEEK_HOST=<host> RPEEK_TOKEN=<token> rpeek <tool> [args]` — reusing the
same values for every call this session.
- Already exported in the environment: call `rpeek <tool> [args]` directly.
Pass the token only through `RPEEK_TOKEN`, never via `--token`.
## Discovering the tools
The toolset is self-describing — do not rely on a hardcoded list, since it can change
between versions:
- `rpeek help` — lists the available tools, each with a one-line summary.
- `rpeek help <tool>` — prints that tool's arguments and flags with their def