Dont Deal Triage

生活服务

作者 shaoqing404版本 0.1.0来源 ClawHub

健康管理

322

下载量

安装量

收藏量

★ 5.0

评分

dont-deal-triage

This skill is for conservative, local-first support. It is not a diagnosis skill.

Workflow

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.
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
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.
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.
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.
Persist only local summaries. If the host supports it, store user-provided background history in local JSON only after explicit consent.
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.
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.
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:

json

{
  "urgency": "emergency | urgent | monitor",
  "reasoning_summary": [
    "Current symptoms",
    "Fatigue context",
    "Known risk factors"
  ],
  "recommended_action": "short imperative sentence",
  "follow_up_questions": []
}

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.

相关推荐

Weather

获取当前天气和预报（无需API密钥）

★ 453↓ 22.8万steipete

Sonoscli

控制Sonos音箱（发现/状态/播放/音量/分组）

★ 56↓ 8.5万steipete

Caldav Calendar

需配置 API Key

使用 vdirsyncer + khal 同步并查询 CalDAV 日历（iCloud、Google、Fastmail、Nextcloud 等）。适用于 Linux。

★ 243↓ 3.1万asleep123

healthcheck

使用 JSON 文件存储追踪饮水和睡眠

★ 11↓ 3万stellarhold170nt

Apple Reminders

通过 macOS 上的 `remindctl` CLI 管理 Apple 提醒事项（列出、添加、编辑、完成、删除），支持列表、日期筛选及 JSON/纯文本输出。

★ 54↓ 2.9万steipete

命理大师

全体系命理大师 — 八字四柱、紫微斗数、奇门遁甲、六爻、梅花易数、塔罗、星盘、数字命理、九宫飞星风水、掌纹面相、起名命名、穿衣搭配、合婚择吉一站式解读。本地档案、可选每日推送（默认关闭）、浏览器六爻界面与 HTML 报告。仅作文化参考，不替代医疗、法律、心理、财务、婚姻等专业建议；遇重大决策请咨询专业人士。

★ 62↓ 2.8万wscats

Workflow

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.

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

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.

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.

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.

Persist only local summaries. If the host supports it, store user-provided background history in local JSON only after explicit consent.

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.

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.

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.

{ "urgency": "emergency | urgent | monitor", "reasoning_summary": [ "Current symptoms", "Fatigue context", "Known risk factors" ], "recommended_action": "short imperative sentence", "follow_up_questions": [] }

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.