Agent skill · volcengine
ov-memory-doctor
Diagnose and fix the OpenViking memory plugin for Codex on this machine: the plugin install (enablement, hooks, MCP server), the client configuration (ovcli.conf / ov.conf / OPENVIKING_* env) and the connection to the OpenViking server (reachability, 401/403, /mcp). Use whenever memory "isn't working": no <openviking-context> block, empty recall, captures not landing, missing or failing MCP memory tools, 401/403, an offline statusline, right after installing/updating the plugin or switching servers/keys, or when the user asks for the plugin's status. Triggers: "memory not working", "check OpenViking", "plugin status", "记忆没生效", "插件状态", "连不上 OpenViking", "recall 为空", "401".
What it needs
About 9k tokens when loaded.
What this skill does
OpenViking Memory Doctor (Codex) Troubleshooting for the OpenViking memory plugin. Three things go wrong on a user's machine, each silently: Install — marketplace registration, [plugins."openviking-memory@openviking"] and [features] hooks (or legacy pluginhooks) in ~/.codex/config.toml, per-hook trust records, the stdio MCP proxy. When these are wrong, hooks never run and nothing is logged anywhere. Configuration — ~/.openviking/ovcli.conf, ~/.openviking/ov.conf and OPENVIKING environment variables. A malformed file reads as "no config" and the plugin silently falls back to http://127.0.0.1:1933 with no key; a stray env var silently overrides the file. Connection — /health answers 200 even with a bad key, so everything can look reachable while every real request 401s. When the resolved url is loopback, the server runs on this machine and the doctor adds a Server health section: whether anything listens on the port, plugin-only keys in ov.conf (claudecode, codex, server.url) that make the server refuse to start, and GET /ready — the server's own per-subsystem verdict (agfs, vectordb, api keys, embedding, ollama). For a remote server only /ready is probed. Everything else on the server side — config validation, live embedding probe, native engine, disk — is openviking-server doctor, run in the server's Python environment. Step 1 — run the doctor The script ships inside the plugin. Codex runs hooks from the plugin cache, so run the doctor from there (newest version directory): If that directory does not exist, fall back to the marketplace copy reported by codex plugin list --json (.installed[] select(.pluginId == "openviking-memory@openviking") .source.path), or to a source checkout's examples/codex-memory-plugin. Options: --json (machine-readable), --offline (skip network probes), --timeout <ms> (per probe, default 5000), --no-color. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills volcengine/ov-memory-doctor--e80a2b