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>
1.3 KiB
1.3 KiB
name, description
| name | description |
|---|---|
| kvb-org-artefacts | Artifacts of the kvb-org-rasci register per task: images, volumes, worktrees. Trigger on "artefakte". |
Artifacts live in the task table of the kvb-org-rasci register: each
belongs to exactly one task, carries its kind, reference and recording time,
and takes status and worker from its task. The script is
${CLAUDE_SKILL_DIR}/../kvb-org-rasci/scripts/rasci.py.
rasci.py set <task> --artifact <kind>:<ref>
rasci.py set <task> --drop-artifact <kind>:<ref>
rasci.py artifacts [--ended] [--task <task>]
Kinds: image:, container:, volume:, network:, stack:, worktree:,
dir:, log:. artifacts lists each task's workdir and branch beside them.
Rules
- Record an artifact the moment it exists, under the task that created it; an unrecorded one is invisible to cleanup.
artifacts --endedlists what belongs todone,stoppedorstaletasks: the cleanup candidates, owned by the task's worker. Everything of an open task stays. Read an artifact's owner here instead of asking peers.- Deleting goes through the
kvb-cleanupskill, where the operator picks; drop the artifact here once it is gone. - The register's
show --widecounts each task's artifacts in its Artifacts column.