Elite Longterm Memory Backup

What to consider before installing: - Verify provenance: the registry metadata, SKILL.md, package.json, and _meta.json show inconsistent versions/IDs and 'Source: unknown' — confirm the publisher and repository (the package.json points to a GitHub repo; inspect it) before trusting the skill. - Local files: the CLI will create SESSION-STATE.md, MEMORY.md, and memory/<date>.md in whatever directory you run it from. These will contain potentially sensitive decisions and context—add them to .gitignore or store them encrypted if needed. - Optional cloud services: SKILL.md demonstrates Mem0 and SuperMemory usage. If you set MEM0_API_KEY or SUPERMEMORY_API_KEY, those services will receive extracted memories. Only provide keys if you trust the service and reviewed its privacy policy; treat those as high-sensitivity credentials. - Minimal privileges: the included bin/elite-memory.js is small and only reads/writes local files and checks a path under HOME; review its code (already included) before running. Avoid installing optional dependencies (mem0ai) unless you intentionally want remote auto-extraction. - Plugin configuration: enabling LanceDB or other agent plugins may require additional configuration/keys—check what data will be sent to OpenAI or other providers when enabling memorySearch. - If you need more assurance: ask the publisher for a signed release or a well-known repository URL, or request that the skill explicitly list optional external env vars (MEM0_API_KEY, SUPERMEMORY_API_KEY) in its registry metadata so their usage is visible up front.