Conciseness

Nearly every line carries non-obvious, plugin-specific knowledge Claude cannot be assumed to have ("claude plugin update is a no-op when the version string did not change", "One 4xx mentioning 'mode' pins recall for 6h", "/health answers 200 even with a bad key"). There is no padding and no explanation of concepts Claude already knows — it assumes competence and every token earns its place, matching the level-5 anchor; level 4 would require over-explanations that could be trimmed, and none are evident.

Actionability

Everything is copy-paste executable: the doctor invocation with flags (`node ${CLAUDE_PLUGIN_ROOT}/scripts/ov-memory-doctor.mjs --json --offline`), exact curl probes with headers and payloads, exact CLI remediations (`claude plugin marketplace update openviking && claude plugin uninstall ... && claude plugin install ...`), exact file paths, and a finding→meaning→action table. This matches the level-5 anchor (fully executable commands covering the common cases) rather than level 4, since no significant execution details are missing.

Workflow Clarity

The sequence is explicit and ordered: run the doctor, read the whole report before acting, then "Work top-down; fix the first ✗ and rerun before chasing the next", then targeted checks "only when the report is not conclusive", and finally "Confirm the fix by rerunning the doctor, then by observing an <openviking-context> block on the next prompt" — a complete feedback loop with validation checkpoints. This matches the level-5 anchor; the level-3 destructive/batch cap does not apply since the workflow is read-only and validated.

Progressive Disclosure

Sections are well organized and the single external pointer — "More symptoms, exact error strings and log stage names: [reference.md](reference.md)" — is one level deep and clearly signaled. However, no bundle directory exists in this skill (no references/, scripts/, or assets/), so the referenced reference.md (and the ov-memory-doctor.mjs the workflow depends on) cannot be verified to exist, leaving a dangling reference; this fits the level-4 anchor (good structure, references mostly clear, minor organization gaps) rather than level 5's easy, fully-resolvable navigation.

Specificity

The description enumerates concrete, specific scope rather than generic action: "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)". It matches the level-5 anchor (multiple specific concrete actions, comprehensive coverage) and exceeds level 4 because the sub-systems, config artifacts, and failure signatures are all named explicitly rather than with minor gaps.

Completeness

Both questions are answered explicitly: what — "Diagnose and fix the OpenViking memory plugin... the plugin install... the client configuration... and the connection"; when — "Use whenever memory 'isn't working': no <openviking-context> block, empty recall... right after installing/updating the plugin or switching servers/keys, or when the user asks for the plugin's status". This is the level-5 anchor verbatim in structure (clear what AND explicit when with concrete trigger phrases), and the voice is third person, so no penalty applies.

Trigger Term Quality

Trigger coverage is comprehensive with natural phrasings users would actually say: "memory not working", "check OpenViking", "plugin status", "recall 为空", "401", plus symptom descriptions ("empty recall", "captures not landing", "an offline statusline") and both English and Chinese synonyms. This fits the level-5 anchor (comprehensive natural terms including synonyms); level 4 would leave common variations missing, which is not the case.

Distinctiveness Conflict Risk

The niche is clear ("the OpenViking memory plugin on this machine") and mostly distinct, but a few listed triggers — "memory not working" and the bare "401" — are generic enough to fire for other memory-related skills or unrelated auth failures. This fits the level-4 anchor (mostly distinct, minor overlap risk with closely related skills) better than level 5, whose minimal-conflict bar the broad triggers slightly miss.