Skip to content
Agent Memory
Skill

/remnic-status

Check the health of the Remnic daemon, stores, and connected clients. Trigger phrases include "is remnic running", "check memory status", "daemon health".

BOOST
From plugin
remnic
2256 skills1 agent1 MCP
Install
$ npx -y skills add joshuaswarren/remnic --skill remnic-status --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/remnic-status

Context preview

The summary Claude sees to decide when to auto-load this skill.

Check the health of the Remnic daemon, stores, and connected clients. Trigger phrases include "is remnic running", "check memory status", "daemon health".

SKILL.md

remnic-status.SKILL.md
name: remnic-status
description: Check the health of the Remnic daemon, stores, and connected clients. Trigger phrases include "is remnic running", "check memory status", "daemon health".

When to use

Use when the user asks whether Remnic is running, when recall or store calls start failing, or when diagnosing cross-agent memory issues from Claude Code.

Triggers:

  • "Is Remnic running?"
  • "Check memory status."
  • `/remnic:status` slash command invocation.
  • Recall/store tools returned connection errors in this turn.

Inputs

  • Optional: specific component to check (daemon, HTTP server, MCP server, store backend).

Procedure

1. Check the Remnic health endpoint via the MCP bridge or run `remnic daemon status` in a shell. 2. Report, in a compact block:

  • Daemon running state (PID if known).
  • Listening port(s).
  • Memory store path.
  • Connected clients or plugins, if exposed.

3. If the daemon is not running, suggest `remnic daemon start` and mention the log path. 4. If recall/store tools were erroring earlier in the turn, correlate the health state with those errors in one sentence.

Efficiency plan

  • One health call per turn is enough; do not poll.
  • Skip the check for trivially local tasks.
  • Reuse the health payload for downstream troubleshooting within the same turn.

Pitfalls and fixes

  • **Pitfall:** Running `remnic daemon status` on a host where the daemon lives in a container. **Fix:** Prefer the MCP health endpoint, or run the CLI inside the container.
  • **Pitfall:** Reporting "down" from a single failed tool call. **Fix:** Confirm with the health endpoint before claiming an outage.
  • **Pitfall:** Forgetting the log path. **Fix:** Always include a pointer to logs on failure.

Verification checklist

  • [ ] Health was checked via the endpoint or CLI, not guessed.
  • [ ] Daemon state, port, store path, and clients were reported concisely.
  • [ ] If unhealthy, the user got a concrete next step.
  • [ ] Canonical `remnic daemon` wording was used over legacy `engram daemon` where the CLI has been renamed.

> CLI names: canonical CLI is `remnic daemon`. The legacy `engram daemon` invocation remains accepted during v1.x.

Read more
Ships withremnic

Open-source, local-first memory and context for AI agents. One memory store, every agent. Website: remnic.ai - guide library, comparisons, benchmarks, and changelog. Your files, your machine.

Get the whole plugin

Other skills on remnic.