← 返回 Skills 市场
tsangho

Viking Memory System Ultra 2

作者 tsangho · GitHub ↗ · v0.0.1 · MIT-0
linuxdarwin ⚠ suspicious
94
总下载
0
收藏
0
当前安装
1
版本数
在 OpenClaw 中安装
/install viking-memory-ultra2
功能描述
Viking Memory System Ultra - 分层记忆基座。特性:动态回流(语义晋升)、智能权重(对数增长)、可逆归档(多粒度摘要)。 核心脚本:sv_write, sv_read, sv_find, sv_autoload, sv_promote, sv_weight, sv_compress, s...
安全使用建议
This skill implements the claimed memory-management features but will send file contents and aggregated context from your SV_WORKSPACE to external LLM endpoints using API keys embedded inside the shipped scripts. Before installing or running: 1) Do NOT use it on sensitive/production data until you audit and modify the code. 2) Inspect and remove any hard-coded API keys; replace them with your own provider keys stored in environment variables (and update scripts to read those env vars). 3) If you don't want remote transmission, disable or stub out the llm_* calls (sv_archive_summary, sv_promote, llm_interface) so all operations remain local. 4) Test in a disposable account or isolated VM to observe network behavior (curl calls and destinations). 5) Be aware the installer copies scripts into ~/.openclaw/viking and the skill may create ~/.openclaw/viking-global and shared files. If you proceed, ensure you understand and control which third-party services receive your memory data.
功能分析
Type: OpenClaw Skill Name: viking-memory-ultra2 Version: 0.0.1 The Viking Memory System Ultra bundle is classified as suspicious primarily due to the inclusion of hardcoded API keys for MiniMax and NVIDIA services within `llm_interface.sh`, `sv_archive_summary.sh`, and `sv_promote.sh`. These scripts are designed to transmit user-generated memory content to external endpoints (e.g., integrate.api.nvidia.com and api.minimaxi.com) for summarization and relevance analysis. While this functionality is consistent with the stated purpose of the skill, the use of developer-provided hardcoded credentials creates a significant privacy risk and a potential data exfiltration path. Additionally, `sv_write_v2.sh` contains a functional bug where a quoted heredoc ('EOF') prevents the expansion of metadata variables like $MEMORY_ID, resulting in malformed memory files.
能力评估
Purpose & Capability
Name/description (hierarchical memory, compression, promote, etc.) align with the included scripts: sv_write, sv_read, sv_find, sv_promote, sv_weight, sv_compress, sv_archive, sv_decompress. Required binaries and env vars (bash, python3, curl, VIKING_HOME, SV_WORKSPACE) are coherent with the implementation. However, the implementation embeds provider credentials directly in scripts (see llm_interface.sh, sv_archive_summary.sh, sv_promote.sh) instead of requiring explicit user-supplied keys — this is unexpected and suspicious for a public skill.
Instruction Scope
Runtime scripts legitimately read many files under the declared workspace and frontmatter metadata (expected for a memory manager). But several scripts transmit memory file contents (or aggregated context) to external APIs via curl (NVIDIA Qwen and a 'MiniMax' endpoint). Those network calls will send user data to third parties; the SKILL.md does not document these endpoints nor warn that private memory will be sent externally. The sv_promote/sv_archive_summary/llm_interface modules prepare and send content from user files to remote LLM services — this is broad data transmission beyond local operations.
Install Mechanism
No remote download or package installation is present; install.sh simply copies provided scripts into VIKING_HOME and marks them executable. That is low-risk compared to fetching arbitrary archives. Still, installing will place executable scripts into the user's ~/.openclaw/viking and may create ~/.openclaw/viking-global directories (sv_write_v2 uses viking-global).
Credentials
Declared environment requirements (VIKING_HOME, SV_WORKSPACE) are proportional. However, the code contains hard-coded API keys and bearer tokens (MiniMax API key and NVIDIA API key strings) rather than asking for credentials via environment variables. Those embedded credentials will be used automatically to call external services and could leak sensitive content; this is disproportionate and not justified by the manifest which lists no external credentials or privacy warnings.
Persistence & Privilege
Skill is not force-enabled (always: false) and is user-invocable. It does write files into its own VIKING_HOME and may create a shared viking-global directory for synced memories; this is expected for a memory manager. It does not request system-wide privileges beyond filesystem access in the user's home directory.
如何使用
  1. 确保已安装 OpenClaw(本地或 Docker 部署)
  2. 在对话框中输入安装命令:/install viking-memory-ultra2
  3. 安装完成后,直接呼叫该 Skill 的名称或使用 /viking-memory-ultra2 触发
  4. 根据 Skill 的参数说明提供必要输入,即可获得结构化输出
版本历史
v0.0.1
test
元数据
Slug viking-memory-ultra2
版本 0.0.1
许可证 MIT-0
累计安装 0
当前安装数 0
历史版本数 1
常见问题

Viking Memory System Ultra 2 是什么?

Viking Memory System Ultra - 分层记忆基座。特性:动态回流(语义晋升)、智能权重(对数增长)、可逆归档(多粒度摘要)。 核心脚本:sv_write, sv_read, sv_find, sv_autoload, sv_promote, sv_weight, sv_compress, s... 它是一个面向 Claude Code / OpenClaw 的 AI Agent Skill 插件,目前累计下载 94 次。

如何安装 Viking Memory System Ultra 2?

在 OpenClaw 或 Claude Code 对话框中运行命令「/install viking-memory-ultra2」即可一键安装,无需额外配置。

Viking Memory System Ultra 2 是免费的吗?

是的,Viking Memory System Ultra 2 完全免费,采用 MIT-0 许可证,可自由下载、安装和使用。

Viking Memory System Ultra 2 支持哪些平台?

Viking Memory System Ultra 2 跨平台运行,可在任意部署了 OpenClaw / Claude Code 的环境中使用(linux, darwin)。

谁开发了 Viking Memory System Ultra 2?

由 tsangho(@tsangho)开发并维护,当前版本 v0.0.1。

💬 留言讨论