Conciseness

The body is extremely dense with no padding and no explanation of concepts Claude already knows ("Preserve typed failures and do not turn a failed read into an empty rules result"), fitting anchor 4. Not 5 because time-sensitive version pins ("2.0.0 or newer", "--skill-version 1.1.7") are embedded in the main body rather than isolated, and long edge-case passages (update notices, sandbox auth diagnostic) could be trimmed or offloaded.

Actionability

Copy-paste-ready commands appear in Quick start ("qodo read rules search --query ... --top-k 20 --scopes ... --json") with a worked JWT query example, a fallback invocation ("${QODO_HOME:-$HOME/.qodo}/bin/qodo"), a concrete three-line query template, and a severity enforcement table — fully executable guidance covering the common CLI cases, matching anchor 5.

Workflow Clarity

A master sequence is stated ("preserve update notices, verify the current tool contract, build focused semantic queries, merge ranked results, explain the applicable constraints, then apply them") with explicit validation gates (unadorned "<qodo> --version" probe, post-update re-probe, "Check isError", one bounded catalog refresh) and explicit feedback loops (low-return fallback re-run, rate-limit wait, "An empty merged list is a valid outcome"), matching anchor 5.

Progressive Disclosure

Three real one-level-deep references exist in the bundle and are condition-signaled ("read [shell guidance](references/windows-shells.md) before the first call; [launcher recovery](references/windows-launcher.md) only if invocation fails"), fitting anchor 4. Not 5 because the main body is heavier than an overview — update-notice policy, the sandbox auth diagnostic, and Git Bash caveats are inlined where they could live in the references directory.

Specificity

"Retrieve and apply Qodo coding rules" plus "Reuse rules already retrieved for the same workspace, repository, and task scope; refresh when that scope changes" names the domain and several concrete actions with explicit scope semantics, matching anchor 4. Not 5 because "apply" is never expanded into what application concretely involves; not 3 because coverage goes beyond 1-2 actions.

Completeness

Both what ("Retrieve and apply Qodo coding rules relevant to implementation, planning, refactoring, or code review") and when ("Use on 'get rules', 'load qodo rules', or 'relevant standards' and when starting a concrete coding task") are explicitly stated with concrete trigger phrases, matching anchor 5. It is not 4 because the when-clause is fully explicit, not merely present.

Trigger Term Quality

"Use on 'get rules', 'load qodo rules', or 'relevant standards' and when starting a concrete coding task" provides good natural keyword coverage with concrete quoted phrases. Not 5 because common variations like "coding standards", "fetch rules", or "team conventions" are missing; not 3 because the included terms are natural and well-chosen.

Distinctiveness Conflict Risk

"Qodo" branding carves a mostly distinct niche with dedicated triggers ("load qodo rules"), matching anchor 4. Not 5 because the generic phrases "get rules" and "relevant standards" could overlap with other coding-standards skills; not 3 because the Qodo anchor keeps conflict risk minor.