DC unifi-os
(no description)
Not recommendedlow grade D
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Exfiltration
net-credential-usescripts/firmware.sh:20Credential used in a network call (verify the destination is the intended service) (detector / deny-list definition)echo "${data}" | jq --arg k "${DEV_KEY}" '[.${k}[] | select(.upgrade_to_firmware != null and .upgrade_to_firmware != "") | {name,model,version,upgrade_to_firmware}]'detector -
low Exfiltration
net-credential-usescripts/firmware.sh:24Credential used in a network call (verify the destination is the intended service) (detector / deny-list definition)echo "${data}" | jq -r --arg k "${DEV_KEY}" '.[$k][] | "\(.name // .mac) | \(.model) | current:\(.version // "?") | \(if (.upgrade_to_firmware // "") != "" then "update→\(.upgrade_to_firmware)" else "detector -
low Exfiltration
net-credential-usescripts/firmware.sh:28Credential used in a network call (verify the destination is the intended service) (detector / deny-list definition)result=$(echo "${data}" | jq -r --arg k "${DEV_KEY}" '.[$k][] | select((.upgrade_to_firmware // "") != "") | "\(.name // .mac) | \(.model) | \(.version) → \(.upgrade_to_firmware)"')detector -
low Exfiltration
net-credential-usescripts/setup_test.sh:29Credential used in a network call (verify the destination is the intended service) (test fixture / example file)http_code=$(curl -so /dev/null -w "%{http_code}" -H "X-API-Key: ${UNIFI_API_KEY}" "${UNIFI_URL}/proxy/network/api/s/${UNIFI_SITE}/stat/health")fixture
Files scanned: 21. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 55/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
- 30When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1931 tokens
- 100Running it twice. Mutating operations check current state
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 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -33 of 18 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 22 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (16 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
This is a legitimate UniFi network-inspection skill, but it should be reviewed because it persists sensitive network data and has under-scoped local file handling.
LLM: suspicious (high) · 28 May 2026