Conciseness

The body is dense, imperative, and assumes Claude's competence: no concept tutorials, no filler, and every sentence carries novel information the model could not infer (e.g., 'viking:// URIs are database paths: never pass them to local file tools or shell commands', 'A reinstall does not delete helper files the new version dropped'). This matches the 'lean and efficient; every token earns its place' anchor rather than the 'minor instances of over-explanation' anchor at 4.

Actionability

Nearly every step is a copy-paste-ready tool call or command: find(query=..., context_type="skill"), add_skill(data=...), the full zip command with exclusion flags, curl -sS -F "file=@/tmp/<name>.zip", ov skills add / validate / remove. It covers the common cases concretely, matching the fully-executable top anchor; it exceeds the anchor at 4 because there are no significant gaps.

Workflow Clarity

Every multi-step workflow (create, install, migrate) is numbered with explicit checkpoints: a name-collision read check before add_skill, 'show the user what would change and install only after they confirm', a dedicated Verify step (tree(uri=..., level_limit=1) should list every uploaded name), and ov skills validate to catch format errors first. Destructive and batch operations (delete, replace, account-wide share, migration upload) all carry explicit confirmation/validation, so the missing-validation cap does not apply; this matches the anchor with explicit validation steps and feedback loops.

Progressive Disclosure

The file is well-organized with clear section headers that make navigation easy, but it is a single ~180-line file with all content inlined — the migration classification rules, the zip/curl upload procedure, and install-from-repository guidance are each substantial enough that they could live in one-level-deep reference files. This matches 'good structure; most content is appropriately placed; minor organization gaps' (anchor 4) rather than anchor 5, which expects well-signaled references and appropriately split content, and the under-50-lines simple-skill exception does not apply.

Specificity

The description opens with seven concrete, specific actions ('Find, use, create, install, share, update, and migrate') anchored to concrete targets (viking://~/skills, viking://agent/skills, add_skill tool, helper files). This matches the anchor for multiple specific concrete actions with comprehensive coverage; it is not score 4 because there are no meaningful gaps in the action coverage.

Completeness

It explicitly answers both questions: the 'what' is stated up front (find/use/create/install/share/update/migrate skills stored in OpenViking) and an explicit 'Use it when...' clause lists multiple concrete trigger situations, including quoting exact phrases. This matches the anchor for clearly and explicitly answering both what AND when with concrete trigger phrases; score 4 would require the 'when' to be less explicit, which it is not.

Trigger Term Quality

It quotes literal user phrases users would naturally say — 'upload my skills', 'save this as a skill', plus multilingual variants ('迁移本地 skill', '把 skill 存到 OpenViking', '新建一个 skill') and concrete local paths (~/.claude/skills, ~/.agents/skills, ~/.cursor/skills). This is comprehensive natural-term coverage including synonyms, matching the top anchor rather than the 'a few natural terms missing' anchor at 4.

Distinctiveness Conflict Risk

The niche is clear — managing skills stored in OpenViking — and the viking:// trigger terms are distinct. However the trigger 'when a task looks like one a stored skill would cover' is broad and overlaps with the harness's own skill loading and closely related skills (e.g., openviking-memory), which is minor overlap risk with closely related skills (anchor 4) rather than minimal conflict risk (anchor 5).