AF session-monitor
Real-time OpenClaw session monitor that tails JSONL transcripts and pushes formatted updates to Telegram as a persistent background process. Use when asked to monitor, watch, observe, track, spy on, or tail agent sessions, set up a live feed or dashboard of agent activity, deploy a background monitor with Telegram push notifications, or restart/stop/check the monitor. Triggers: monitor sessions, watch agent, start monitor, restart monitor, stop monitor, monitor status, session dashboard, live feed, tail sessions, what is the agent doing, observe agent, track activity, spy on agent, background monitor, push notifications, 监控session, 监控agent, 盯着agent, 看看agent在干嘛, 实时监控, 后台监控, 订阅session, agent活动推送, 重启监控, 停止监控, 监控状态. NOT for one-shot session inspection (use built-in sessions_list / sessions_history for that).
As a process F 38/100 · Will not run — References files that are not bundled: scripts/.pid
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
read-dotenvSKILL.md:23Reads a .env filecp scripts/.env.example scripts/.env
Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/.pid
Process rating: all ten parameters 38/100
- 0Tools and files. 1 referenced file(s) missing: scripts/.pid
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (session-monitor) differs from the folder (openclaw-session-monitor)
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 14 steps
- 100Execution cost. Instruction body is 1132 tokens
- 100Progress reporting. Reports progress
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
- +3Description length 815: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -216 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 10 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (5 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 7 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.