Page change report
Check named web pages against the last visit and report only real changes (price, wording, availability, broken parts), quoting before and after.
In Lobstack: Skills › Library › Add
What your agent will do.
Someone wants to know when particular pages change — a competitor's pricing, terms of service, a status page, their own checkout — without checking by hand.
- 01
Confirm the pages and what matters on each: the price table, the plan limits, a sentence in the terms. Watching "the whole page" reports every rotating banner.
- 02
Open each page and read what is actually shown, not the page source. Note anything that failed to load.
- 03
Compare with what you remembered from last time. On the first run, remember this visit as the baseline and say nothing can be compared yet.
- 04
Ignore noise: dates, counters, cookie banners, rotating quotes, ad slots, and lists reordered with the same items.
- 05
For each real change, quote the before and the after with the page and the time you read it, and say whether it looks deliberate or broken.
- 06
Remember the new state as the baseline for next time.
- 07
Report by exception: when nothing changed, one line says so. Offer to run it on a schedule, and ask before saving the routine.
Read only. Never sign in, fill in a form, add to a basket or click anything that changes state on somebody's account.
The whole SKILL.md: 33 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: page-change-reportdescription: "Check named web pages against the last visit and report only real changes (price, wording, availability, broken parts), quoting before and after."metadata: title: "Page change report" category: research tags: [monitoring, web]--- ## When to use this Someone wants to know when particular pages change -- a competitor's pricing,terms of service, a status page, their own checkout -- without checking by hand. ## How 1. Confirm the pages and what matters on each: the price table, the plan limits, a sentence in the terms. Watching "the whole page" reports every rotating banner.2. Open each page and read what is actually shown, not the page source. Note anything that failed to load.3. Compare with what you remembered from last time. On the first run, remember this visit as the baseline and say nothing can be compared yet.4. Ignore noise: dates, counters, cookie banners, rotating quotes, ad slots, and lists reordered with the same items.5. For each real change, quote the before and the after with the page and the time you read it, and say whether it looks deliberate or broken.6. Remember the new state as the baseline for next time.7. Report by exception: when nothing changed, one line says so. Offer to run it on a schedule, and ask before saving the routine. Read only. Never sign in, fill in a form, add to a basket or click anything thatchanges state on somebody's account.
- ResearchFeatured
Research brief
Answer a research question with a sourced brief: the answer first, then the evidence, how confident it is, and what could not be found.
SKILL.md · App - Research
Competitor scan
Compare named competitors on what matters to a decision (price, audience, features, recent moves) from their own public pages.
SKILL.md · App - Research
Stress-test a plan
Question a plan or design one point at a time, biggest risk first, until every open point is decided or deliberately parked, then hand back the decisions.
SKILL.md · App - Research
Fact-check a draft
Fact-check a draft: pull out every checkable claim, check each against the source closest to it, and mark it confirmed, wrong (with the fix) or unverified.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App