dont-deal-triage
This skill is for conservative, local-first support. It is not a diagnosis skill.
Workflow
- 1. Gather local context before reasoning.
This skill package is self-contained.
From the skill folder, run
node scripts/index.js to generate the latest local snapshot.
If command execution is unavailable, read
~/.dont-deal/snapshot.json if it already exists.
- 2. In quick mode, solve only the red vs yellow question.
Read
references/quick-mode.md.
The core output is:
red = emergency help now
yellow = urgent medical review today
- 3. Check for immediate red flags before asking many questions.
Read
references/emergency-thresholds.md.
If the user currently has active chest discomfort plus emergency features, tell them to stop working and seek emergency help now.
- 4. Use fatigue data as context, not proof.
Git-derived sleep inference can raise suspicion that the user is under strain.
It cannot rule heart risk in or out.
- 5. Keep the conversation short and action-oriented.
If the user is symptomatic right now, prefer one question at a time.
Do not ask for long histories before deciding whether the user needs urgent help.
- 6. Persist only local summaries.
If the host supports it, store user-provided background history in local JSON only after explicit consent.
- 7. Keep machine inspection narrow.
Detect only the current host context.
Read only the active repository's git timestamps.
Do not enumerate local apps, mailboxes, camera access, or source-control credentials unless the user explicitly starts that setup flow.
- 8. Treat bystander use as valid.
The user may be asking for someone else.
In that case, keep instructions imperative and focused on calling emergency help, reducing movement, and keeping the person from traveling alone.
- 9. Prefer the bundled scripts over ad hoc reimplementation.
Use
scripts/quick-triage-cli.js for local fast-mode testing.
Use
scripts/index.js for the local fatigue and host snapshot.
Response rules
- - Never reassure the user that symptoms are "just stress" or "probably not serious."
- Never tell the user to drive themselves to the hospital when emergency symptoms are active.
- Tell the user to reduce activity immediately if chest pain is ongoing.
- If emergency care is indicated, stop discussing code or work until the user confirms they are safe.
- Treat git activity as a weak fatigue signal, not evidence about the user's exact sleep duration.
- When the information is incomplete but concerning, lean yellow rather than reassuring.
- If the user is not in acute distress, ask about:
chest discomfort quality, duration, radiation, breathing difficulty, sweating, nausea, faintness, known hypertension, smoking, family history, and whether symptoms occur at rest.
Output shape
When the host can return structure, prefer:
CODEBLOCK0
Host portability
Keep this skill prompt generic:
- - Claude Code can wire this through its own skill surface.
- Codex can invoke the local analyzer directly.
- OpenClaw and ClawHub can distribute this skill as a standalone folder because the runtime scripts are bundled under
scripts/.
Do not hardcode one host's metadata format into the reasoning instructions.
dont-deal-triage
此技能用于保守的、本地优先的支持。它并非诊断技能。
工作流程
- 1. 在推理之前收集本地上下文。
此技能包是自包含的。
从技能文件夹运行 node scripts/index.js 以生成最新的本地快照。
如果命令执行不可用，则读取 ~/.dont-deal/snapshot.json（如果已存在）。
- 2. 在快速模式下，仅解决红色与黄色问题。
阅读 references/quick-mode.md。
核心输出为：
红色 = 立即寻求紧急救助
黄色 = 今日需紧急就医复查
- 3. 在提出大量问题之前，先检查即时红色警报。
阅读 references/emergency-thresholds.md。
如果用户当前有活动性胸部不适并伴有紧急特征，告知其停止工作并立即寻求紧急救助。
- 4. 将疲劳数据作为上下文参考，而非确凿证据。
基于Git的睡眠推断可能引发用户处于压力状态的怀疑。
它不能排除或确认心脏风险。
- 5. 保持对话简短且以行动为导向。
如果用户当前有症状，优先一次只问一个问题。
在决定用户是否需要紧急帮助之前，不要询问冗长的病史。
- 6. 仅持久化本地摘要。
如果主机支持，仅在获得明确同意后将用户提供的背景历史存储到本地JSON中。
- 7. 保持机器检查范围狭窄。
仅检测当前主机上下文。
仅读取活跃仓库的Git时间戳。
除非用户明确启动设置流程，否则不要枚举本地应用、邮箱、摄像头访问或源代码控制凭据。
- 8. 将旁观者使用视为有效。
用户可能是在为他人询问。
在这种情况下，保持指令命令式，专注于呼叫紧急救助、减少移动以及防止该人独自出行。
- 9. 优先使用捆绑脚本而非临时重新实现。
使用 scripts/quick-triage-cli.js 进行本地快速模式测试。
使用 scripts/index.js 获取本地疲劳和主机快照。
响应规则
- - 切勿安抚用户说症状“只是压力”或“可能不严重”。
- 当紧急症状活跃时，切勿告诉用户自己开车去医院。
- 如果胸痛持续，立即告知用户减少活动。
- 如果指示需要紧急护理，停止讨论代码或工作，直到用户确认其安全。
- 将Git活动视为微弱的疲劳信号，而非用户确切睡眠时间的证据。
- 当信息不完整但令人担忧时，倾向于黄色而非安抚。
- 如果用户未处于急性痛苦中，询问以下内容：
胸部不适的性质、持续时间、放射范围、呼吸困难、出汗、恶心、头晕、已知高血压、吸烟史、家族史以及症状是否在休息时出现。
输出格式
当主机可以返回结构化数据时，优先使用：
json
{
urgency: emergency | urgent | monitor,
reasoning_summary: [
当前症状,
疲劳上下文,
已知风险因素
],
recommended_action: 简短命令式语句,
followupquestions: []
}
主机可移植性
保持此技能提示通用：
- - Claude Code 可通过其自身的技能界面连接此功能。
- Codex 可直接调用本地分析器。
- OpenClaw 和 ClawHub 可将此技能作为独立文件夹分发，因为运行时脚本已捆绑在 scripts/ 下。
不要将某一主机的元数据格式硬编码到推理指令中。
