Conciseness

The body is lean and operational throughout — commands, a compact prefix table, preconditions, and a checklist — with no explanations of concepts Claude already knows. Even the force-push paragraph earns its place by explaining a non-obvious failure mode ("the lease is intact and the wrong branch gets rewritten"), matching anchor 5.

Actionability

Fully executable, copy-paste-ready commands in both recipes (`git fetch upstream --prune --tags`, `git switch -c <branch-name> upstream/main`, `gh pr checkout <NNNN>`, `git push --force-with-lease`) plus concrete verification commands and real example slugs like `fix/r8-animation-release` — anchor 5.

Workflow Clarity

Preconditions with verification commands (`git status --porcelain`, `git remote -v`), a numbered recipe with a sanity check, a rebase variant with explicit pre-push validation ("confirm this is the PR you meant, before any push"), conflict-resolution feedback, and a post-branch checklist. The destructive force-push is well guarded, so the cap does not apply — anchor 5.

Progressive Disclosure

Well-organized single-topic sections with one-level-deep, clearly signaled references (`.specify/memory/constitution.md`, `AGENTS.md`, `CLAUDE.md`), no bundle files needed. Minor gap: the 9-row prefix table duplicates the in-repo canonical list that constitution.md and CONTRIBUTING.md already carry, adding a fourth copy with drift risk — anchor 4 rather than 5.

Specificity

Names the domain (branching off fetched origin/main in Meshtastic-Android) and one composite action plus its outcome ("so the branch is based correctly and nothing is carried over"), but does not list several discrete actions — the fetch, rebase, and naming coverage in the body is absent. Matches anchor 3 (1-2 concrete actions, not comprehensive) rather than 4.

Completeness

Explicitly answers what ("The canonical recipe for starting a fresh working branch off a freshly fetched `origin/main` in Meshtastic-Android") and when ("Use this whenever a unit of work starts" followed by concrete quoted trigger phrases). Both are explicit with concrete triggers, matching anchor 5 rather than 4 where the 'when' would be less specific.

Trigger Term Quality

Quoted natural phrases "new branch off main", "peel off a fresh branch", "dust off #NNNN" plus "a unit of work starts" give good trigger coverage, but "rebase #NNNN" (a flow the skill explicitly covers) and plain "create a branch" variants are missing — a few natural terms short of anchor 5.

Distinctiveness Conflict Risk

Scoped to Meshtastic-Android branch bootstrap with distinctive triggers like "dust off #NNNN", giving a clear niche, but branch creation is a broadly applicable git operation with minor overlap risk against a generic branch/rebase skill — anchor 4 rather than 5.