Menu
Load specific context from hmem based on what is needed RIGHT NOW. Use when load_project output is not enough for the current question.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Update flow for hmem. Runs `npm update -g`, syncs skills, applies migrations, verifies hooks, shows the changelog. Use when the user asks to update/upgrade hmem, hmem-mcp, or its-over-9k (any language), or when the startup version-check flags a new release. Runs the npm update itself — don't assume it's already done.
Switch active project mid-session via load_project, then fix any misrouted O-entry exchanges. Use when the user says 'aktiviere/lade Projekt X', 'switch to project Y', or whenever you'd otherwise call load_project mid-session.
View and change hmem memory settings, hooks, sync, and checkpoints. Use on /hmem-config, or when the user asks why context is huge, how to change auto-save, how often checkpoints fire, or how to set up sync.
Merge all session checkpoint summaries into one final O-Entry summary. Run at end of sessions with 2 or more checkpoints.
Curate an .hmem file (your own or foreign) — mark obsolete/irrelevant, fix titles, consolidate duplicates, repair broken links. **Requires the `hmem-curate` MCP server** (skill prompts the user to enable it on entry). Use whenever the user says 'aufräumen', 'memory aufräumen', 'Speicher aufräumen', 'hmem aufräumen', 'clean up memory', 'tidy up hmem', 'curate memory', 'consolidate duplicates', 'merge duplicate entries', 'fix broken links', 'kümmer dich um die Memory', or invokes /hmem-curate. Also trigger when `memory_health()` flags BLOCKER/WARNING issues, when a P-entry's load_project output exceeds 4k tokens (session-start noise check defers to this skill), or before any batch cleanup of L, E, D, P entries. Skipping this skill and editing memory directly bypasses health checks, severity triage, and obsolete-chain integrity — never curate without it.
Dispatch an isolated sub-agent that returns only [RESULT]...[/RESULT]. Use for any search, lookup, 'does X exist?', 'find Y', calculation, or isolated writing — never do these inline when dispatch fits.
| name | hmem-context |
| description | Load specific context from hmem based on what is needed RIGHT NOW. Use when load_project output is not enough for the current question. |
Use when:
Do NOT use for session start — use hmem-session-start instead.
Pick ONE:
For keyword search: search_memory(query: "")
For semantic search: find_related(id: "P00XX", query: "")
For direct node: read_memory(id: "P00XX.2")
Replace P00XX with the active project ID (e.g., P0056).
Select at most 3 nodes that directly answer the question.
[CONTEXT LOADED]
: <body of node 1> --- <title of node 2>: <body of node 2> [/CONTEXT LOADED] If nothing relevant found:[CONTEXT LOADED] No relevant context found for: [/CONTEXT LOADED]
→ If the missing info is code structure: dispatch an Explore agent to locate it in the filesystem. → After finding it, update the Codebase node immediately using the correct depth: L3 — module group (if the group is missing): append_memory(id="P00XX.2", title="Core modules") L4 — individual module with signature + purpose: append_memory(id="P00XX.2.N", title="moduleName.ts", body="functionName(param: Type): Return — purpose. src/path/moduleName.ts") L5 — optional extended notes (edge cases, caveats): append_memory(id="P00XX.2.N.M", title="Note", body="...")
