Quantum Agent Memory

QAOA-powered memory optimization for AI agents. Uses quantum computing (Qiskit) to solve three memory management problems: clustering related memories, selec...

Before installing or running this skill: 1) Treat the manifest omissions as suspicious — the code requires QUANTUM_API_TOKEN, MEM0_URL, and an IBM quantum token even though the registry lists none. 2) Do not run the example systemd service as root; prefer a dedicated unprivileged system user. 3) Inspect and possibly edit hard-coded paths in scripts/ibm_cron.py (RESULTS_DIR, TOKEN_FILE) before running. 4) Understand that the OpenClaw plugin injects selected memories into every agent prompt — review and control which agents the plugin is enabled for. 5) Be aware QiskitRuntimeService.save_account will persist IBM credentials to local config; store tokens with least privilege and in a controlled location. 6) If you want to proceed, run the service in an isolated environment (container or dedicated VM), lock down MEM0 and API tokens, and review plugin files that will be placed into agent extension directories.

Type: OpenClaw Skill Name: quantum-agent-memory Version: 1.0.0 The skill bundle implements a complex quantum-based memory management system using QAOA, but contains several high-risk security practices. Specifically, the documentation in 'references/api-setup.md' provides a systemd service template that runs the API server as 'root', and 'scripts/ibm_cron.py' contains hardcoded absolute paths ('/home/dt/...') and directly accesses sensitive credentials in the user's home directory ('~/.ibm_quantum_token'). While the code appears to perform its stated function, these vulnerabilities and the lack of environment sanitization pose a risk of privilege escalation and credential exposure.