Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →minpeter/hermes-agent-consult
Consult the local `hermes` agent as the long-term-memory oracle for minpeter's machines, from inside another coding agent (pi, codex, senpi, Kiro, Claude Code).
Passed 16 of 20 test cases with the skill, and 5 of 20 without it.
and 18 more in the full report
12 fixed6 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We just updated our Kubernetes service manifest in git. Formulate the shell command to pass our uncommitted git diff to the agent CLI for an operational review, ensuring the output is brief and restricted to 3 points maximum.
| Checked | Without skill | With skill |
|---|---|---|
| Passes `$(git diff)` inside the prompt argument to `hermes -z`. | Missed | Passed |
| Instructs the agent in the prompt string to limit output to 3 bullets maximum. | Passed | Passed |
The instructions your model reads when the skill loads.
hermes is minpeter's long-running personal agent. It holds persistent memory
about the machines, homelab, networking, and past decisions that a fresh coding
agent in a single repo cannot see. Treat it as a peer to consult, not a tool to
run: it is the cheapest source of the context you are missing, and it is the
place that context has to be stored so the next agent finds it.
Verify it is available before relying on it: command -v hermes. If it is
missing, fall back to asking the user and say why.
| Move | When | Command |
|---|---|---|
| Consult | You need context the repo does not contain, and you were about to ask the user | hermes -z "<question>" |
| Teach | You changed infra, or learned something with a long shelf life | hermes -t memory -z "Remember: <fact>" |
| Review | Non-trivial diff, plan, or ops procedure before you hand it over | hermes -z "Review this: … <diff>" |
-z is one-shot: it prints only the final response text to stdout, no banner,
no spinner, no session id. It is built for exactly this kind of scripted use.
The prompt must immediately follow -z. hermes -t memory -z "…" and
hermes -z "…" -t memory both work; hermes -z -t memory "…" is an argparse
error, because -t gets consumed as the prompt. Putting -z last is the habit
that never breaks.
The rule: when you are about to ask the user a question about their environment, history, or preferences, ask hermes first. The user is the slow, expensive path; hermes answers in ~10s and often already knows.
Consult for:
test cases passed, vs 5 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.