BC session-log-analyzer
View and analyze session logs, generate PDF reports, and sync to Notion. Supports daily automated reporting via cron.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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.
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.
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
- 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.
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 2
-
high Dangerous commands
cmd-persistenceSKILL.md:63Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null; echo "0 2 * * * /root/.openclaw/workspace/tmux_scripts/daily-log-report.sh >> /root/.openclaw/workspace/pdfs/daily_report.log 2>&1") | crontab -
Medium and low: 1
-
low Dangerous commands
cmd-cron-mentionSKILL.md:63Mentions editing / listing crontab(crontab -l 2>/dev/null; echo "0 2 * * * /root/.openclaw/workspace/tmux_scripts/daily-log-report.sh >> /root/.openclaw/workspace/pdfs/daily_report.log 2>&1") | crontab -
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 51/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
- 40Consistency. Frontmatter name (session-log-analyzer) differs from the folder (terrycarter-session-log-analyzer)
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100Execution cost. Instruction body is 544 tokens
- 100Running it twice. No mutating operations
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 117: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 9 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.