feat(check): score fix, break, efficiency and speed in one block

kvb-check-efficiency measures a change against its base: tokens.py counts skill text tokens and listing words, measure.py runs one command in a base worktree and the working tree (one run per side, the mean of five over 100, an estimate marked ~ when other processes load the CPU). kvb-check-speed reads wall time from the same run and is not relevant for skills. kvb-check-score prints fix, break, efficiency, speed and the product score with emojis plus a gate line: below 90/5 it reports, over 100 it requires asking the operator before the commit.

Every skill that reported confidence and break risk now shows the score block; the 90/5 bar adds efficiency and speed at most 100. Commit blocks and the commit call's approval prompt name worktree, branch, diff stat and the score values, also for merges. 24 descriptions were shortened to keep the skill listing within its budget.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

skills/kvb-git-merge-fix/SKILL.md

@@ -1,8 +1,7 @@
 ---
 name: kvb-git-merge-fix
 description: >
-  Find the commits on any branch that carry a described fix and merge them
-  here. Trigger on a request to bring over a fix from another branch.
+  Find commits on any branch carrying a described fix and merge them here. Trigger on a request to bring over a fix from another branch.
 ---
 
 The free text after the skill name is the fix description and the only input.
@@ -59,6 +58,8 @@ and its diff plainly is the described fix.
 - One or a few commits, rest of the branch unwanted: `git cherry-pick -x <sha>…`
   (`-x` records the origin).
 - The whole branch is wanted: `git merge --no-ff <branch>`.
+- Every cherry-pick or merge call creates commits: it follows the
+  approval-prompt duty of `kvb-git-commit-no-verify`.
 - Conflicts: resolve them by reading both sides. Never `-X ours`/`-X theirs`,
   never `git checkout --ours/--theirs` wholesale: that silently drops one
   side's fix. Unresolvable → `git cherry-pick --abort` / `git merge --abort`,
@@ -67,7 +68,8 @@ and its diff plainly is the described fix.
 ## 7. Report
 
 Show `git log --oneline <base>..HEAD` and the resulting diffstat, then apply the
-kvb-check-confidence skill: what came over, what did not, what still has to be verified.
+kvb-check-confidence skill and its kvb-check-score block: what came over, what
+did not, what still has to be verified.
 Run the project's test or quality gate only when the operator asks for it.
 
 ## Rules