CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

75

Quality

93%

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.

Concise and highly actionable with excellent examples and clear sectioning, but the workflow lacks validation/verification checkpoints for its batch-create and delete operations, which the rubric caps at 3 for workflow clarity.

Suggestions

Add a verification checkpoint after batch create (e.g., confirm jobs[] count matches urls[] and report any that failed) so batch results are validated before proceeding.

Add an explicit confirm/verify step before the destructive delete action (e.g., list the job first or require acknowledging job_id) to introduce a validate-before-act feedback loop.

For check results on change, include a brief validate/confirm step (e.g., verify the diff is meaningful before webhook delivery) to give the workflow an explicit feedback loop.

DimensionReasoningScore

Conciseness

Lean body with no padding or explanations of concepts Claude already knows — Quick Reference examples, a compact parameters table, and short How-It-Works/Anti-Patterns sections each earn their tokens. Not 4 because there are no noticeable instances of over-explanation to trim.

5 / 5

Actionability

Quick Reference gives copy-paste-ready JSON for create (single, batch, selector, webhook), list, check, and pause/resume/delete, plus a parameters table with types and defaults covering the common cases. Not 4 because guidance is fully executable with no gaps.

5 / 5

Workflow Clarity

How It Works lists a clear create→check→manage sequence, but the skill has batch operations (urls[]) and a destructive action (delete) with no validation/verification checkpoints (no confirm-before-delete, no batch-creation verification, no validate→fix→retry feedback loop). The rubric's batch/destructive cap at 3 applies and takes precedence; not 4 because the missing checkpoints are material, not minor.

3 / 5

Progressive Disclosure

Well-organized sections (Quick Reference, Parameters, How It Works, Anti-Patterns, When NOT to use, See Also) with one-level-deep, clearly-signaled cross-links to sibling skills; no nested references and no monolithic bulk. Not 4 because structure and signaling are clean with no organization gaps.

5 / 5

Total

18

/

20

Passed

Description

100%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: third-person voice, concrete capabilities, comprehensive natural trigger phrases with synonyms, and an explicit what-and-when structure. No fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Create lazy watch jobs on one or many URLs, list them, and check for changes on demand — with optional SSRF-guarded webhook delivery" — covering create/list/check/webhook with batch and selector variants. Not the 4 anchor because coverage is comprehensive rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both what (monitor pages, create/list/check jobs, webhook delivery) and when ("Use when the user says…" with concrete trigger phrases), matching the 5 anchor; not 4 because the when-clause is concrete and specific rather than merely present.

5 / 5

Trigger Term Quality

Includes natural user phrases with synonyms — "monitor this page", "watch this URL for changes", "tell me when this updates", "track this changelog", "notify me if this changes" — matching the comprehensive-synonym anchor rather than the 4 anchor which expects a few missing terms.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (lazy page-change monitoring with SSRF-guarded webhooks) with distinct triggers and minimal overlap; sibling skills (diff/cache/fetch) are explicitly distinguished. Not 4 because conflict risk is minimal, not just minor.

5 / 5

Total

20

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository
KnockOutEZ/wigolo
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.