From 63c7c4ae2c952cabc9dcd8344b1e6f588e0b81ae Mon Sep 17 00:00:00 2001 From: damocles Date: Sun, 30 Aug 2026 03:26:09 +0200 Subject: [PATCH] hive-c0re: drop stale 'question' example from check_size doc --- .../base/skills/choosing-a-comms-channel/SKILL.md | 14 ++++++++++---- hive-c0re/src/agent_config/limits.rs | 4 ++-- 2 files changed, 12 insertions(+), 6 deletions(-) diff --git a/claude-plugins/plugins/base/skills/choosing-a-comms-channel/SKILL.md b/claude-plugins/plugins/base/skills/choosing-a-comms-channel/SKILL.md index e0f512cb..6168c519 100644 --- a/claude-plugins/plugins/base/skills/choosing-a-comms-channel/SKILL.md +++ b/claude-plugins/plugins/base/skills/choosing-a-comms-channel/SKILL.md @@ -16,10 +16,16 @@ future reader won't think to look). dashboard-visible one-way message is fine. Don't reach for a conversational channel just to say something that needs no response. - **A specific decision you need recorded, that threads an answer back - to you** - use a mechanism built for exactly that (queues cleanly, - the answer comes back attached to the question). This matters for - anything you'll need to point back to later - a gated approval, a - go/no-go call. + to you** - there's no dedicated generic tool for this shape anymore + (a prior asker/answerer mechanism that did was removed). Use the + closest fit instead: if the decision is issue-shaped, it's really the + next bullet (post it where the context lives and it stays that + thread's own back-and-forth); otherwise use a real conversational + channel and write the outcome down somewhere a future reader will + actually find it - the channel itself won't do that bookkeeping for + you. This still matters for anything you'll need to point back to + later - a gated approval, a go/no-go call - it just takes one extra, + deliberate step now instead of a tool doing it automatically. - **An issue-shaped question or decision** - post it where the surrounding context already lives (the tracked item itself), not in a side channel. A future reader looking at that item should find the diff --git a/hive-c0re/src/agent_config/limits.rs b/hive-c0re/src/agent_config/limits.rs index ae2ad299..955d1074 100644 --- a/hive-c0re/src/agent_config/limits.rs +++ b/hive-c0re/src/agent_config/limits.rs @@ -26,8 +26,8 @@ pub const MESSAGE_MAX_BYTES: usize = 4096; /// `Response::Err`) on failure. /// /// `label` shows up in the error message verbatim — pass a short -/// noun like `"send"`, `"question"`, `"broadcast"` so the model can -/// tell which call got rejected. +/// noun like `"send"` or `"broadcast"` so the model can tell which +/// call got rejected. pub fn check_size(label: &str, body: &str) -> Result<(), String> { if body.len() > MESSAGE_MAX_BYTES { Err(format!(