/memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether session_start is useful.
$ npx -y skills add AVIDS2/memorix --skill memorix-sessions --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-sessions
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether session_start is useful.
SKILL.md
memorix-sessions.SKILL.mdname: memorix-sessions description: Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether session_start is useful.
Memorix Sessions
`memorix_session_start` is optional. Use it when session semantics help; do not make memory-only work heavier than needed.
Tool Router
| Situation | Prefer | CLI fallback | |---|---|---| | Resume a prior long-running task | `memorix_session_start` | `memorix session start --agent <name>` | | HTTP control plane needs project binding | `memorix_session_start` with `projectRoot` | `memorix session start --projectRoot <absolute-path>` | | Need recent handoff/session summaries | `memorix_session_context` | `memorix session context` | | End a real working session | `memorix_session_end` | `memorix session end --sessionId <id> --summary "<summary>"` | | Need explicit subagent coordination identity | `memorix_session_start` with `joinTeam: true` | `memorix session start --joinTeam --agentType <agent>` |
Decision Rules
- For normal memory search/store, do not require session start.
- In HTTP mode, pass the absolute workspace path as `projectRoot` when available.
- `projectRoot` is a detection anchor; Git identity is the final project identity.
- Do not join coordination state unless the user is using tasks, messages, locks, handoff, or `memorix orchestrate`.
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-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
Open skill