Save monitored pages and topics to schedule recurring decay scans in local agents. Use when Codex needs to set up ongoing content performance monitoring for a set of pages or topics.
Scanned 9/20/2026
Install to Claude Code
npx -y skills add unempyd/revenueos --skill content-decay-monitor-setup --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Content Decay Monitor Setup?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/unempyd-content-decay-monitor-setup)More formats (shields.io, HTML) on the badges page.
---
name: content-decay-monitor-setup
description: Save monitored pages and topics to schedule recurring decay scans in local agents. Use when Codex needs to set up ongoing content performance monitoring for a set of pages or topics.
---
# Content Decay Monitor Setup
## Overview
Configure a recurring monitor that checks a list of pages or topics for organic performance changes. The monitor runs on a schedule (weekly/monthly) and alerts when performance drops below a threshold.
## Inputs
- List of URLs or topics to monitor
- Monitoring frequency (weekly, biweekly, monthly)
- Alert threshold (e.g., 15% click decline, 20% impression drop)
- Optional: GSC property or GA4 property
## Workflow
1. Define the monitor scope: pages, topics, or both.
2. Set baseline performance from current GSC/GA4 data.
3. Configure the check frequency and alert threshold.
4. Store the monitor configuration in a local file or agent config.
5. On each check cycle: fetch current data, compare to baseline, flag pages below threshold.
6. Route alerts to the user (with traffic-decay-detector for deeper analysis).
## Output
Monitor configuration file and recurring check instructions for the agent runtime.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!