Mostly efficient command examples, but padded with concept explanations Claude already knows ("Interactive rebase is the Swiss Army knife", "Binary search through commit history to find the commit that introduced a bug", "Your safety net - tracks all ref movements") and runs ~400 lines. Not score 3 because several one-liners restate common Git knowledge and the body could be tightened; not score 1 because it is not grossly verbose and avoids long library/background exposition.

Provides abundant concrete, executable git commands (e.g. `git rebase -i HEAD~5`, `git cherry-pick abc123..def456`, `git bisect run ./test.sh`) that are copy-paste ready. Not score 2 because examples are complete and runnable rather than pseudocode or vague direction.

Workflows are sequenced, but destructive/batch operations (rebase, `--force-with-lease`, `reset --hard`, multi-branch cherry-pick) lack inline validation checkpoints — safety guidance sits separately in Best Practices/Recovery rather than as validate-then-proceed steps. Not score 3 per the destructive-operations cap; not score 1 because sequences and abort/--continue feedback loops are present.

Clear section organization and a signaled Resources list, but the referenced bundle files (references/git-rebase-guide.md, assets/git-workflow-checklist.md, scripts/git-clean-branches.sh, etc.) do not exist in references/assets/scripts, and most detailed content is inline rather than split into those files. Not score 3 because references are dangling and content that should be separate is inline; not score 1 because references are one level deep and sections are well organized, not a monolithic wall.

Lists multiple concrete actions — "rebasing, cherry-picking, bisect, worktrees, and reflog" — matching the anchor for several specific concrete actions rather than vague language. Not score 2 because the actions are named concretely and comprehensively, not just a domain label.

Explicitly states what it does (master advanced Git workflows...) and when to use it via an explicit "Use when..." clause. Not score 2 because the when guidance is explicit, not merely implied.

The "Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues" clause covers natural phrases users would say. Not score 2 because it offers several relevant trigger variations rather than a single keyword.

The advanced-Git niche (rebase, cherry-pick, bisect, worktrees, reflog) is distinct with specific triggers unlikely to fire for unrelated skills. Not score 2 because the scope is tightly scoped to advanced Git history operations.