Conciseness

The body is dense with non-obvious operational detail (tool roles, limit ranges, alias fallbacks) and wastes little on concepts Claude already knows. However, the viking://~ alias-fallback paragraph in step 3 and the terse "Resource directory rules do not apply to Memory" sentence are spots that could be trimmed or tightened, matching anchor 4 ("Efficient; minor instances of over-explanation that could be trimmed") rather than the fully lean anchor 5.

Actionability

Guidance is directly executable: concrete tool calls with argument specifics ("find... with limit around 5-10", "search with mode='context'", "target_uri: 'viking://~/memories/experiences'") and a worked example with an actual query string ("deployment image pull failure private registry"). As an instruction-only skill, its guidance is copy-paste ready and covers the common cases, matching anchor 5.

Workflow Clarity

The recall loop is a clear 5-step sequence with feedback guidance ("Make at most one focused follow-up search when execution fails for a materially new reason", judge results then read 1-3 URIs, "If nothing relevant comes back, proceed without memory"), and the persist half is sequenced during/after work. It sits between anchor 4 and 5: most checkpoints are present, but there is no verification step after persisting (e.g., a health/read-back check), a minor validation gap that anchor 5's explicit validation requirement would demand.

Progressive Disclosure

The body is an ~95-line overview with a real, well-signaled, one-level-deep reference: references/optional-tools.md is linked twice with a clear condition for when to read it, and the reference file exists and delivers the deferred detail. It falls just short of anchor 5 because some edge-case detail (the viking://~ alias and pre-alias server fallback in step 3) is inlined in SKILL.md where it could live in the reference file — a minor organization gap matching anchor 4.

Specificity

"Recall and persist long-term memory through the OpenViking MCP tools" names the domain, and concrete actions follow: "retrieve relevant prior knowledge with find/search/read" and "persist durable facts, preferences, decisions, and lessons with remember". This matches the anchor "Lists several specific actions; minor gaps in coverage" — the import path (add_resource) and maintenance tools are not mentioned, keeping it below the comprehensive anchor 5.

Completeness

The "what" is explicit ("Recall and persist long-term memory through the OpenViking MCP tools... retrieve... with find/search/read... persist... with remember") and the "when" is explicit with concrete triggers ("Use at the start of any substantive task (coding, configuration, debugging, multi-step or tool-based work)... during or after work") plus a negative boundary ("Do not use for casual chat or simple factual questions"). This clearly matches anchor 5: both what and when answered with concrete trigger phrases.

Trigger Term Quality

Natural trigger phrases are present: "coding, configuration, debugging, multi-step or tool-based work", "remember", "recall", "long-term memory", "preferences", and "lessons" — terms users would plausibly say. A few natural synonyms (e.g., "notes", "knowledge base", "past sessions") are missing, which fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

Distinctiveness Conflict Risk

The OpenViking-specific framing and explicit tool names give it a clear niche, but the "when" clause ("any substantive task (coding, configuration, debugging, multi-step or tool-based work)") is broad and could overlap with other memory or context-management skills that trigger on the same generic conditions. This fits anchor 4 ("Mostly distinct; minor overlap risk with closely related skills") rather than anchor 5's minimal-conflict positioning.