How do I install the Memory Troubleshoot skill?

Run npx skillmds@latest add spillwavesolutions/memory-troubleshoot in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Memory Troubleshoot safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Memory Troubleshoot?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Memory Troubleshoot free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Memory Troubleshoot?

spillwavesolutions (@spillwavesolutions) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Memory Troubleshoot by spillwavesolutions

Name: Memory Troubleshoot
Author: spillwavesolutions

Memory Troubleshoot

Diagnostic and troubleshooting workflow for agent-memory. Guides users through common install/config/daemon/ingest issues. Requires confirmation before any edits or restarts. Provides verification commands only.

File contents

Memory Troubleshoot Skill

Diagnose and resolve common agent-memory issues safely. This skill never runs verification commands automatically and always asks for confirmation before edits or restarts.

When to Use

Daemon will not start
Commands are not found
Connection refused
No events captured
Summarization failures

Safety Rules

Do not edit files or restart services without confirmation
Provide verification commands only
Keep fixes scoped to the reported issue

Diagnostic Flow

Step 1: Identify the symptom

Which issue are you seeing?

1. "command not found" for memory-daemon or memory-ingest
2. "connection refused" or cannot query daemon
3. Daemon starts then stops
4. No events captured
5. Summarization not working
6. Other / not sure

Enter selection [1-6]:

Step 2: Provide targeted diagnostics (commands only)

1) Command not found

which memory-daemon
which memory-ingest
echo $PATH

2) Connection refused

memory-daemon status
lsof -i :50051
memory-daemon query --endpoint http://[::1]:50051 root

3) Daemon stops immediately

memory-daemon status
tail -50 ~/Library/Logs/memory-daemon/daemon.log
tail -50 ~/.local/state/memory-daemon/daemon.log

4) No events captured

grep -n "memory-ingest" ~/.claude/hooks.yaml
which memory-ingest
memory-daemon status

5) Summarization failing

echo "OPENAI: ${OPENAI_API_KEY:+set}"
echo "ANTHROPIC: ${ANTHROPIC_API_KEY:+set}"

Step 3: Offer safe fixes (with confirmation)

For each fix, ask:

I can apply the following fix:
  [describe the change]

Proceed? (yes/no)

Examples:

PATH update

Add ~/.local/bin to PATH in your shell profile

Restart daemon

Stop and restart the daemon:
  memory-daemon stop
  memory-daemon start

Fix hooks file

Add memory-ingest handler to ~/.claude/hooks.yaml

Step 4: Provide verification commands (optional)

memory-daemon status
memory-daemon query --endpoint http://[::1]:50051 root

Common Fix Playbooks

"command not found"

Ensure binaries are installed
Add install directory to PATH
If missing, re-run memory-install

"connection refused"

Confirm daemon is running
Check port conflicts on 50051
Update grpc_port in config if needed

"no events captured"

Confirm hooks file contains memory-ingest
Confirm memory-ingest is on PATH
Restart the agent session after hook changes

"summarization not working"

Set provider API key
Ensure config provider matches key

Escalation

If diagnostics do not resolve the issue, recommend:

Re-run memory-verify for a full check
Re-run memory-install with a fresh setup

---name: memory-troubleshootdescription: Diagnostic and troubleshooting workflow for agent-memory. Guides users through common install/config/daemon/ingest issues. Requires confirmation before any edits or restarts. Provides verification commands only.license: MIT---# Memory Troubleshoot SkillDiagnose and resolve common agent-memory issues safely. This skill never runsverification commands automatically and always asks for confirmation beforeedits or restarts.## When to Use- Daemon will not start- Commands are not found- Connection refused- No events captured- Summarization failures## Safety Rules- Do not edit files or restart services without confirmation- Provide verification commands only- Keep fixes scoped to the reported issue## Diagnostic Flow### Step 1: Identify the symptom```Which issue are you seeing?1. "command not found" for memory-daemon or memory-ingest2. "connection refused" or cannot query daemon3. Daemon starts then stops4. No events captured5. Summarization not working6. Other / not sureEnter selection [1-6]:```### Step 2: Provide targeted diagnostics (commands only)**1) Command not found**```which memory-daemonwhich memory-ingestecho $PATH```**2) Connection refused**```memory-daemon statuslsof -i :50051memory-daemon query --endpoint http://[::1]:50051 root```**3) Daemon stops immediately**```memory-daemon statustail -50 ~/Library/Logs/memory-daemon/daemon.logtail -50 ~/.local/state/memory-daemon/daemon.log```**4) No events captured**```grep -n "memory-ingest" ~/.claude/hooks.yamlwhich memory-ingestmemory-daemon status```**5) Summarization failing**```echo "OPENAI: ${OPENAI_API_KEY:+set}"echo "ANTHROPIC: ${ANTHROPIC_API_KEY:+set}"```### Step 3: Offer safe fixes (with confirmation)For each fix, ask:```I can apply the following fix: [describe the change]Proceed? (yes/no)```Examples:**PATH update**```Add ~/.local/bin to PATH in your shell profile```**Restart daemon**```Stop and restart the daemon: memory-daemon stop memory-daemon start```**Fix hooks file**```Add memory-ingest handler to ~/.claude/hooks.yaml```### Step 4: Provide verification commands (optional)```memory-daemon statusmemory-daemon query --endpoint http://[::1]:50051 root```## Common Fix Playbooks### "command not found"- Ensure binaries are installed- Add install directory to PATH- If missing, re-run `memory-install`### "connection refused"- Confirm daemon is running- Check port conflicts on 50051- Update `grpc_port` in config if needed### "no events captured"- Confirm hooks file contains `memory-ingest`- Confirm `memory-ingest` is on PATH- Restart the agent session after hook changes### "summarization not working"- Set provider API key- Ensure config provider matches key## EscalationIf diagnostics do not resolve the issue, recommend:- Re-run `memory-verify` for a full check- Re-run `memory-install` with a fresh setup

Frequently asked questions