BC Cameras
Connect to security cameras, capture snapshots, and process video feeds with protocol support.
As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
ProcedureInfrastructureMedia and videotype and topics are labelled automatically from the skill text
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Exfiltration
net-credential-usesecurity-integration.md:39Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -H "Authorization: Bearer $HA_TOKEN" \
security skill -
low Exfiltration
net-credential-usesecurity-integration.md:46Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -H "Authorization: Bearer $HA_TOKEN" \
security skill -
low Exfiltration
net-credential-usesecurity-integration.md:91Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -H "Authorization: Bearer $TOKEN" \
security skill
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "changelog"
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
- 20When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 17 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 555 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)
- +3Description length 94: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 9 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.
External checks
ClawHub: suspicious
This camera skill appears purpose-aligned, but it handles sensitive camera images and includes examples that upload or fetch footage without enough privacy and transport-safety guardrails.
LLM: suspicious (medium) · VirusTotal: suspicious · 28 May 2026