Conciseness

The body is lean and purely instructional ("Use `weave preview BRANCH`, replacing BRANCH with the shell-quoted requested ref") with every sentence directing action, but the time-sensitive pin "(tested with 0.5.4)" is the one trims-worthy instance per the version-number guideline, holding it at "minor instances of over-explanation" (anchor 4) rather than anchor 5.

Actionability

Commands are concrete and executable as written — `weave --version`, `weave preview BRANCH`, and `weave preview BRANCH --file path/to/file` — with explicit placeholder-substitution guidance and both the whole-branch and single-file cases covered; not 4 because there is no material gap in the common cases.

Workflow Clarity

The sequence is clear and ordered (confirm the tool via `weave --version`, identify the ref, check working-tree status, preview, then "Report the conflicts or independent entity changes the preview actually shows") with an explicit error-recovery path ("If absent, explain the prerequisite"); the skill is explicitly read-only, so the destructive-operation validation cap does not apply.

Progressive Disclosure

At ~25 lines with no external references needed and no bundle files present, the single well-organized flow satisfies the simple-skill exception: nothing is inlined that belongs in a separate file, and there are no nested or buried references.

Specificity

It names the domain and one concrete action — "Preview how a named branch would merge into HEAD using the locally installed Weave CLI, without applying the merge" — but offers no second capability (e.g., reporting conflicts or per-file previews), fitting the "1-2 concrete actions, but not comprehensive" anchor rather than anchor 4's "several specific actions".

Completeness

It explicitly answers both what ("Preview how a named branch would merge into HEAD using the locally installed Weave CLI, without applying the merge") and when ("Use when reviewing overlapping branch or parallel-agent changes") with a concrete trigger phrase, matching anchor 5; not 4 because the "when" clause is explicit and specific, not merely present.

Trigger Term Quality

Natural terms are present ("preview", "merge", "branch", "HEAD", "overlapping branch or parallel-agent changes"), but the phrase users most commonly say for this need — "merge conflicts" — is absent, leaving "a few natural terms missing" (anchor 4) rather than anchor 5's comprehensive synonym coverage; not 3 because core keyword coverage is solid.

Distinctiveness Conflict Risk

The Weave-specific, read-only framing ("without applying the merge") carves a mostly distinct niche, but the trigger "reviewing overlapping branch or parallel-agent changes" could also fire review-type skills, giving "minor overlap risk with closely related skills" (anchor 4) rather than anchor 5's minimal conflict risk.