DB ourmem
Shared memory that never forgets. Cloud hosted or self-deployed. Collective intelligence for AI agents with Space-based sharing across agents and teams. Use when users say: - "install ourmem" / "install omem" - "setup memory" / "setup omem" - "add memory plugin" - "ourmem onboarding" / "omem onboarding" - "memory not working" - "remember this" - "save this for later" - "don't forget" - "recall preferences" - "what did I say last time" - "import memories" - "share memories" - "share with user" - "share memories to someone" - "team memory" - "shared space" - "persistent memory" - "cross-session memory" - "collective intelligence" - "memory analytics" - "memory stats" - "self-host memory" - "deploy memory server" Even if the user doesn't say "ourmem" or "omem", trigger when they want persistent memory, memory sharing between agents, memory analytics, or memory import/export.
Shared memory that never forgets.
As a process B 67/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 16
✓ No critical or high findings
Medium and low: 16
-
medium Exfiltration
net-credential-usereferences/api-quick-ref.md:33Credential used in a network call (verify the destination is the intended service)curl -s "$API_URL/v1/memories/search?q=dark+mode&limit=5" -H "X-API-Key: $KEY"
-
medium Exfiltration
net-credential-usereferences/api-quick-ref.md:36Credential used in a network call (verify the destination is the intended service)curl -s "$API_URL/v1/memories/search?q=architecture&space=all" -H "X-API-Key: $KEY"
-
medium Exfiltration
net-credential-usereferences/api-quick-ref.md:39Credential used in a network call (verify the destination is the intended service)curl -s "$API_URL/v1/memories?category=preferences&tier=core&limit=20" -H "X-API-Key: $KEY"
-
medium Exfiltration
net-credential-usereferences/api-quick-ref.md:42Credential used in a network call (verify the destination is the intended service)curl -s $API_URL/v1/memories/MEMORY_ID -H "X-API-Key: $KEY"
-
medium Exfiltration
net-credential-usereferences/api-quick-ref.md:50Credential used in a network call (verify the destination is the intended service)curl -sX DELETE $API_URL/v1/memories/MEMORY_ID -H "X-API-Key: $KEY"
-
medium Exfiltration
net-credential-usescripts/verify.sh:56Credential used in a network call (verify the destination is the intended service)AUTH=$(curl -sf -H "X-API-Key: $API_KEY" "$API_URL/v1/memories?limit=1" 2>/dev/null && echo "OK" || echo "FAIL")
-
medium Exfiltration
net-credential-useSKILL.md:238Credential used in a network call (verify the destination is the intended service)curl -sf -H "X-API-Key: $API_KEY" "$API_URL/v1/memories?limit=1" \
-
medium Exfiltration
net-credential-useSKILL.md:343Credential used in a network call (verify the destination is the intended service)curl -sf -H "X-API-Key: $API_KEY" "$API_URL/v1/memories?limit=1" && echo "Auth OK"
-
medium Exfiltration
net-credential-useSKILL.md:516Credential used in a network call (verify the destination is the intended service)curl -sX POST "$API_URL/v1/imports" -H "X-API-Key: $API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:525Credential used in a network call (verify the destination is the intended service)curl -sX POST "$API_URL/v1/imports/cross-reconcile" -H "X-API-Key: $API_KEY"
-
low Exfiltration
read-dotenvreferences/selfhost-setup.md:38Reads a .env filecp .env.example .env
-
low Exfiltration
net-credential-useSKILL-web.md:492Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -sf -H "X-API-Key: $API_KEY" "https://api.ourmem.ai/v1/memories?limit=1" && echo "Auth OK"
vendor-host -
low Exfiltration
net-credential-useSKILL-web.md:606Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -s https://api.ourmem.ai/v1/spaces -H "X-API-Key: $API_KEY"
vendor-host -
low Exfiltration
net-credential-useSKILL-web.md:757Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -sX POST "https://api.ourmem.ai/v1/imports/cross-reconcile" -H "X-API-Key: $API_KEY"
vendor-host -
low Exfiltration
net-credential-useSKILL-web.md:765Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -s "https://api.ourmem.ai/v1/imports/IMPORT_ID" -H "X-API-Key: $API_KEY"
vendor-host -
low Exfiltration
net-credential-useSKILL-web.md:773Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl -sX POST "https://api.ourmem.ai/v1/imports/IMPORT_ID/intelligence" -H "X-API-Key: $API_KEY"
vendor-host
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5426 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "keywords"
Process rating: all ten parameters 67/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 31 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 70Execution cost. Instruction body is 5426 tokens
- 85Steps. 105 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 19 top-level sections: this looks like several domains in one skill
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)
- +3Description length 886: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 27 example trigger phrases
- +4Structure: 27 headings
- +3Step-by-step instructions: 105 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: 74.