ov-memory-doctor
Diagnose and fix the OpenViking memory plugin for Codex on this machine: the plugin install (marketplace, config.toml enablement, hook trust records, MCP server), the client configuration (ovcli.conf / ov.conf / OPENVIKING_* env — which one wins, what the API key claims) and the connection to the OpenViking server (reachability, 401/403, /mcp). Use whenever memory "isn't working": no <openviking-context> block appears, recall is always empty, turns are not captured, MCP memory tools are missing or fail, 401/403 errors, right after installing/updating the plugin or switching servers/keys, or when the user asks for the plugin's status. Trigger phrases include "memory not working", "check OpenViking", "plugin status", "记忆没生效", "插件状态", "连不上 OpenViking", "recall 为空", "401", "0 memories extracted". When the server runs on this machine (loopback url) it also checks the port, plugin-only keys in ov.conf that stop the server from starting, and `GET /ready`; everything else server-side stays wit
Unsigned, install at your own risk
UnverifiedThis skill has no cryptographic signature attached. We can't verify the contents match what the publisher intended.
Install this skill
Run this command in your terminal. No account required — it auto-detects your AI tool and installs the skill file.
npx @skills-hub-ai/cli install openviking-ov-memory-doctorSetup by platform
Install
One-click setup for your editorRun in your project root
npx @skills-hub-ai/cli install openviking-ov-memory-doctor --target claude-codeInstructions
Security
Reviews (0)
Related skills
Browse all →More from OpenViking
View source →More Build skills
Browse category →Frequently asked questions about ov-memory-doctor
What does the ov-memory-doctor skill do?
Diagnose and fix the OpenViking memory plugin for Codex on this machine: the plugin install (marketplace, config.toml enablement, hook trust records, MCP server), the client configuration (ovcli.conf / ov.conf / OPENVIKING_* env — which one wins, what the API key claims) and the connection to the OpenViking server (reachability, 401/403, /mcp). Use whenever memory "isn't working": no <openviking-context> block appears, recall is always empty, turns are not captured, MCP memory tools are missing or fail, 401/403 errors, right after installing/updating the plugin or switching servers/keys, or when the user asks for the plugin's status. Trigger phrases include "memory not working", "check OpenViking", "plugin status", "记忆没生效", "插件状态", "连不上 OpenViking", "recall 为空", "401", "0 memories extracted". When the server runs on this machine (loopback url) it also checks the port, plugin-only keys in ov.conf that stop the server from starting, and `GET /ready`; everything else server-side stays wit It's a reusable SKILL.md instruction set that loads into your AI coding assistant on demand, no prompt engineering, no copy-pasting every session.
How do I install the ov-memory-doctor skill?
Run `npx @skills-hub-ai/cli install openviking-ov-memory-doctor` from your terminal. The CLI writes the SKILL.md to the correct location for your AI tool (e.g. ~/.claude/skills/openviking-ov-memory-doctor/ for Claude Code or ~/.cursor/skills/ for Cursor with --target cursor) and adds it to your project's .skills.json lockfile.
Which AI tools does ov-memory-doctor work with?
ov-memory-doctor runs in Claude Code. It follows the open Agent Skills standard (SKILL.md), so the same skill works in every supported tool without modification.
Is the ov-memory-doctor skill free?
Yes. Every skill on skills-hub.ai is free and open-source. There are no premium tiers, paywalls, or usage limits. You only pay for whatever AI assistant you're already using.
How do I use ov-memory-doctor after installing it?
In Claude Code, type `/openviking-ov-memory-doctor` (or whatever slash command the skill registers) and the AI follows the skill's instructions immediately. You can also reference it by name in natural language, your AI loads the skill into context when relevant.
Can I share the ov-memory-doctor skill with my team?
Yes. Commit your project's .skills.json lockfile and teammates run `npx @skills-hub-ai/cli install` (no args) to install every skill at the exact version you pinned. Organization-scoped installs work via skills-hub.ai organizations.