CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

web-monitor

Use this skill when the user wants to watch a webpage for changes, monitor a URL, detect content updates, or get notified when a site changes.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

90%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary lean, code-first skill body: fully executable snippets organized in a clear progression from a minimal check to a full monitoring loop, with concise diffing and notification coverage. The only gaps are the absence of validation/verification steps in the loop and minor opportunities to offload secondary content (notification channels, Playwright) into reference files.

DimensionReasoningScore

Conciseness

The body is code-first with zero padding — every section is a lean, self-contained snippet with no explanations of concepts Claude already knows (no library tutorials, no 'what is hashing' prose). Every token earns its place.

5 / 5

Actionability

All snippets are complete and executable: a stateful hash-based check, BeautifulSoup selector monitoring, unified diffing, Discord/Telegram/generic webhook notification, a full polling loop, and Playwright rendering for JS pages. Copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

Sections build logically from single check → targeted element → diffing → notification → full loop → JS pages, and the full loop includes per-URL try/except as an error checkpoint. Not a 5: no validation steps (e.g., confirming state persistence or notification delivery), and the batch URL loop's error path only prints rather than recovers.

4 / 5

Progressive Disclosure

The body is self-contained with well-organized sections and no broken or buried references (no bundle files exist, so nothing is misfiled). It misses 5 because at ~133 lines, content like the per-channel notification snippets and Playwright section could be split into reference files, and the quick-reference table duplicates section content.

4 / 5

Total

18

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A concise, natural-sounding description with an explicit 'Use when' clause and several distinct trigger phrases covering the monitoring niche well. Its main weakness is that the 'what' is folded into the trigger list, leaving the concrete capabilities (hashing, selectors, notification channels) unstated.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'watch a webpage for changes', 'monitor a URL', 'detect content updates', 'get notified when a site changes' — matching the anchor for several specific actions with minor coverage gaps. It falls short of 5 because it never states what the skill technically does (hashing, CSS selectors, notification channels).

4 / 5

Completeness

It has an explicit 'Use this skill when...' trigger clause and a serviceable 'what' embedded in those trigger phrases. Not a 5 because the 'what' is not stated as standalone capabilities (content hashing, diffing, webhook/Discord/Telegram/email alerts) the way the top anchor separates what from when.

4 / 5

Trigger Term Quality

Natural user phrasings like 'watch a webpage for changes' and 'get notified when a site changes' give good keyword coverage. A few common variations are missing ('website', 'check for updates', 'alert me', 'scrape'), so it does not reach comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Webpage change monitoring is a clear niche with distinct triggers ('watch a webpage', 'monitor a URL', 'detect content updates') and minimal overlap risk with adjacent skills like scheduling or scraping.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ProwlrBot/prowlr-marketplace

Path

skills/web-monitor/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.