/memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
$ npx -y skills add AVIDS2/memorix --skill memorix-troubleshooting --agent claude-codeHow 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
/memorix-troubleshooting
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
SKILL.md
memorix-troubleshooting.SKILL.mdname: memorix-troubleshooting
description: Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
Memorix Troubleshooting
Prefer direct CLI diagnostics first. MCP is an integration surface, not the only way to operate Memorix.
Diagnostic Router
| Symptom | Check | CLI fallback | |---|---|---| | MCP tools missing | host MCP config and restart | `memorix setup --agent <agent>` | | Unsure project is bound | project status | `memorix status` and `git status` | | HTTP MCP stale or unbound | background health and explicit session bind | `memorix background status`; then `memorix session start --projectRoot <path>` | | Hooks not firing | hook status | `memorix hooks status` | | Need to inspect generated files | preview | `memorix hooks preview --agent <agent>` | | Setup looks incomplete | reinstall host integration | `memorix setup --agent <agent>` | | Need dashboard/control plane | background service | `memorix background start` or `memorix serve-http --port 3211` |
Mode Rules
- Use stdio MCP (`memorix serve`) for normal host-launched MCP integration.
- Use HTTP/background only for shared endpoint, dashboard, Docker, multiple clients, or foreground control-plane debugging.
- On Windows, prefer absolute native paths for `projectRoot` and remember that visually similar junction paths may bind different session histories.
- If MCP is unavailable but the CLI works, continue through CLI commands instead of blocking.
Read more
name: memorix-troubleshooting description: Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
Memorix Troubleshooting
Prefer direct CLI diagnostics first. MCP is an integration surface, not the only way to operate Memorix.
Diagnostic Router
| Symptom | Check | CLI fallback | |---|---|---| | MCP tools missing | host MCP config and restart | `memorix setup --agent <agent>` | | Unsure project is bound | project status | `memorix status` and `git status` | | HTTP MCP stale or unbound | background health and explicit session bind | `memorix background status`; then `memorix session start --projectRoot <path>` | | Hooks not firing | hook status | `memorix hooks status` | | Need to inspect generated files | preview | `memorix hooks preview --agent <agent>` | | Setup looks incomplete | reinstall host integration | `memorix setup --agent <agent>` | | Need dashboard/control plane | background service | `memorix background start` or `memorix serve-http --port 3211` |
Mode Rules
- Use stdio MCP (`memorix serve`) for normal host-launched MCP integration.
- Use HTTP/background only for shared endpoint, dashboard, Docker, multiple clients, or foreground control-plane debugging.
- On Windows, prefer absolute native paths for `projectRoot` and remember that visually similar junction paths may bind different session histories.
- If MCP is unavailable but the CLI works, continue through CLI commands instead of blocking.
Open-source cross-agent memory layer for coding agents via MCP. Compatible with Claude Code, Codex, Cursor, Windsurf, Gemini CLI, Antigravity, OpenClaw, Hermes Agent, Oh-my-Pi, Pi, Copilot, Kiro, OpenCode, and Trae.
Repo: AVIDS2/memorix
Other skills on memorix.
- /memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
Open skill - /memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
Open skill - /memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
Open skill - /memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
Open skill - /memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
Open skill - /memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether session_start is useful.
Open skill