CF device-management
设备管理工具,用于管理摄像头、监控等实时设备,支持设备增删改查、实时画面查看、直播流地址获取。当用户提及摄像头、监控、设备管理、查看实时画面、直播流、监控地址等关键词时使用。
As a process F 28/100 · Will not run — References files that are not bundled: streamUrl, references/api_doc.md, assets/player_template.html
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 files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.
Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Obfuscation
obf-base64-blobSKILL.md:186Long base64-looking blobhttp://cmgw…888/LCO/BJ10…2E9/0/1/2026…842/open…3u8?source=open&id=…
-
medium Obfuscation
obf-base64-blobSKILL.md:251Long base64-looking blob| 2020005731198033922 | BJ10…2E9 | 大华摄像头1BD9 | 大华 | - | ✅ 在线 | [▶️ 查看实时画面](http://cmgw…888/LCO/BJ10…2E9/0/1/2026…842/open…816
-
medium Obfuscation
obf-base64-blobSKILL.md:261Long base64-looking blob播放地址:[▶️ 点击播放](http://cmgw…888/LCO/BJ10…2E9/0/1/2026…842/open…3u8?source=open&id=…)
-
low Secrets in code
secret-high-entropy-tokenscripts/config.py:38High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)DEFAULT__APP_ID_TANGE = "AD_3…cV4"
quoted
Files scanned: 33. 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") - warning
missing-refreference to a missing file: streamUrl - warning
missing-refreference to a missing file: references/api_doc.md - warning
missing-refreference to a missing file: assets/player_template.html
Process rating: all ten parameters 28/100
- 0Tools and files. 3 referenced file(s) missing: streamUrl, references/api_doc.md, assets/player_template.html
- 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
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (device-management) differs from the folder (smyx-device-management)
- 100Steps. 29 steps
- 100Execution cost. Instruction body is 2228 tokens
- low The response is described with custom markup (8 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)
- +3Description length 87: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -34 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 12 headings
- +3Step-by-step instructions: 29 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 54.