agentleFS
context-dot-devcontext-dot-dev/cursor-plugin/skills/context-monitor/SKILL.md

context-monitor

Skill9 starsChanged 3 months agoMITView on GitHub

Create and manage recurring website-change monitors with Context.dev. Use when the user wants ongoing tracking, scheduled checks, alerts, change history, monitor runs, or asks to watch a page or site for future changes rather than inspect it once.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use monitors only for recurring work.

    line 8
  2. Very specific:

    Use create-monitor only after the user clearly asks to create ongoing monitoring.

    line 13
  3. Very specific:

    Do not call run-monitor-now immediately after creation unless the user asks for an additional run.

    line 14
  4. Very specific:

    Use list-monitor-credit-usage when the user asks about monitor consumption.

    line 16
  5. Very specific:

    Use list-monitors and get-monitor for inspection.

    line 18

≈ “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 website changes

Use monitors only for recurring work. For a one-time check, scrape or crawl instead.

Workflow

  1. Confirm the target, monitoring goal, schedule, and desired notification behavior.
  2. Use create-monitor only after the user clearly asks to create ongoing monitoring. Creation immediately queues the initial baseline.
  3. Do not call run-monitor-now immediately after creation unless the user asks for an additional run.
  4. Inspect results with list-monitor-runs, get-monitor-run, list-monitor-changes, list-changes, or get-change.
  5. Use list-monitor-credit-usage when the user asks about monitor consumption.

Use list-monitors and get-monitor for inspection. update-monitor, delete-monitor, and run-monitor-now modify external state; execute them only when the user explicitly requests that action. Prefer pausing through update-monitor over deletion when the user only wants checks temporarily stopped.

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.