SKILLEMALL.ai

CD kindle-claude-monitor

把闲置 Kindle / 旧手机 / 任意空闲屏幕变成 Claude Code 的状态监视屏。用户说「把 Kindle 变成 Claude Code 状态屏」/「Claude Code 状态监视屏 / monitor / 仪表盘」/「让 Claude 等确认时通知我」/「多 session 监控」/`/kindle-claude-monitor` 时触发。本机 Python HTTP server 接收 hooks 事件,渲染 e-ink 友好的纯黑白仪表盘——「思考中 / 执行中 / 请确认 / 已完成」一眼可见。多 session 下 waiting 状态有粘性锁。

Not recommendedcritical or high security findings
ClawHub Agent Skills author: heavenchenggong v0.1.1 MIT-0 7 files · 3 scripts body ≈ 894 tokens Open the sourceclawhub.ai analyzed 2 d ago

把闲置 Kindle / 旧手机 / 任意空闲屏幕变成 Claude Code 的状态监视屏。用户说「把 Kindle 变成 Claude Code 状态屏」/「Claude Code 状态监视屏 / monitor / 仪表盘」/「让 Claude 等确认时通知我」/「多 session…

As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
C
64/100
safety, quality, tests
Safety 60%
57
Quality 40%
75
Run on models
none yet
Process rating
D
45/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • 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 · 6

  • high Dangerous commands cmd-persistence install.sh:48
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load "$PLIST_DST"
Medium and low: 5
  • medium Dangerous commands cmd-persistence README.md:35
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    2. 渲染并装 launchd plist 到 `~/Library/LaunchAgents/com.user.kindle-monitor.plist`
    quoted
  • medium Dangerous commands cmd-persistence README.md:106
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    改值后改 `~/Library/LaunchAgents/com.user.kindle-monitor.plist` 的 `EnvironmentVariables` 块,再 `launchctl unload && load` 一次。
    quoted
  • medium Dangerous commands cmd-persistence SKILL.md:84
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    - 把 launchd plist 写到 `~/Library/LaunchAgents/` 并启动
    quoted
  • medium Dangerous commands cmd-persistence SKILL.md:113
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)
    改了之后改 plist 里的 EnvironmentVariables 块,然后 `launchctl unload && launchctl load` 一次。
    quoted
  • medium Dangerous commands cmd-persistence uninstall.sh:9
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)
    PLIST_DST="$HOME/Library/LaunchAgents/com.user.kindle-monitor.plist"
    code literal

Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 45/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
  • 30Running it twice. 1 mutating operations with no state check
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Steps. 19 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 894 tokens
  • 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

  • +5Description has no quoted example phrases that should trigger the skill
  • +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
  • +3Description length 288: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 19 items
  • +4Has examples (3 code blocks)
  • +3All 2 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.

External checks

ClawHub: suspicious
This skill is a coherent local Claude Code monitor, but it exposes Claude workflow data on the local network and installs persistent hooks without strong user controls.
LLM: suspicious (high) · VirusTotal: · 13 Jun 2026