What problem does it solve?
When the OpenViking memory plugin for Claude Code silently stops working — no context injection, empty recall, captures not landing, or MCP tools failing with 401/403 — this Skill pinpoints the root cause across the plugin install, client configuration, and server connection instead of leaving you to guess.
Core Features & Use Cases
- Automated diagnostic report: Runs a doctor script covering six sections — Environment, Plugin install, Configuration, Connection, Server health, and Recent activity — with a summary of every failure and its fix.
- Finding-to-fix mapping: A lookup table translates each doctor finding (e.g., unparseable ovcli.conf, rejected API key, stale plugin cache, proxy/TLS issues) into a concrete remediation step.
- Targeted manual probes: Provides curl and CLI commands to verify hooks, API key identity, the /mcp endpoint, and capture delivery when the report is inconclusive.
- Use Case: After updating the plugin your statusline shows offline and recall returns nothing; run the doctor, find that an env var is overriding ovcli.conf, remove it, and confirm the fix with a rerun.
Quick Start
Ask the assistant to run the OpenViking memory doctor and diagnose why the memory plugin is not working on this machine.