Bumblebiber/o9k-recall
skills/o9k-recall/SKILL.md
Dispatch a Haiku sub-agent to search hmem for relevant memories. Sub-agent returns matching entries as ID + one-line summary. Main agent context stays clean.
$ install --global
skillsauthnpx skillsauth add Bumblebiber/hmem o9k-recallInstall 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 12, 2026, 4:23 AM124.3s1 file scanned
SKILL.md
- name:
- o9k-recall
- description:
- Dispatch a Haiku sub-agent to search hmem for relevant memories. Sub-agent returns matching entries as ID + one-line summary. Main agent context stays clean.
o9k-recall
TRIGGER
Use when:
- You need to find past decisions, lessons, or session context from hmem
- You don't know the exact node ID
- You want to keep the search work out of the main context
STEP 1: Define the search query
Before dispatching, write down:
- QUERY: what to search for (keywords, concept, or question)
- TYPE: what kind of memory (L-Entry = lesson, O-Entry = session, P-Entry = project, any)
STEP 2: Dispatch Haiku sub-agent
Send the sub-agent exactly this prompt (fill in QUERY and TYPE):
Search hmem for: <QUERY> Memory type filter: <TYPE or "any">
Use these tools in order:
- search_memory(query: "<QUERY>") — keyword search
- find_related(id: "<active P-Entry ID>", query: "<QUERY>") — semantic search
Collect all results. Deduplicate by ID.
Return ONLY this format:
[RECALL RESULTS] <ID> | <one-line summary of what this entry contains> <ID> | <one-line summary> ... [/RECALL RESULTS]
If nothing found: [RECALL RESULTS] none [/RECALL RESULTS]
Max 10 results. Most relevant first. IDs exact (e.g., L0042, O0056.3.2, P0048.6). Nothing before [RECALL RESULTS]. Nothing after [/RECALL RESULTS]. No commentary, no explanation.
STEP 3: Use results
The main agent receives the [RECALL RESULTS] block. To read a specific entry in full: call read_memory(id: "<ID from results>") To load a project: call load_project(id: "<P-Entry ID from results>")
Do NOT load all results at once — pick only what the current question needs.
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