Conciseness

The body is dense and almost entirely non-obvious CLI-specific contract (exit-code semantics, typed error codes, batch envelope shapes) with essentially no filler Claude would already know. It misses the 5 anchor because of small redundancies — the `auth token` raw-token exception is stated in §1 and repeated as an exception in §3, and the exit-10 approval rule is restated in §7a — but is well above the 3 anchor's 'some unnecessary explanation'.

Actionability

Every section is copy-paste ready: concrete command lines ("weknora profile add prod --host https://kb.example.com --use", "echo \"$WEKNORA_API_KEY\" | weknora auth login --with-token"), an exit-code table with per-code agent actions, a realistic JSON error envelope, and a working chaining example (KB=$(weknora kb create ... --jq '.data.id')). This matches the fully-executable anchor.

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints: the auth section marks order as 'do this first — order matters', verifies with `auth status`, uses `kb status`/`kb check` for `retrieval_ready`, prescribes `--dry-run` before mutations, and defines exit-code-driven recovery (re-auth on exit 3, backoff on 6/7, user approval on exit 10) plus batch failure inspection. Destructive and batch operations all have feedback loops, satisfying the cap.

Progressive Disclosure

With no bundle files present, the single-file organization is strong: numbered, well-labeled sections (auth, KB selection, output contract, exit codes, destructive writes, chaining, command map, self-help) plus a 'Common mistakes' table make navigation easy, and the one deep-dive (chat vs session ask vs search) is deliberately offloaded to a sibling skill. It falls short of 5 because the pointer targets `weknora-rag-search` outside this bundle, so the decision table is not actually reachable from what ships here, and some detail (e.g., the full per-resource command map) is inline rather than split out.

Specificity

The description enumerates multiple concrete capability areas — "authenticating, managing knowledge bases / documents / sessions / agents, running search or chat, or interpreting the CLI's JSON envelopes and exit codes" — each tied to specific actions on a named tool. It sits firmly at the comprehensive anchor rather than 4, since the action list covers the CLI's full surface with no significant gaps.

Completeness

It opens with an explicit trigger clause — "Use when driving a WeKnora RAG server through the `weknora` CLI as an agent" — and pairs it with a clear statement of what the skill covers, plus ordering guidance ("Read this before any other weknora-* skill"). Both what and when are explicit with concrete trigger phrases, matching the 5 anchor exactly.

Trigger Term Quality

Natural trigger phrases are present and varied: "WeKnora RAG server", "weknora CLI", "knowledge bases", "documents", "sessions", "search or chat", "authenticating". It falls short of the 5 anchor because common user phrasings like "upload", "retrieval", "query", or product-file synonyms are absent, though coverage is well beyond the 3 anchor's 'some relevant keywords'.

Distinctiveness Conflict Risk

The niche is unambiguous: it is scoped to the named WeKnora product and its `weknora` CLI, and explicitly positions itself as the base for the `weknora-*` family. Product- and tool-specific triggers make conflict with unrelated skills minimal, matching the clear-niche anchor.