Agent skill · volcengine
ov-memory-doctor
Diagnose and fix the OpenViking memory plugin 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 Client-side troubleshooting for the OpenViking memory plugin. The plugin has three moving parts and each fails silently in its own way: Install — marketplace registration, plugin enablement, the nine hooks, 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, resolved as env → ovcli.conf → ov.conf → defaults. A malformed file reads as "no config", which silently disables the plugin; a stray env var silently overrides the file. Connection — /health answers 200 even with a bad key, so the statusline can be green 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 Options: --json (machine-readable), --offline (skip network probes), --timeout <ms> (per probe, default 5000), --no-color. The report has six sections — Environment, Plugin install, Configuration, Connection, Server health, Recent activity — and a Summary listing every ✗/⚠ with a fix. Read the whole report before acting: a single root cause usually shows up in several sections (for example a bad key → "api key rejected" + "system/status → 401" + turnsfailed > 0). If the report says "this script is not running from the registered install", rerun it from the path it prints — Claude Code executes hooks from that copy. The API key is never printed in full. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills volcengine/ov-memory-doctor