AD web-monitor
Monitor web pages for changes, price drops, stock availability, and custom conditions. Use when a user asks to watch/track/monitor a URL, get notified about price changes, check if something is back in stock, or track any website for updates. Also handles listing, removing, checking, and reporting on existing monitors. v3 adds change summaries, visual diffs, price comparison, templates, JS rendering, and webhooks.
Monitor web pages for changes, price drops, stock availability, and custom conditions.
As a process D 39/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Exfiltration
exfil-webhook-urlSKILL.md:65Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)python3 scripts/monitor.py watch "https://example.com" --browser --webhook "https://hooks.slack.com/..."
placeholder -
low Exfiltration
exfil-webhook-urlSKILL.md:81Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)--webhook "https://hooks.slack.com/..."
placeholder -
low Exfiltration
exfil-webhook-urlSKILL.md:280Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)python3 scripts/monitor.py add "https://example.com" --webhook "https://hooks.slack.com/services/..."
placeholder
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 39/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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 10 mutating operations with no state check
- 40Consistency. Frontmatter name (web-monitor) differs from the folder (web-monitor-pro)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 50 steps
- 100Execution cost. Instruction body is 2658 tokens
- low 24 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
- +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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 417: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 50 items
- +4Has examples (27 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.