BD yotta-logwatch
元察 —— 跨智能体的安全日志分析检测技能:零依赖自研解析 auth/secure、Web 访问日志(common/combined)、PowerShell 脚本块日志、Windows 事件日志(Security/System),检测爆破 / webshell / 扫描 / 异常登录 / 可疑脚本块 / 可疑进程 / 账户操作 / 日志清空,输出时间线与中文教学报告。触发:用户给出登录日志 / Web 访问日志 / PowerShell 日志 / Windows 事件日志,要分析入侵痕迹、排查异常活动、审计本地日志时。边界:只读本地日志文件;不联网、不主动扫描、不修改任何其内容;仅用于已获授权 / 自有资产的安全审计。
元察 —— 跨智能体的安全日志分析检测技能:零依赖自研解析 auth/secure、Web 访问日志(common/combined)、PowerShell 脚本块日志、Windows 事件日志(Security/System),检测爆破 / webshell / 扫描 / 异常登录 / 可疑脚本块 / 可疑进程…
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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
- 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 · 6
✓ No critical or high findings
Medium and low: 6
-
medium Dangerous commands
cmd-persistencereferences/windows-event-rules.md:64Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)| powershell / pwsh / cmd /c / wscript / cscript / schtasks /create / sc create | medium | 脚本宿主 / 持久化命令 |
security skill -
medium Dangerous commands
cmd-encoded-execscripts/test_yotta_logwatch.py:46Executes a base64/encoded payload (test fixture / example file; quoted — discussed, not commanded)'powershell -EncodedCommand SQBF…GoA')
fixturequoted -
medium Dangerous commands
cmd-persistencescripts/yotta_logwatch.py:120Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)"invoke-command", "register-scheduledtask", "set-content", "out-file",
code literal -
medium Dangerous commands
cmd-persistencescripts/yotta_logwatch.py:856Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)("schtasks /create", "计划任务创建(持久化)", "medium"),code literal -
low Secrets in code
secret-high-entropy-tokenscripts/test_yotta_logwatch.py:46High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)'powershell -EncodedCommand SQBF…GoA')
fixturequoted
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 16. 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 48/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
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 100Steps. 30 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1226 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)
- +3Output format is not stated: the model decides each time
- -31 of 2 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 313: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.