CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wigolo-watch

Monitor a page for changes over time. Create lazy watch jobs on one or many URLs, list them, and check for changes on demand — with optional SSRF-guarded webhook delivery when a change is detected. Use when the user says "monitor this page", "watch this URL for changes", "tell me when this updates", "track this changelog", "notify me if this changes", or wants recurring change detection on web content.

Quality

90%

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

87%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.

A tight, highly actionable skill body: executable examples for every action, a precise parameter table, useful anti-patterns, and explicit 'when NOT to use' boundaries. The one real weakness is the absence of validation/verification guidance for its batch-create and delete operations, which caps workflow clarity per the rubric.

Suggestions

Add a verification step after batch create — e.g., 'confirm the returned `jobs[]` count matches the number of `urls` submitted' — so batch operations have an explicit checkpoint.

Document the `check` response shape (changed/unchanged fields and what a reported diff looks like) so callers can act on results without trial and error.

Add brief error-recovery guidance for failed checks (e.g., fetch failure or invalid `selector`) — a validate-and-retry loop for the fragile parts of the check workflow.

DimensionReasoningScore

Conciseness

The ~72-line body is lean with no filler: the only explanatory prose ("there is no background daemon" for the lazy model, one sentence on SSRF guarding) is tool-specific and necessary, and every section (Quick Reference, Parameters, How It Works, Anti-Patterns, When NOT to use, See Also) earns its tokens.

5 / 5

Actionability

The Quick Reference gives complete, copy-paste-ready JSON payloads covering all seven actions, and the parameter table adds types, defaults, mutual exclusivity ("Mutually exclusive with `urls`"), and return shapes ("Batch create returns `jobs[]` only") — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

"How It Works" lays out a clear create → check → manage sequence with per-action semantics, but the skill includes batch operations (`urls[]` batch create) and a destructive action (`delete`) with no validation or verification steps (e.g., confirming the `jobs[]` count matches the input URLs, or confirming deletion) — the rubric's explicit cap for batch/destructive skills without validation applies, overriding the simple-skill exception. It stays at 3 rather than 2 because the sequence itself is coherent and unambiguous.

3 / 5

Progressive Disclosure

The body is well-organized into clearly headed sections with nothing inlined that belongs in a separate file at this size, and the "See Also" cross-links to sibling skills (wigolo-diff, wigolo-cache, wigolo-fetch) are one level deep and clearly signaled with one-line descriptions — easy to navigate, no bundle files are needed or referenced.

5 / 5

Total

18

/

20

Passed

Description

91%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 strong description: concrete capabilities in third person, an explicit 'Use when' clause with abundant natural trigger phrases, and a clearly scoped niche. The only gaps are the unmentioned pause/resume/delete management actions and slight overlap risk with sibling one-shot comparison skills.

DimensionReasoningScore

Specificity

Lists several concrete third-person actions — "Create lazy watch jobs on one or many URLs, list them, and check for changes on demand — with optional SSRF-guarded webhook delivery" — but omits the job-management actions (pause/resume/delete) that the tool supports, a minor coverage gap that keeps it below the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what ("Create lazy watch jobs… list them, and check for changes on demand") and when ("Use when the user says…") with concrete quoted trigger phrases, exactly matching the top anchor's what+when structure.

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger phrasings users would actually say: "monitor this page", "watch this URL for changes", "tell me when this updates", "track this changelog", "notify me if this changes", plus "recurring change detection on web content" — covering synonyms and varied user intents, matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

The recurring/lazy framing ("Monitor a page for changes over time", "recurring change detection") carves a clear niche with distinct triggers, but phrases like "check for changes on demand" and "track this changelog" carry minor overlap risk with adjacent one-shot diff and bulk change-detection skills, which the description does not disambiguate.

4 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

KnockOutEZ/wigolo

Path

skills/wigolo-watch/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.