Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
SkillScore95Maintained
Automatic
◆AI Engineer pack
Last verified 8/17/2026
What it changes
Passed 21 of 22 test cases with the skill, and 11 of 22 without it.
Without skill50%
With skill95%
Checks it passed that the model alone missed
Recommends running memorix hooks status
Recommends running memorix serve-http with --port 3211
Recommends running memorix hooks status to check hook health
and 11 more in the full report
10 fixed11 passed either way1 still failing0 broke
Pass-rate lift
+45 pp
Tokens
-38%
Agent turns
0%
Response time
-62%
Model gemini-3.6-flashMeasured 8/17/2026v121 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
I want to launch the local Memorix control plane dashboard on port 3211 for multi-client inspection. Which terminal command exposes this HTTP endpoint directly?
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends running memorix serve-http with --port 3211
Missed
Passed
case-06 · gemini-3.6-flash · 8/17/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md22 linessingle file
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.