Context Doctor
v1.0.0上下文诊断。随时检查当前会话的健康状态——context 使用率、token 消耗趋势、哪些工具调用最占空间、预估还能聊多少轮、给出优化建议。触发词：体检、诊断、context doctor、健康检查、token 用了多少、还能聊多久、会话状态。
⭐ 0· 80·0 current·0 all-time
by@wavmson
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (context health diagnostics) match the SKILL.md: it only needs session metadata and conversation/tool-output statistics. No unrelated credentials, binaries, or install artifacts are requested.
Instruction Scope
Instructions rely on a platform-provided session_status API and access to conversation history and tool-output metadata (exec/read/web_fetch results). That is appropriate for a context-diagnostic skill, but it does require the agent to be allowed to read session metadata and summaries of tool outputs; the SKILL.md states it will not include conversation content in reports.
Install Mechanism
Instruction-only skill with no install spec or code files — lowest install risk. README mentions cloning from GitHub as an installation option; since no install script or binary is executed by the skill itself, this is informational only. If you clone from the repo, validate the GitHub source first.
Credentials
No environment variables, credentials, or config paths are requested. The data the skill wants (token counts, tool call counts, tool output sizes) are proportional to diagnostics and consistent with its stated purpose.
Persistence & Privilege
always is false and the skill does not request persistent elevated privileges or modify other skills. The README mentions optional periodic checks via HEARTBEAT.md, but the skill itself does not auto-run or auto-compact; execution remains user/agent-controlled.
Assessment
This skill appears coherent and low-risk for its stated role, but before installing or enabling it: 1) confirm your platform exposes a session_status or equivalent API and that you consent to the agent reading session/tool metadata (token counts, tool output sizes, file read counts). 2) The skill may need access to tool-output metadata and file-read events (not raw conversation text) — ensure that this level of access is acceptable for your privacy needs. 3) The README suggests cloning from GitHub; if you follow that route, verify the repository origin and review its files. 4) If you integrate with companion skills (Smart Compact, Session Resume), ensure those skills are trusted so diagnostic recommendations do not cause unexpected automated actions. Overall, the skill is internally consistent — treat it as a diagnostics helper that requires access to session metadata, not as a networked or credential-hungry component.Like a lobster shell, security has layers — review code before you run it.
latestvk971vvtnkngsgv6445sz437rzs8409vh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.