agentleFS
princechouhan19princechouhan19/OpenCometAI/skills/monitor-page/SKILL.md

Monitor Page

Skill35 starsChanged 4 days agoMITView on GitHub

Register a background watcher that re-checks a page and notifies on change. 1. Determine WHAT to watch: a price, a text string ("In stock"), a section of the page, or the page overall. Get the interval if the user said one, else default to every 15 minutes. 2. Ensure the current tab is on the target URL (navigate first if needed), then call monitor_start with: - url — the page to watch - intervalMin — minutes between checks - checkText…

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ensure the current tab is on the target URL (navigate first if needed), then call monitor_start with:

    line 25
  2. Very specific:

    Prefer a narrow checkText (e.g.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Monitor Page

Register a background watcher that re-checks a page and notifies on change.

Procedure

  1. Determine WHAT to watch: a price, a text string ("In stock"), a section of the page, or the page overall. Get the interval if the user said one, else default to every 15 minutes.
  2. Ensure the current tab is on the target URL (navigate first if needed), then call monitor_start with:
    • url — the page to watch
    • intervalMin — minutes between checks
    • checkText — optional exact text/selector value to detect
  3. Confirm registration from the executor result. State the schedule and that a desktop notification will fire on change.

Tool discipline

  • One monitor per URL — re-registering the same URL updates the previous one.
  • Prefer a narrow checkText (e.g. "₹4,999", "Out of stock") over whole-page diffs — fewer false alarms.
  • Monitoring runs locally in the extension; no page content leaves the device unless Privacy Mode is off.

Answer format

👁 Watching <url> every <N> min for <what>. You'll get a notification when it changes. Mirror in data: { "monitor": { url, intervalMin, checkText } }.

Verify before done

  • Executor returned { ok: true, monitor } — never claim a monitor exists without that confirmation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.