Bumblebiber/hmem-context
skills/hmem-context/SKILL.md
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 --global
skillsauthnpx skillsauth add Bumblebiber/hmem hmem-contextInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 8, 2026, 4:08 AM163.0s1 file scanned
SKILL.md
- 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.
hmem-context
TRIGGER
Use when:
- The current question requires a past decision not in the project brief
- You need to recall a specific bug, pattern, or lesson
- You need code details not in the Overview
Do NOT use for session start — use hmem-session-start instead.
STEP 1: Identify what type of information is needed
Pick ONE:
- Past decision → use search_memory with keywords from that decision
- Lesson or pattern → use find_related on the concept
- Code details → use read_memory on P00XX.2 (Codebase section)
STEP 2: Run the search (pick ONE)
For keyword search: search_memory(query: "<specific keywords>")
For semantic search: find_related(id: "P00XX", query: "<concept>")
For direct node: read_memory(id: "P00XX.2")
Replace P00XX with the active project ID (e.g., P0056).
STEP 3: Filter results
Select at most 3 nodes that directly answer the question.
- Prefer L-Entries over O-Entries (more compact, already distilled)
- Prefer entries with matching keywords in title
- Discard everything else
STEP 4: Output
[CONTEXT LOADED]
<title of node 1>: <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: <your query> [/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="...")
Related Skills
Bumblebiber/o9k-update
tools
VerifiedTrustedCommunity
Update flow for its-over-9k (hmem). Runs `npm update -g`, syncs skills, applies migrations, verifies hooks, shows the changelog. Use when the user asks to update/upgrade hmem, o9k, o9k-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.
19SKILL.mdUpdated May 12, 2026
Bumblebiber/o9k-session-start
development
VerifiedTrustedCommunity
Mandatory entry point for every Cortex session — invoke at conversation start, after /clear, and after any load_project call. All stable context (H-entries, projects, device, sync) is pre-injected by the hook — no read_memory(mode='essentials') needed. Surfaces pending git work, Next Steps + open T-tasks, and runs the O-entry routing check.
19SKILL.mdUpdated May 12, 2026
Bumblebiber/o9k-curate
tools
VerifiedTrustedCommunity
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 /o9k-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.
19SKILL.mdUpdated May 12, 2026
Bumblebiber/o9k-new-rule
testing
VerifiedTrustedCommunity
Add a new rule and place it correctly — decide between a cross-project R-entry and a project-specific subnode under the active project's Rules section. Use whenever the user says 'neue Regel', 'Regel hinzufügen', 'new rule', 'add a rule', or invokes /o9k-new-rule. Critical safeguard: project-specific rules placed as R-entries pollute the session-start Rules listing across every project — get the scope right BEFORE writing.
18SKILL.mdUpdated May 21, 2026