agentleFS
marketingskillsmarketingskills/seo/skills/content-decay-monitor-setup/SKILL.md

content-decay-monitor-setup

Skill7 starsChanged 5 months agoMITView on GitHub

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.

The file

Files
SKILL.md

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.

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.