Datris Memory
PassAudited by ClawScan on May 7, 2026.
Overview
This appears to be a coherent Datris memory skill, but it is designed to upload local memory markdown files into a persistent Datris-backed semantic index.
Install this only if you want Datris to index your local MEMORY.md and memory/*.md files for long-term recall. Before first use, review those files for secrets or sensitive personal data, confirm you trust the configured Datris MCP server, and understand that the skill may create or update Datris resources in the openclaw catalog.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Private or inaccurate content in MEMORY.md or memory/*.md may be retained in Datris and reused in future memory answers.
The skill intentionally creates a persistent semantic memory index from local markdown memory files, which can later influence retrieval and agent context.
Datris is the long-term semantic memory layer. Local memory files are the source of truth. Datris is rebuilt from them
Review the local memory files before ingestion, avoid storing secrets or highly sensitive data there, and treat retrieved memory as context to verify rather than unquestionable truth.
The configured Datris MCP server and Datris backend may receive and store the contents of the local memory files.
The skill depends on an MCP server boundary and uploads local memory data through Datris tooling, so the user must trust that MCP endpoint and its data handling.
Use the Datris Platform as a long-term semantic memory layer through the Datris MCP server
Use only a trusted Datris MCP server/account, verify where the data is stored, and confirm the Datris retention and access controls match your expectations.
A sync or re-ingestion run may modify or temporarily remove Datris search results for the indexed memory files.
The skill instructs the agent to perform mutating Datris operations, including deleting and re-uploading index chunks. This is aligned with keeping the Datris index synchronized, but it changes external Datris state.
When re-ingesting a file that already exists in the pipeline, delete its existing chunks first, wait for the delete to complete, then upload
Confirm that local markdown files are the intended source of truth and that Datris index changes are acceptable before running ingestion or sync.
Ordinary questions about past notes may cause the agent to consult or initialize the Datris memory layer.
The skill asks to be invoked broadly for memory-related requests, including when the user does not explicitly mention Datris. This is purpose-aligned but expands when Datris memory behavior may be used.
Use this skill any time the user mentions saving, recalling, ingesting, syncing, or searching memory through Datris — and any time they ask a memory-shaped question
If you install it, expect Datris to be the default memory retrieval path; ask the agent to avoid Datris for a task if you want purely local handling.