Real Skill packageSource verifiedClawHub registry

XMemo Memory

Persistent, user-owned memory for agents. Use the standalone runtime to remember, recall, search, preserve restart continuity, manage TODOs and expenses, or diagnose XMemo when MCP tools are unavailable.

Identity and source

Publisher attributionXMemoregistry owner unverified by skillvetai
Functional categoryAgent Engineering, Security & Governanceautomatically inferred · 64% rule confidence
Package forminstruction with code6 recorded files
Canonical sourceClawHub registryclawhub:xmemo:xmemo
Open canonical source ↗

Platform declarations

These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.

OpenClawnative officialProvenance: registry distribution

Independent structural checks

These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.

Claude Codepasses structure
Checker 0.1.0 · agent-skills-2026-08-13+claude-code-docs-2026-08-13 · 9/2/2026.claude/skills/xmemo-memory

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenAI Codexpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+codex-docs-2026-08-13 · 9/2/2026.agents/skills/xmemo-memory

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenClawpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+openclaw-docs-2026-08-13 · 9/2/2026skills/xmemo-memory

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

Installation and inspection

This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.

clawhub install @xmemo/xmemo
clawhub inspect @xmemo/xmemo --version 1.1.15

Security evidence

SkillVetAI static result: no findings detected

This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.

Status
completed
Coverage
full text content
Files
6 / 6 inspected as text
Checked
9/2/2026, 4:32:29 AM
Scanner
0.1.3
Policy
1.0.3
4 inferred permission indicators
  • network access — automatically inferred
  • filesystem read — automatically inferred
  • filesystem write — automatically inferred
  • credential access — automatically inferred
1 dependency and API indicators
  • api: clawhub.ai
External clawhub result: clean

This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.

Evidence checked
9/1/2026, 10:13:22 PM
Release binding
Matches this record
  • vt: clean
  • skillspector: suspicious
  • llm: clean

Recorded files

The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.

Package content hashsha256:290396ffd0a01441b15604fd00e173621e025669f7cfd0bee9b1967291905a83
Show up to 6 recorded paths
  • CHANGELOG.md
  • references/operations.md
  • references/troubleshooting.md
  • scripts/xmemo-skill.mjs
  • skill-card.md
  • SKILL.md

Source changelog

- Add explicit read-only Knowledge support to `recall-context` through the opt-in `--include_knowledge true` flag; the default request remains Memory-only for backward compatibility. - Request the least-privilege `knowledge:read` scope during new formal Skill device login. Existing credentials are never expanded automatically; use verified reauthorization when Knowledge access is needed. - Include `recall-context` in top-level help and document the Knowledge scope, service feature, temporary-token, and untrusted-context boundaries. - Tests cover the opt-in request field, strict boolean parsing, login scope, top-level help, and Knowledge authorization documentation.

Release security diff

mediumCompared fixed releases 1.1.14 and 1.1.15; 0 finding and 0 permission indicators were added.

Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.

Change reasons and limitations
  • content hash changed

Observed release history

These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.

1.1.148/30/2026sha256:01f826cdcd610f6de72ab2d6d417ace99398ee686ee36d31554b78ac456d2285
1.1.138/29/2026sha256:7423736a3920ec9ed15af363b12ad911e4a24d5dcadfc24ac66c8ed2b6da1a8e
1.1.128/22/2026sha256:82400562ac3b6b980e8677a19210621850769b65f0b9e57770cb3a8640ee4e50
1.1.118/19/2026sha256:f5164f7fd3e1edf5818717bdb4fe2178e22f7dafaecc3bcc9a0c8c16ac19c364
1.1.108/18/2026sha256:3aed351a32aa6608bb68a953a65e5a6db652c6470f5be487429b4d2cfef710db
1.1.98/16/2026sha256:bb6884351d46365bdeea8cb428950dea7b3450cb9032b7b904f3fd8899355f25