competitor-serp-monitor
Skill7 starsChanged 5 months agoMITView on GitHub
Track competitors new pages, ranking shifts, SERP feature changes, and content strategies. Use when Codex needs to monitor competitor movements in organic search.
In this repository22 other files it gives its agents.
- authority-mark-keyword-difficultySkill
- cannibalization-checkSkill
- client-report-writerSkill
- content-decay-monitor-setupSkill
- content-moat-plannerSkill
- content-refresh-briefSkill
- exceed-quality-thresholdSkill
- internal-link-builderSkill
- keyword-opportunity-finderSkill
- keyword-plannerSkill
- live-search-console-dataSkill
- proposal-builderSkill
- refresh-vs-new-contentSkill
- schema-fix-writerSkill
- seo-content-briefSkill
- seo-growth-loopSkill
- seo-offer-architectSkill
- seo-priority-scoreSkill
- seo-strategySkill
- technical-seo-triageSkill
- title-meta-rewriterSkill
- traffic-decay-detectorSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Check frequency (default: weekly)
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Competitor SERP Monitor
Overview
Monitor a set of competitor domains for changes in their organic search presence: new pages appearing in top positions, ranking shifts, SERP feature acquisition or loss, and content strategy changes.
Inputs
- List of competitor domains to monitor
- Optional: shared keyword list or topic cluster
- Check frequency (default: weekly)
Workflow
- Define the competitor set and shared keywords or topics.
- For each keyword, fetch the current SERP and record:
- Which competitor domains appear and at what rank
- SERP features (featured snippets, PAAs, video, images)
- New URLs from competitors (not seen in previous check)
- Compare against the prior SERP snapshot.
- Flag changes: new competitor entries, rank improvements, SERP feature gains.
- Analyze new competitor content for angle, format, depth, and entities covered.
- Surface threats (competitor gaining on your positions) and opportunities (competitor losing ground).
Output
Competitor movement report with new pages, rank changes, SERP feature shifts, and content analysis.
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
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.

