Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mkurman/watch-monitor
Canonical watch/monitor pack for meaningful change detection across web sources, connectors, repo activity, or triggers, with false-positive suppression and alert summaries.
Passed 25 of 25 test cases with the skill, and 15 of 25 without it.
and 8 more in the full report
10 fixed15 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
What is the third step in the manual run execution recipe after comparing current and prior state?
| Checked | Without skill | With skill |
|---|---|---|
| The third step applies suppression rules. | Missed | Passed |
The instructions your model reads when the skill loads.
I want to define a watch that only notifies me on meaningful changes, whether the source is a webpage, connector-backed resource, repo activity, or trigger event.
watch_source: webpage / connector resource / repo / webhook familythreshold: significance threshold or rule setsuppression_rules: optional false-positive suppression criteriadelivery_channel: in-app or chat channelRun the Watch/Monitor pack every hour for the chosen source and notify only when the threshold is exceeded.
test cases passed, vs 15 / 25 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.