CtrlK
BlogDocsLog inGet started
Tessl Logo

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

76

Quality

98%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean, highly actionable, and workflow-sequenced with strong validation feedback loops. The only gap is that the one external reference (reference.md) is signaled but not actually shipped in the bundle.

Suggestions

Ship the referenced reference.md file (or remove the link to it) so the 'More symptoms, exact error strings and log stage names' pointer resolves.

Consider moving the large finding→action table to reference.md to keep SKILL.md as a tighter overview, since the table is the bulk of the token budget.

DimensionReasoningScore

Conciseness

The body is dense and signal-rich, assumes Claude's competence throughout (no basic concept explanations), and every line carries diagnostic value; it respects the token budget without padding.

5 / 5

Actionability

Provides fully executable, copy-paste-ready commands (curl probes, claude plugin/mcp commands, node doctor script) and a concrete finding→meaning→action table covering the common cases.

5 / 5

Workflow Clarity

Clear top-down sequence (run doctor → map findings top-down fixing the first ✗ and rerunning → targeted checks → Fixing) with explicit validation feedback loops ('rerun before chasing the next', 'Confirm the fix by rerunning the doctor, then by observing an <openviking-context> block').

5 / 5

Progressive Disclosure

Well-organized sections with a single clearly-signaled one-level-deep reference to reference.md, but that referenced file is not present in the bundle, which is a minor navigation gap that prevents a top score.

4 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: it states concrete capabilities across three subsystems, gives an explicit 'Use when...' clause with concrete scenarios, and lists natural trigger terms in two languages. It is distinct and unlikely to be selected for the wrong skill.

DimensionReasoningScore

Specificity

Lists multiple concrete diagnostic/fix actions across three named subsystems (install enablement/hooks/MCP server, ovcli.conf/ov.conf/env configuration, server reachability/401/403//mcp) with comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (diagnose and fix the three moving parts) and 'when' ('Use whenever memory isn't working' followed by concrete scenarios and a Triggers list).

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases in both English and Chinese, including synonyms and specific error tokens like '401', 'recall 为空', 'plugin status', covering what users would naturally say.

5 / 5

Distinctiveness Conflict Risk

A clearly scoped niche (OpenViking memory plugin doctor) with distinct, product-specific triggers that would not fire for unrelated skills; minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository
volcengine/OpenViking
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.