DC bsession-tool-pro
浏览器会话助手专业版是面向企业级场景的完整浏览器会话管理工具。在免费版单次抓取能力之上，新增定时任务（recurring）、会话持久化、Webhook通知、批量会话管理、企业级监控告警、Cloudflare自动规避、会话调试增强七大高级能力。Use。Use when 需要项目管理、任务规划、进度跟踪、团队协作时使用。不适用于实际人员绩效评估。 功能涵盖: bsession。
浏览器会话助手专业版是面向企业级场景的完整浏览器会话管理工具。在免费版单次抓取能力之上，新增定时任务（recurring）、会话持久化、Webhook通知、批量会话管理、企业级监控告警、Cloudflare自动规避、会话调试增强七大高级能力。Use。Use when…
As a process C 53/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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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 Exfiltration
exfil-webhook-urlSKILL.md:247Webhook / callback URL commonly used for exfiltration (verify the destination)webhook: https://hooks.slack.com/services/未指定
-
high Exfiltration
exfil-webhook-urlSKILL.md:261Webhook / callback URL commonly used for exfiltration (verify the destination)url: https://hooks.slack.com/services/未指定
Medium and low: 4
-
medium Exfiltration
exfil-webhook-urlreferences/detail.md:185Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)notifier.register("slack-alerts", "https://hooks.slack.com/services/xxx", "slack")quoted -
medium Exfiltration
exfil-webhook-urlreferences/detail.md:273Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)webhook_url="https://hooks.slack.com/services/xxx"
quoted -
medium Exfiltration
exfil-webhook-urlSKILL.md:139Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)monitor.notifier.register("slack-alerts", "https://hooks.slack.com/services/未指定", "slack")quoted -
medium Exfiltration
exfil-webhook-urlSKILL.md:154Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)webhook_url="https://hooks.slack.com/services/未指定"
quoted
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: All mapping items must start at the same column at line 10, column 1: description: "浏览器会话助手专业版是面向企业级场景的完整浏览器会话管理工具。在免费版单次抓取能力之上，新增定时任务（recurring）、会话持… when 需要项目管理、任务规划、进度跟踪、团队协作时使用。不适用于实际人员绩效评估. ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-long-hermesdescription is 188 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "edition" - note
frontmatter-keyunknown frontmatter key "tools"
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. Tools declared in frontmatter
- 100Steps. 36 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2813 tokens
- 100Running it twice. No mutating operations
- low 17 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
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
- +2Single-language instructions
- +3Description length 188: enough signal without eating the budget
- +4Structure: 45 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.