BC auto-logger
自动记录日常活动、对话摘要、重要事件到 memory 目录。支持定时记录、事件触发记录、每日总结。
自动记录日常活动、对话摘要、重要事件到 memory 目录。支持定时记录、事件触发记录、每日总结。
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
ProcedureSoftware developmentAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
How to improve
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Dangerous commands
cmd-execpolicy-bypassREADME.md:34Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)- 参数:`-ExecutionPolicy Bypass -File "C:\Users\24267\.openclaw\workspace\scripts\auto…ps1" -Action "daily_review"`
quoted -
low Dangerous commands
cmd-execpolicy-bypassREADME.md:41Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)openclaw cron add --name "hourly-log" --cron "0 * * * *" --command "powershell -ExecutionPolicy Bypass -File scripts\auto…ps1 -Action session_end"
quoted -
low Dangerous commands
cmd-execpolicy-bypassREADME.md:44Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)openclaw cron add --name "daily-review" --cron "0 23 * * *" --command "powershell -ExecutionPolicy Bypass -File scripts\auto…ps1 -Action daily_review"
quoted
Files scanned: 2. 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 53/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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 53 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 801 tokens
- 100Running it twice. No mutating operations
- low 11 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)
- +3Description length 49: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 36 headings
- +3Step-by-step instructions: 53 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.