PluginBench
Skill
Review
Audit score 70

alert-manager

aaron-he-zhu/seo-geo-claude-skills

Set up proactive monitoring alerts for ranking, traffic, technical, and competitor changes.

What is alert-manager?

Alert Manager configures threshold-based notifications for future SEO metric changes across rankings, traffic, backlinks, technical issues, and competitor activity. Use this when setting up ongoing monitoring; for one-time reports or current measurements, use rank-tracker or performance-reporter instead.

  • Define alert categories for rankings, traffic, technical, backlinks, competitors, GEO/AI, and brand metrics
  • Configure trigger conditions, thresholds, and priority levels (Critical/High/Medium/Low) for each alert rule
  • Map alert responses to severity levels with response times and next actions
  • Set up delivery channels, routing, cooldowns, and escalation paths
  • Generate alert summary with category counts, critical playbook, and weekly review checklist

How to install alert-manager

npx skills add https://github.com/aaron-he-zhu/seo-geo-claude-skills --skill alert-manager
Prerequisites
  • Recent baseline data or historical metrics for the domains/keywords being monitored
  • Delivery preferences (email, Slack, or other channels)
  • Access to SEO tools or search console data (optional; can work with user-provided baselines)
Claude Code
Cursor
Windsurf
Cline

How to use alert-manager

  1. 1.Specify the domain(s) and metrics you want to monitor (rankings, traffic, technical, backlinks, competitors)
  2. 2.Provide baseline data or recent performance metrics to establish normal volatility
  3. 3.Choose alert categories and define trigger conditions for each (e.g., ranking drop >3 positions)
  4. 4.Set threshold levels and assign priority (Critical/High/Medium/Low) to each alert rule
  5. 5.Configure delivery channels and response plans for each severity level
  6. 6.Review and save the alert configuration to memory/monitoring/

Use cases

Good for
  • Monitor keyword ranking drops and set alerts when top keywords fall more than 3-5 positions
  • Track organic traffic changes with warning at -15% week-over-week and critical at -30%
  • Watch for new crawl errors and security issues with daily frequency
  • Monitor backlink loss and AI citation changes across key queries
  • Set up multi-channel notifications (email, Slack) with escalation for critical issues
Who it's for
  • SEO managers and specialists setting up ongoing monitoring
  • Digital marketers tracking competitive changes and market shifts
  • Technical SEO teams monitoring crawl errors and Core Web Vitals
  • Content strategists watching AI visibility and citation metrics

alert-manager FAQ

What's the difference between alert-manager and rank-tracker?

alert-manager sets up ongoing threshold-based notifications for future changes. rank-tracker measures current rankings one time. Use alert-manager for monitoring; use rank-tracker for snapshots.

Do I need SEO tools connected to use this skill?

No. All integrations are optional. You can provide baseline data, critical keywords, and preferences manually, and the skill will configure alerts without external tools.

How do I avoid alert fatigue?

The skill includes threshold tuning based on normal volatility, cooldowns, and escalation paths. Label thresholds as Measured, User-provided, or Estimated to ensure they match your actual metric behavior.

What happens after I set up alerts?

The skill outputs a configuration summary and saves it to memory/monitoring/. For ongoing reporting, use performance-reporter next. Alerts run standalone after setup.

Can I set alerts for competitor metrics?

Yes. Competitor alerts are one of the supported categories. Define trigger conditions (e.g., competitor gains >5 positions on shared keywords) and set priority and delivery routing.

Full instructions (SKILL.md)

Source of truth, from aaron-he-zhu/seo-geo-claude-skills.


name: alert-manager description: 'Use when the user asks to "set SEO alerts" or "排名掉了提醒我"; configures threshold notifications for FUTURE ranking, traffic, technical, and competitor changes. Not for one-time measurement or reporting — use rank-tracker or performance-reporter. SEO预警/排名监控' version: "9.9.12" license: Apache-2.0 compatibility: "Claude Code and compatible agent-skill hosts" homepage: "https://github.com/aaron-he-zhu/seo-geo-claude-skills" when_to_use: "Use when setting up monitoring alerts for rankings, traffic, backlinks, technical issues, or AI visibility changes." argument-hint: "<domain> [metric]" metadata: author: aaron-he-zhu version: "9.9.12" geo-relevance: "low"

Alert Manager

Sets up proactive monitoring alerts for ranking, traffic, technical, backlink, competitor, and GEO changes.

Quick Start

Set up SEO monitoring alerts for [domain]
Create ranking drop alerts for my top 20 keywords

Skill Contract

Expected output: an alert configuration summary plus the standard handoff summary for memory/monitoring/.

  • Reads: baselines, critical keywords/metrics to watch, normal volatility, delivery preferences, and any user-provided or tool data.
  • Writes: a user-facing monitoring deliverable and reusable summary.
  • Promotes: significant anomalies, durable thresholds, follow-up actions, and pending decisions to memory/open-loops.md.
  • Done when: each chosen alert category has a named trigger condition, threshold, and priority; a Critical/High/Medium/Low response plan and delivery routing are defined; and thresholds are tuned to the metric's stated normal volatility.
  • Primary next skill: performance-reporter when alert output needs a reporting cadence.

Handoff Summary

Emit the standard shape from skill-contract.md §Handoff Summary Format.

Data Sources

All integrations optional (see CONNECTORS.md). With tools, monitor real-time feeds from ~~SEO tool, ~~search console, and ~~web crawler. Without tools, ask for baselines, critical keywords, preferences, and historical data.

Decision Gates

Stop and ask the user when:

  • No baseline or normal-volatility reference exists for the metrics to be watched — thresholds would be arbitrary. Offer: (1) supply recent baseline data, (2) use the Quick Reference defaults below and label them Estimated, (3) cancel.

Continue silently (never stop for):

  • Which delivery channel to use — default to the channel already in context (or email) and note it.
  • A category the user did not mention — leave it unconfigured; do not add alerts they did not request.

Instructions

When a user requests alert setup:

  1. Define Alert Categories — choose from rankings, traffic, technical, backlinks, competitors, GEO / AI, and brand alerts.
  2. Configure Alert Rules by Category — define trigger condition, threshold, alert name, and priority for each relevant rule; tie each threshold to a stated baseline and label that baseline Measured / User-provided / Estimated.
  3. Define Alert Response Plans — map Critical / High / Medium / Low to response time and next actions.
  4. Set Up Alert Delivery — configure channels, routing, cooldowns, maintenance windows, and escalation paths.
  5. Create Alert Summary — output category counts, the critical playbook, and a weekly review checklist as the deliverable.

Label every metric Measured (tool/export), User-provided, or Estimated (model inference); never present an estimate as measured; if a required metric is unavailable, mark it N/A — do not invent it.

Reference: See Alert Configuration Templates for the full category tables, thresholds, and response-plan templates.

Example

Sample outcome: a keyword alert matrix with Critical vs High thresholds, a response plan for drops, and notification routing to email + Slack.

Alert Threshold Quick Reference

MetricWarningCriticalFrequency
Organic traffic-15% WoW-30% WoWDaily
Keyword positions>3 position drop>5 position dropDaily
Pages indexed-5% change-20% changeWeekly
Crawl errors>10 new/day>50 new/dayDaily
Core Web Vitals"Needs Improvement""Poor"Weekly
Backlinks lost>5% in 1 week>15% in 1 weekWeekly
AI citation lossAny key query>20% queriesWeekly
Security issuesAny detectedAny detectedDaily

Reference: See Alert Threshold Guide for threshold setting, fatigue prevention, escalation paths, and response playbooks.

Save Results

Ask "Save these results?" If yes, write to memory/monitoring/ — see Skill Contract §Save Results Template.

Reference Materials

Next Best Skill

Reporting cadence requested → performance-reporter. Standalone setup → Terminal. Visited-set rule applies per skill-contract.md.