SKILLEMALL.ai
GitHub ↗ RU Sign in

CD 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".

volcengine/OpenViking Agent Skills author: volcengine AGPL-3.0 2 files body ≈ 4 026 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Diagnose and fix the OpenViking memory plugin on this machine: the plugin install (enablement, hooks, MCP server), the client configuration (ovcli.conf /…

As a process D 39/100 · Unfinished process — References files that are not bundled: examples/memory-plugin-shared/, scripts/setup.mjs

AnalyzerDockerAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
85/100
safety, quality, tests
Safety 60%
89
Quality 40%
80
Run on models
none yet
Process rating
D
39/100
Unfinished process
References files that are not bundled: examples/memory-plugin-shared/, scripts/setup.mjs
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 3

✓ No critical or high findings

Medium and low: 3
  • medium Exfiltration net-credential-use SKILL.md:123
    Credential used in a network call (verify the destination is the intended service)
    curl -sS -H "Authorization: Bearer $KEY" "$URL/health"  # 200 without account_id/user_id/role ⇒ key invalid
  • medium Exfiltration net-credential-use SKILL.md:124
    Credential used in a network call (verify the destination is the intended service)
    curl -sS -w '\n%{http_code}\n' -H "Authorization: Bearer $KEY" "$URL/api/v1/system/status"  # real 401/403
  • low Dangerous commands cmd-pipe-to-shell SKILL.md:78
    Downloads and executes remote code from an unrecognised host (pipe to shell) (documentation table row; the skill's own vendor host)
    | `not registered in installed_plugins.json` / `claude plugin list does not show …` | Plugin never installed, or installed under an old id | Re-run the one-line installer (`curl -fsSL https://openviki
    tablevendor-host

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: examples/memory-plugin-shared/
  • warning missing-ref reference to a missing file: scripts/setup.mjs
  • note edit-residue the text marks something as outdated (lines 52, 67, 82): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 39/100

Will not run. References files that are not bundled: examples/memory-plugin-shared/, scripts/setup.mjs
  • 0Tools and files. 2 referenced file(s) missing: examples/memory-plugin-shared/, scripts/setup.mjs
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 30Running it twice. 14 mutating operations with no state check
  • 70When it triggers. States when to use, but not when not to
  • 70Execution cost. Instruction body is 4026 tokens
  • 100Steps. 19 steps
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (6 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 6 example trigger phrases
  • +3Description length 670: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 19 items
  • +4Has examples (4 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.