refactor(skills): cap every SKILL.md at 600 words and cut agent messages

Every loaded SKILL.md and every listed description is paid on every turn of every session, and every delivered message costs its recipient a full turn. scripts/budget.py gains SKILL_WORDS = 600, enforced by test_lock, and test_naming forbids a skill naming its own slash command; 53 descriptions and 10 body lines drop it. The 18 longest skills move details into 31 side files read only in their situation (organize's capacity, succession, peers, offices, relay and lineage; cleanup's docker, worktrees, execute and ask; code-tune, changelog, triage, dream, split and others), so all SKILL.md files shrink from 33866 to 26291 words without dropping a rule; an independent review of HEAD against the new text found no loss in 60 of 64 skills and three weakenings, now restored (WSJF re-estimates after an objective change, cleanup's volume checklist, essence's absolute dates).

The kvb-org-organize Peer protocol sends status that asks nothing to the news board, answers nothing that asks nothing, keeps messages terse, and lets light runs admit themselves in the operator's wording; the skills follow it (operator reads the register, relax and wakeup reply through the news, evening collects them there, wsjf asks only for missing estimates, cleanup and triage batch their questions). Skills that explore code ask the codebase-memory-mcp graph first, subagent briefs scale with the stakes and cap their answers, and the skills that need the full register or council tables call show --wide or list --long.

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

skills/kvb-org-priority/SKILL.md

@@ -2,8 +2,7 @@
 name: kvb-org-priority
 description: >
   Let the operator reorder the agents' priority from a selection; pins their
-  tasks in that order. Trigger on /kvb-org-priority, "prioritaet", "reihenfolge
-  der agents".
+  tasks in that order. Trigger on "prioritaet", "reihenfolge der agents".
 ---
 
 The operator's order of the agents outranks every WSJF score. It is written
@@ -20,7 +19,7 @@ rasci.py order "<agent>,<agent>,..."
 
 `rasci.py agents` prints one line per agent with open tasks, in the
 register's rank: number, agent, task count, tasks. Show it as a table with
-each agent's status and OKR from `rasci.py show`.
+each agent's status and OKR from `rasci.py show --wide`.
 
 ## Step 2: selection
 
@@ -42,9 +41,10 @@ the listed ones; say so in the question.
 `rasci.py order "<A>,<B>,..."` pins the listed agents' tasks 1..n in that
 order, keeping each agent's own task order. It writes other sessions' rows:
 the operator decides priority, so this is the one exception to "write only
-your own rows". Show `rasci.py agents` again, then tell the resource chair
-of the `kvb-org-organize` skill and every reordered agent their new rank, one
-message each.
+your own rows". Show `rasci.py agents` again, then post the new ranks for the
+resource chair of the `kvb-org-organize` skill and every reordered agent as
+one `${CLAUDE_SKILL_DIR}/../kvb-org-organize/scripts/news.py post "<text>"`,
+not as messages.
 
 ## Rules