SKILLEMALL.ai

AB graph-rag-memory

Graph-RAG memory system using Graphiti temporal knowledge graph + FalkorDB + local Ollama embeddings. Provides persistent, queryable long-term memory for OpenClaw agents via a MoE-style (Mixture-of-Experts) multi-embedding router. Use when: setting up persistent agent memory, querying past conversations or facts, ingesting documents into the memory graph, checking memory system status, or integrating graph-rag memory into an OpenClaw agent. Triggers on: "memory system", "graph rag", "graphiti", "persistent memory", "ingest memory", "query memory", "what do you remember", "memory upgrade".

ClawHub Agent Skills author: jebadiahgreenwood v0.1.0 MIT-0 10 files · 2 scripts body ≈ 1 358 tokens Open the sourceclawhub.ai analyzed 4 d ago

As a process B 67/100 · Nearly there — weak spots: result and completion, running it twice, progress reporting

IntegrationAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
86
Run on models
none yet
Process rating
B
67/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 67/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 3 mutating operations with no state check
    • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 11 steps
    • 100Failures and branches. 1 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1358 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -4Absolute local paths (C:\Users, /home/…): not portable
    • -32 of 5 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 8 example trigger phrases
    • +3Description length 595: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 11 items
    • +4Has examples (10 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.

    External checks

    ClawHub: suspicious
    This appears to be a real local memory tool, but it persistently ingests workspace data, changes OpenClaw behavior, and starts background refresh code with weak consent and review boundaries.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026