AC workbuddy-skill-session-callback
【仅限 WorkBuddy 桌面版使用】会话回调（Session Callback）——实现"一个会话调起另一个会话"的能力：外部进程、定时任务（cron job）或另一个 agent 会话，向目标会话注入消息，唤醒其 agent 带完整上下文继续处理。适用于 WorkBuddy 桌面版：监控回传后唤醒主会话推进任务、定时任务回调指定会话、异步任务完成后通知会话、多会话协作接力、替代 openclaw 的 sessions_send 机制。当用户在 WorkBuddy 中提到"会话回调"、"唤醒会话"、"session callback"、"会话调起另一个会话"、"cron 唤醒指定会话"、"向会话注入消息"、"主会话收到提醒后推进"、"sessions_send" 时使用本 skill。注意：本技能依赖 WorkBuddy 本地结构（~/.workbuddy/sessions/、projects/*.jsonl、/api/v1/acp/*），不适用于 openclaw 等其他平台。
【仅限 WorkBuddy 桌面版使用】会话回调（Session Callback）——实现"一个会话调起另一个会话"的能力：外部进程、定时任务（cron job）或另一个 agent 会话，向目标会话注入消息，唤醒其 agent 带完整上下文继续处理。适用于 WorkBuddy…
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 36 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1335 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 12 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 448: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.