AC sentry-mode
Webcam surveillance with AI analysis. Two modes: (1) One-shot analysis - answer specific questions about your space, (2) BOLO watch mode - continuous monitoring with motion detection and custom watchlists for people/objects. Use cases: "Is anyone in the room?", "What's on my desk?", or keep watch for "guy with black hat", "little blond girl", etc. Motion-triggered alerts with 3-min cooldown.
Webcam surveillance with AI analysis.
As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
The same skill appears in 2 more places: skill-library-mcp, skill-library-mcp
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 14. 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: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Webcam surveillance with AI analysis. Two modes: (1) One-shot anal… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 57/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (sentry-mode) differs from the folder (sentry-mode-skill)
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 89 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 1439 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
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
- +4Description does not say when NOT to use the skill (false activations)
- -35 of 6 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 394: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 89 items
- +3Output format is stated explicitly
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.