@openviking/openclaw-plugin 2026.5.8 → 2026.5.10-dev.3

package/INSTALL-AGENT.md

@@ -9,14 +9,14 @@ User-facing docs:
 
 ## Identity
 
-This package is the OpenClaw plugin `@openviking/openclaw-plugin`.
+This package is the OpenClaw plugin `@openclaw/openviking`.
 
 | User intent | Command |
 | --- | --- |
-| Fresh install, latest | `openclaw plugins install @openviking/openclaw-plugin` |
-| Upgrade plugin to latest | `openclaw plugins install @openviking/openclaw-plugin` |
+| Fresh install, latest | `openclaw plugins install @openclaw/openviking` |
+| Upgrade plugin to latest | `openclaw plugins install @openclaw/openviking` |
 | Install or upgrade a specific release | Use the published ClawHub package selector if available; otherwise ask before using backup `ov-install --plugin-version=<REF>` |
-| Upgrade only the plugin | `openclaw plugins install @openviking/openclaw-plugin` |
+| Upgrade only the plugin | `openclaw plugins install @openclaw/openviking` |
 | Show installed plugins | `openclaw plugins list` |
 | Backup install when ClawHub is unavailable | `npx -y openclaw-openviking-setup-helper@latest --base-url <URL> [--api-key <KEY>]` |
 | Operate on a specific OpenClaw instance | add `--workdir <path>` |
@@ -31,7 +31,7 @@ clawhub install openviking
 That installs an AgentSkill, not the plugin. The plugin install command is:
 
 ```bash
-openclaw plugins install @openviking/openclaw-plugin
+openclaw plugins install @openclaw/openviking
 ```
 
 ## Required Inputs
@@ -53,7 +53,7 @@ Never silently replace another context engine.
 Use this workflow for normal installs and upgrades from published packages.
 
 ```bash
-openclaw plugins install @openviking/openclaw-plugin
+openclaw plugins install @openclaw/openviking
 openclaw openviking setup --base-url <OPENVIKING_URL> --api-key <API_KEY> --json
 openclaw gateway restart
 openclaw openviking status --json
@@ -62,7 +62,7 @@ openclaw openviking status --json
 If the registry prefix is required:
 
 ```bash
-openclaw plugins install clawhub:@openviking/openclaw-plugin
+openclaw plugins install clawhub:@openclaw/openviking
 ```
 
 ## Setup JSON Contract
@@ -157,7 +157,7 @@ Requirements:
 
 Version boundaries:
 
-- `2026.4.8` is the minimum supported OpenClaw version for the current `@openviking/openclaw-plugin` plugin.
+- `2026.4.8` is the minimum supported OpenClaw version for the current `@openclaw/openviking` plugin.
 - `2026.5.3` starts requiring compiled JavaScript runtime output during package install when a plugin package declares TypeScript entries.
 - `2026.5.4` and later no longer fall back to `.ts` source for installed/global plugin runtime loading when the compiled JavaScript output is missing; the plugin may be skipped.
 - Published ClawHub packages are built before release and include `dist/*.js`, so normal users do not need to build locally.
@@ -220,7 +220,7 @@ openclaw plugins list
 Fresh install:
 
 ```bash
-openclaw plugins install @openviking/openclaw-plugin
+openclaw plugins install @openclaw/openviking
 openclaw openviking setup --base-url <OPENVIKING_URL> --api-key <API_KEY> --json
 openclaw gateway restart
 openclaw openviking status --json
@@ -307,7 +307,7 @@ Same plugin ID (openviking, >= 0.3.x):
 
 ```bash
 rm -rf ~/.openclaw/extensions/openviking/
-openclaw plugins install @openviking/openclaw-plugin
+openclaw plugins install @openclaw/openviking
 openclaw openviking setup --reconfigure
 openclaw gateway restart
 openclaw openviking status --json
@@ -319,7 +319,7 @@ Old plugin ID (memory-openviking, < 0.3.x):
 openclaw plugins uninstall memory-openviking 2>/dev/null || true
 openclaw config set plugins.slots.memory none
 rm -rf ~/.openclaw/extensions/memory-openviking/
-openclaw plugins install @openviking/openclaw-plugin
+openclaw plugins install @openclaw/openviking
 openclaw openviking setup --base-url <OPENVIKING_URL> --api-key <API_KEY> --json
 openclaw gateway restart
 openclaw openviking status --json
@@ -333,7 +333,7 @@ Existing config fields are preserved during migration. The new plugin reads old
 
 ## Backup Path: ov-install
 
-`ov-install` is the backup path, not the primary user install path. Use it when `openclaw plugins install @openviking/openclaw-plugin` cannot reach ClawHub, is rate-limited, or when the user explicitly wants a source ref / Git branch install.
+`ov-install` is the backup path, not the primary user install path. Use it when `openclaw plugins install @openclaw/openviking` cannot reach ClawHub, is rate-limited, or when the user explicitly wants a source ref / Git branch install.
 
 Backup install:
 
@@ -352,4 +352,4 @@ Backup/source commands:
 | Show helper-tracked version | `ov-install --current-version` |
 | Update helper-managed install | `ov-install --update` |
 
-For user installs, always try `openclaw plugins install @openviking/openclaw-plugin` first. Choose `ov-install` only as the backup path.
+For user installs, always try `openclaw plugins install @openclaw/openviking` first. Choose `ov-install` only as the backup path.

package/INSTALL-ZH.md

@@ -1,12 +1,12 @@
 # 为 OpenClaw 安装 OpenViking
 
-OpenViking 通过 `@openviking/openclaw-plugin` 插件为 OpenClaw 提供长期记忆、知识库检索、语义搜索和 RAG 上下文能力。
+OpenViking 通过 `@openclaw/openviking` 插件为 OpenClaw 提供长期记忆、知识库检索、语义搜索和 RAG 上下文能力。
 
 这份文档同时面向用户和自动化 agent：用户可以按步骤执行，agent 可以按命令和 JSON 结果判断下一步。
 
 ## 不要把插件和 Skill 装混
 
-`@openviking/openclaw-plugin` 是 OpenClaw 插件。
+`@openclaw/openviking` 是 OpenClaw 插件。
 
 不要用下面这个命令安装本插件：
 
@@ -19,7 +19,7 @@ clawhub install openviking
 安装插件应使用：
 
 ```bash
-openclaw plugins install @openviking/openclaw-plugin
+openclaw plugins install @openclaw/openviking
 ```
 
 ## 前置要求
@@ -36,7 +36,7 @@ OpenClaw 插件包版本边界：
 - `2026.4.8` 是当前插件支持的最低 OpenClaw 版本。
 - `2026.5.3` 开始，OpenClaw 在安装包时会校验 TypeScript 插件入口是否有编译后的 JavaScript 产物。
 - `2026.5.4` 及之后，已安装/全局插件如果缺少编译后的 JavaScript，运行时不再回退加载 `.ts` 源码，插件可能被跳过。
-- 推荐的 `openclaw plugins install @openviking/openclaw-plugin` 会安装已经发布并包含 `dist/*.js` 的插件包，普通用户不需要本地编译。
+- 推荐的 `openclaw plugins install @openclaw/openviking` 会安装已经发布并包含 `dist/*.js` 的插件包，普通用户不需要本地编译。
 - `ov-install` 是备用/源码安装路径。当 ClawHub 或 OpenClaw 插件管理器路径不可用、被限流，或者明确需要测试源码 ref 时才使用。目标 OpenClaw `>= 2026.5.3` 时，它会在安装过程中编译插件。
 
 快速检查：
@@ -87,13 +87,13 @@ curl http://127.0.0.1:1933/health
 ### 1. 安装插件
 
 ```bash
-openclaw plugins install @openviking/openclaw-plugin
+openclaw plugins install @openclaw/openviking
 ```
 
 如果你的 OpenClaw 环境需要显式 registry 前缀，使用：
 
 ```bash
-openclaw plugins install clawhub:@openviking/openclaw-plugin
+openclaw plugins install clawhub:@openclaw/openviking
 ```
 
 ### 2. 配置插件
@@ -271,7 +271,7 @@ python examples/openclaw-plugin/health_check_tools/ov-healthcheck.py
 
 ## 备用路径：ov-install
 
-`ov-install` 是备用路径，不是主安装方式。仅当 `openclaw plugins install @openviking/openclaw-plugin` 无法访问 ClawHub、被限流，或者你明确需要从 Git 分支/源码 ref 安装测试时使用。
+`ov-install` 是备用路径，不是主安装方式。仅当 `openclaw plugins install @openclaw/openviking` 无法访问 ClawHub、被限流，或者你明确需要从 Git 分支/源码 ref 安装测试时使用。
 
 先尝试 OpenClaw 插件管理器。如果该路径不可用，再执行：
 
@@ -292,7 +292,7 @@ ov-install
 | `--agent-prefix PREFIX` | Agent 路由前缀 |
 | `--update` | 更新 helper 管理的安装 |
 
-面向用户的安装，请先使用 `openclaw plugins install @openviking/openclaw-plugin`。只有作为备用路径时才选择 `ov-install`。
+面向用户的安装，请先使用 `openclaw plugins install @openclaw/openviking`。只有作为备用路径时才选择 `ov-install`。
 
 ## 从 ov-install 迁移到 openclaw plugin install
 
@@ -307,7 +307,7 @@ ov-install 的 context-engine 部署会将文件写入 `~/.openclaw/extensions/o
 rm -rf ~/.openclaw/extensions/openviking/
 
 # 通过 OpenClaw 插件管理器安装
-openclaw plugins install @openviking/openclaw-plugin
+openclaw plugins install @openclaw/openviking
 
 # 重新配置（openclaw.json 中的已有配置会保留）
 openclaw openviking setup --reconfigure
@@ -330,7 +330,7 @@ openclaw config set plugins.slots.memory none
 rm -rf ~/.openclaw/extensions/memory-openviking/
 
 # 安装新插件
-openclaw plugins install @openviking/openclaw-plugin
+openclaw plugins install @openclaw/openviking
 openclaw openviking setup --base-url <OPENVIKING_URL> --api-key <API_KEY> --json
 openclaw gateway restart
 openclaw openviking status --json

package/INSTALL.md

@@ -1,12 +1,12 @@
 # Install OpenViking for OpenClaw
 
-OpenViking provides long-term memory, knowledge base search, semantic retrieval, and RAG-style context for OpenClaw through the `@openviking/openclaw-plugin` plugin.
+OpenViking provides long-term memory, knowledge base search, semantic retrieval, and RAG-style context for OpenClaw through the `@openclaw/openviking` plugin.
 
 This guide describes the current plugin install flow. It is written for both people and automation agents.
 
 ## Do Not Install The Skill By Mistake
 
-`@openviking/openclaw-plugin` is an OpenClaw plugin.
+`@openclaw/openviking` is an OpenClaw plugin.
 
 Do not use this command for plugin installation:
 
@@ -19,7 +19,7 @@ That command installs an AgentSkill named `openviking`, not the OpenClaw plugin.
 Use this plugin command instead:
 
 ```bash
-openclaw plugins install @openviking/openclaw-plugin
+openclaw plugins install @openclaw/openviking
 ```
 
 ## Requirements
@@ -36,7 +36,7 @@ OpenClaw plugin package boundaries:
 - `2026.4.8` is the minimum supported OpenClaw version for the current plugin.
 - `2026.5.3` starts validating package installs so TypeScript plugin entries need compiled JavaScript output.
 - `2026.5.4` and later stop falling back to `.ts` source for installed/global plugin runtime loading when compiled JavaScript is missing.
-- The recommended `openclaw plugins install @openviking/openclaw-plugin` path installs a published package that already includes `dist/*.js`.
+- The recommended `openclaw plugins install @openclaw/openviking` path installs a published package that already includes `dist/*.js`.
 - `ov-install` is the backup/source install path. Use it when ClawHub or the OpenClaw plugin manager path is unavailable/rate-limited, or when explicitly testing a source ref. For OpenClaw `>= 2026.5.3`, it builds the plugin during installation.
 
 Quick check:
@@ -87,13 +87,13 @@ Use this path for normal users, production installs, and agent-assisted installs
 ### 1. Install The Plugin
 
 ```bash
-openclaw plugins install @openviking/openclaw-plugin
+openclaw plugins install @openclaw/openviking
 ```
 
 If your OpenClaw installation requires an explicit registry prefix, use:
 
 ```bash
-openclaw plugins install clawhub:@openviking/openclaw-plugin
+openclaw plugins install clawhub:@openclaw/openviking
 ```
 
 ### 2. Configure The Plugin
@@ -253,7 +253,7 @@ This checks the Gateway to OpenViking path by injecting a real conversation and
 
 ## Backup Path: ov-install
 
-`ov-install` is the backup path, not the primary install path. Use it when `openclaw plugins install @openviking/openclaw-plugin` cannot reach ClawHub, is rate-limited, or when you explicitly need to install/test plugin files from a Git branch or source ref.
+`ov-install` is the backup path, not the primary install path. Use it when `openclaw plugins install @openclaw/openviking` cannot reach ClawHub, is rate-limited, or when you explicitly need to install/test plugin files from a Git branch or source ref.
 
 Try the OpenClaw plugin manager first. If that path is unavailable, run:
 
@@ -274,7 +274,7 @@ Useful backup/source flags:
 | `--agent-prefix PREFIX` | Agent routing prefix |
 | `--update` | Update an existing helper-managed install |
 
-For user-facing installs, use `openclaw plugins install @openviking/openclaw-plugin` first. Choose `ov-install` only as the backup path.
+For user-facing installs, use `openclaw plugins install @openclaw/openviking` first. Choose `ov-install` only as the backup path.
 
 ## Migrate From ov-install To openclaw plugin install
 
@@ -289,7 +289,7 @@ The ov-install context-engine deployment writes files to `~/.openclaw/extensions
 rm -rf ~/.openclaw/extensions/openviking/
 
 # Install via the OpenClaw plugin manager
-openclaw plugins install @openviking/openclaw-plugin
+openclaw plugins install @openclaw/openviking
 
 # Reconfigure (your existing config in openclaw.json is preserved)
 openclaw openviking setup --reconfigure
@@ -347,7 +347,7 @@ openclaw config set plugins.slots.memory none
 rm -rf ~/.openclaw/extensions/memory-openviking/
 
 # Install new plugin
-openclaw plugins install @openviking/openclaw-plugin
+openclaw plugins install @openclaw/openviking
 openclaw openviking setup --base-url <OPENVIKING_URL> --api-key <API_KEY> --json
 openclaw gateway restart
 openclaw openviking status --json

package/README.md

@@ -1,4 +1,4 @@
-# @openviking/openclaw-plugin — OpenViking OpenClaw Plugin
+# @openclaw/openviking — OpenViking OpenClaw Plugin
 
 OpenClaw context-engine plugin for OpenViking remote memory, context database, RAG and semantic retrieval.
 
@@ -7,29 +7,29 @@ OpenClaw context-engine plugin for OpenViking remote memory, context database, R
 This page is for the **OpenClaw plugin package**:
 
 ```
-@openviking/openclaw-plugin
+@openclaw/openviking
 ```
 
 **Do NOT** install the plugin with `clawhub install openviking` — that installs the `openviking` AgentSkill (under `skills/openviking`), which is a different thing.
 
-For **agent-assisted plugin setup**, ask the agent to follow [INSTALL-AGENT.md](./INSTALL-AGENT.md). The primary install path is still `openclaw plugins install @openviking/openclaw-plugin`.
+For **agent-assisted plugin setup**, ask the agent to follow [INSTALL-AGENT.md](./INSTALL-AGENT.md). The primary install path is still `openclaw plugins install @openclaw/openviking`.
 
 ## Install (Natural Language)
 
 Ask your agent:
 
-> Install the OpenClaw plugin @openviking/openclaw-plugin for OpenViking remote memory. My server is at `http://my-server:1933` and my API key is `sk-xxx`.
+> Install the OpenClaw plugin @openclaw/openviking for OpenViking remote memory. My server is at `http://my-server:1933` and my API key is `sk-xxx`.
 
 Or in Chinese:
 
-> 帮我安装 OpenViking 远程记忆插件 @openviking/openclaw-plugin。我的服务器地址是 `http://my-server:1933`，API key 是 `sk-xxx`。
+> 帮我安装 OpenViking 远程记忆插件 @openclaw/openviking。我的服务器地址是 `http://my-server:1933`，API key 是 `sk-xxx`。
 
 The agent will automatically run install → setup → restart → verify. No manual steps needed.
 
 ## Install (Command Line)
 
 ```bash
-openclaw plugins install @openviking/openclaw-plugin
+openclaw plugins install @openclaw/openviking
 openclaw openviking setup --base-url http://my-server:1933 --api-key sk-xxx --json
 openclaw gateway restart
 openclaw openviking status --json
@@ -39,7 +39,7 @@ The `setup` command automatically activates the context-engine slot and validate
 
 ## Search Keywords
 
-@openviking/openclaw-plugin, openclaw openviking plugin, openviking remote memory plugin, OpenViking Context Database plugin, install-openviking-memory.
+@openclaw/openviking, openclaw openviking plugin, openviking remote memory plugin, OpenViking Context Database plugin, install-openviking-memory.
 
 ## Documentation
 
@@ -197,13 +197,14 @@ So `afterTurn()` is closer to "incremental append plus threshold-triggered async
 
 ## Tools and Expandability
 
-Beyond automatic behavior, the plugin exposes six tools directly:
+Beyond automatic behavior, the plugin exposes seven tools directly:
 
 - `memory_recall`: explicit long-term memory search
 - `memory_store`: write text into an OpenViking session and trigger commit
 - `memory_forget`: delete by URI, or search first and remove a single strong match
 - `ov_archive_expand`: expand a concrete archive back into raw messages
-- `ov_import`: import a resource or skill; defaults to resource and uses `kind: "skill"` for skills
+- `add_resource`: import a document, directory, URL, or Git repository as an OpenViking resource
+- `add_skill`: import or register an OpenViking agent skill
 - `memory_search`: search OpenViking resources and skills, especially after importing them
 
 They serve different roles:
@@ -212,7 +213,8 @@ They serve different roles:
 - `memory_recall` gives the model an explicit follow-up search path
 - `memory_store` is for immediately persisting clearly important information
 - `ov_archive_expand` is the "go back to archive detail" escape hatch when summaries are not enough
-- `ov_import` lets the agent complete explicit import requests without asking the user to remember slash commands
+- `add_resource` lets the agent save explicit document or repository import requests without asking the user to remember slash commands
+- `add_skill` imports skills into OpenViking, while `add_resource` imports resources
 - `memory_search` closes the loop after import by letting the user or agent confirm and consume resources and skills
 
 `ov_archive_expand` is especially important because `assemble()` normally returns archive summaries and indexes, not the full raw transcript.
@@ -227,8 +229,8 @@ Resource and skill imports are intentionally separate because they land in diffe
 The plugin also registers explicit slash commands for manual imports:
 
 ```text
-/ov-import ./README.md --to viking://resources/openviking-readme --wait
-/ov-import ./skills/install-openviking-memory --kind skill --wait
+/add-resource ./README.md --to viking://resources/openviking-readme --wait
+/add-skill ./skills/install-openviking-memory --wait
 /memory-search "OpenViking install" --uri viking://resources/openviking-readme
 /memory-search "memory install skill" --uri viking://agent/skills
 ```