/content-monitor
Monitor web pages for changes and extract updated content with scheduling support.
$ npx -y skills add CoWork-OS/CoWork-OS --skill content-monitor --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/content-monitor
Context preview
The summary Claude sees to decide when to auto-load this skill.
Monitor web pages for changes and extract updated content with scheduling support.
SKILL.md
content-monitor.SKILL.mdname: content-monitor
description: "Monitor web pages for changes and extract updated content with scheduling support."
Content Monitor
Purpose
Monitor web pages for changes and extract updated content with scheduling support.
Routing
- Use when: Use when the user wants to monitor a webpage for changes, track content updates, or set up recurring content checks.
- Do not use when: Don't use for one-time scraping where web-scraper skill is more appropriate.
- Outputs: Content snapshot with timestamp for comparison, optionally scheduled for recurring checks.
- Success criteria: Captures a clean content snapshot that can be compared with future scrapes to detect changes.
Trigger Examples
Positive
- Use the content-monitor skill for this request.
- Help me with content monitor.
- Use when the user wants to monitor a webpage for changes, track content updates, or set up recurring content checks.
- Content Monitor: provide an actionable result.
Negative
- Don't use for one-time scraping where web-scraper skill is more appropriate.
- Do not use content-monitor for unrelated requests.
- This request is outside content monitor scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | url | string | Yes | URL to monitor for changes | | selector | string | No | CSS selector for the section to monitor (optional) |
Runtime Prompt
- Current runtime prompt length: 997 characters.
- Runtime prompt is defined directly in `../content-monitor.json`.
Read more
name: content-monitor description: "Monitor web pages for changes and extract updated content with scheduling support."
Content Monitor
Purpose
Monitor web pages for changes and extract updated content with scheduling support.
Routing
- Use when: Use when the user wants to monitor a webpage for changes, track content updates, or set up recurring content checks.
- Do not use when: Don't use for one-time scraping where web-scraper skill is more appropriate.
- Outputs: Content snapshot with timestamp for comparison, optionally scheduled for recurring checks.
- Success criteria: Captures a clean content snapshot that can be compared with future scrapes to detect changes.
Trigger Examples
Positive
- Use the content-monitor skill for this request.
- Help me with content monitor.
- Use when the user wants to monitor a webpage for changes, track content updates, or set up recurring content checks.
- Content Monitor: provide an actionable result.
Negative
- Don't use for one-time scraping where web-scraper skill is more appropriate.
- Do not use content-monitor for unrelated requests.
- This request is outside content monitor scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | url | string | Yes | URL to monitor for changes | | selector | string | No | CSS selector for the section to monitor (optional) |
Runtime Prompt
- Current runtime prompt length: 997 characters.
- Runtime prompt is defined directly in `../content-monitor.json`.
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
- /attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide discovery passes with worker-specific threat models, semantically merge candidates, synthesize one canonical validation
Open skill - /finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Open skill - /security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
Open skill