fidelis-memorylisted
Install: claude install-skill hermes-labs-ai/fidelis
# fidelis memory workflow
This skill is the procedure for using the `fidelis` MCP tools that ship with
this plugin. It does not describe how fidelis is built; see
<https://github.com/hermes-labs-ai/fidelis> for that.
The retrieval path is zero-LLM by default: the server returns stored passages
verbatim and never regenerates them. Treat what comes back as a quotation, not
as a paraphrase you may polish.
## Before you start
Call `fidelis_health` once per session. It is the only cheap way to tell the
three failure modes apart:
| Result | Meaning | What to do |
|---|---|---|
| `status: ok \| memories: N` with N > 0 | Store is live and populated | Proceed |
| `status: ok \| memories: 0` | Server is up, store is empty | Say so; do not present an empty recall as "nothing was decided" |
| `fidelis-server unreachable at …` | No server on the configured port | Stop using these tools and tell the user to run `fidelis init` (or `fidelis server`) |
An unreachable server is not an empty memory. Never report the two the same way.
## Recall before answering
When the turn leans on something outside the transcript, retrieve first.
1. `fidelis_orient` — the default for a conversational turn. Pass the user's
utterance verbatim as `utterance`, plus up to four `recent_turns` when the
referent is a pronoun ("that project", "the thing we changed"). It returns
an evidence-bound orientation packet or explicitly abstains. **An abstention
is an answer**: it means the store has nothi