BC s2-universal-scanner
S2-SP-OS Universal Spatial Sensor Sniffer. Scans LAN for S2-Native Zero-Knowledge Heartbeats (6D-VTM extraction), legacy sensors (Modbus, MQTT), and cross-verifies sleeping nodes via Gateway APIs. / S2 万能空间传感器探测器。首发支持 S2 原生零知识心跳与 6D-VTM 提取,向下兼容传统物联网嗅探。
As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokens2-universal-scanner-AGENT-EXAMPLES.md:43High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)"raw_fingerprint": "GH-5…ion",
fixturequoted -
low Secrets in code
secret-high-entropy-tokenuniversal_scanner.py:74High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"raw_fingerprint": "GH-5…ion",
quoted
Files scanned: 4. 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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 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
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 324 tokens
- 100Running it twice. No mutating operations
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 252: enough signal without eating the budget
- +4Structure: 3 headings
- +3Step-by-step instructions: 4 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.
External checks
ClawHub: suspicious
This looks more like a mock scanner than a trustworthy discovery tool, and it could mislead users or agents into acting on fake device inventory.
LLM: suspicious (high) · VirusTotal: · 29 May 2026