Alert Manager

This skill should be used when the user asks to "set up SEO alerts", "monitor rankings", "notify me when rankings drop", "traffic alerts", "watch competitor...

Security Scan

The skill's instructions look like a coherent SEO alert handbook, but its metadata (primary credential AMPLITUDE_API_KEY and an expectation of optional network connectors) does not match the runtime instructions — this mismatch is unexplained and worth clarifying before installing.

Purpose & Capability

The SKILL.md describes setting up SEO/GEO alerts via SEO tools, Search Console, and web crawlers; it does not describe any use of Amplitude. Yet the registry metadata declares AMPLITUDE_API_KEY as the primary credential. Amplitude (a product analytics platform) is not an obvious or necessary dependency for an SEO alert manager, so the declared primaryEnv looks disproportionate or misplaced.

Instruction Scope

The SKILL.md is instruction-only and stays within the alerting domain: templates, threshold guides, notification routing, and prompts for manual/machine connectors. It does not instruct the agent to read unrelated system files or exfiltrate data. However, it references external connectors and optional 'MCP network access' for tool integrations without enumerating endpoints or how credentials would be used.

Install Mechanism

No install spec and no code files are present (instruction-only). That minimizes disk/write risk. The skill does reference an npx command for installing other skills in the same collection, but it does not perform downloads itself.

Credentials

No env vars are required in SKILL.md content, yet metadata lists AMPLITUDE_API_KEY as primaryEnv. There are no other declared credentials for common SEO services (Search Console, Google Analytics, Ahrefs, SEMrush, etc.). Requiring an Amplitude key without explanation is disproportionate and unexplained.

Persistence & Privilege

always:false and model invocation is enabled (the platform default). The skill does not request persistent system-level presence or attempt to modify other skills' configs. No elevated privileges requested in the package metadata or instructions.

What to consider before installing

Key points to check before installing or using this skill: - Ask the publisher why AMPLITUDE_API_KEY is declared as the primary credential and exactly how it would be used. If the skill does not need Amplitude, do not provide that key. - Request a clear list of third-party connectors and endpoints the skill will call (Search Console, Google Analytics, SEO APIs, crawler services). Verify you trust those endpoints before supplying credentials. - Because this is instruction-only (no code), risk is lower, but the skill can still instruct an agent to call external APIs. Confirm where alert data and any exported metrics will be sent and stored. - If you must provide credentials, prefer creating least-privilege API keys (scoped tokens) and rotate/delete them after testing. - If the author cannot justify Amplitude or provide connector details, consider this a red flag and avoid granting credentials or enabling autonomous use. What would change this assessment: - If the author updates metadata to remove AMPLITUDE_API_KEY or documents why Amplitude is required and shows in-SKILL.md usage of that key (and it is necessary and scoped), the mismatch would be resolved and the skill would lean toward benign. - If additional unrelated credentials or network endpoints appear without justification, the verdict should be escalated to higher concern.

SEO & GEO Skills Library · 20 skills for SEO + GEO · Install all: npx skills add aaron-he-zhu/seo-geo-claude-skills

<details> <summary>Browse all 20 skills</summary>

Research · keyword-research · competitor-analysis · serp-analysis · content-gap-analysis

Build · seo-content-writer · geo-content-optimizer · meta-tags-optimizer · schema-markup-generator

Optimize · on-page-seo-auditor · technical-seo-checker · internal-linking-optimizer · content-refresher

Monitor · rank-tracker · backlink-analyzer · performance-reporter · alert-manager

Cross-cutting · content-quality-auditor · domain-authority-auditor · entity-optimizer · memory-management

</details>

Sets up proactive monitoring alerts for critical SEO and GEO metrics. Triggers notifications when rankings drop, traffic changes significantly, technical issues occur, or competitors make moves.

When to Use This Skill

• Setting up SEO monitoring systems
• Creating ranking drop alerts
• Monitoring technical SEO health
• Tracking competitor movements
• Alerting on content performance changes
• Monitoring GEO/AI visibility changes
• Setting up brand mention alerts

What This Skill Does

1. Alert Configuration: Sets up custom alert thresholds
2. Multi-Metric Monitoring: Tracks rankings, traffic, technical issues
3. Threshold Management: Defines when alerts trigger
4. Priority Classification: Categorizes alerts by severity
5. Notification Setup: Configures how alerts are delivered
6. Alert Response Plans: Creates action plans for each alert type
7. Alert History: Tracks alert patterns over time

How to Use

Set Up Alerts

Set up SEO monitoring alerts for [domain]

Create ranking drop alerts for my top 20 keywords

Configure Specific Alerts

Alert me when [specific condition]

Set up competitor monitoring for [competitor domains]

Review Alert System

Review and optimize my current SEO alerts

Data Sources

See CONNECTORS.md for tool category placeholders.

With ~~SEO tool + ~~search console + ~~web crawler connected: Automatically monitor real-time metric feeds for ranking changes via ~~SEO tool API, indexing and coverage alerts from ~~search console, and technical health alerts from ~~web crawler. Set up automated threshold-based alerts with notification delivery.

With manual data only: Ask the user to provide:

1. Current baseline metrics for alert thresholds (rankings, traffic, backlinks)
2. Critical keywords or pages to monitor
3. Alert priority levels and notification preferences
4. Historical data to understand normal fluctuation ranges
5. Manual reporting on metric changes when they check their tools

Proceed with the alert configuration using provided parameters. User will need to manually check metrics and report changes for alert triggers.

Instructions

When a user requests alert setup:

1. Define Alert Categories

   ## SEO Alert System Configuration
   
   **Domain**: [domain]
   **Configured Date**: [date]
   
   ### Alert Categories
   
   | Category | Description | Typical Urgency |
   |----------|-------------|-----------------|
   | Ranking Alerts | Keyword position changes | Medium-High |
   | Traffic Alerts | Organic traffic fluctuations | High |
   | Technical Alerts | Site health issues | Critical |
   | Backlink Alerts | Link profile changes | Medium |
   | Competitor Alerts | Competitor movements | Low-Medium |
   | GEO Alerts | AI visibility changes | Medium |
   | Brand Alerts | Brand mentions and reputation | Medium |
   

2. Configure Alert Rules by Category

   For each relevant category (Rankings, Traffic, Technical, Backlinks, Competitors, GEO/AI, Brand), define alert name, trigger condition, threshold, and priority level.

   Reference: See references/alert-configuration-templates.md for complete alert tables, threshold examples, and response plan templates for all 7 categories.

3. Define Alert Response Plans

   Map each priority level (Critical, High, Medium, Low) to a response time and immediate action steps.

4. Set Up Alert Delivery

   Configure notification channels (Email, SMS, Slack), recipient routing by role, suppression rules (duplicate cooldown, maintenance windows), and escalation paths.

5. Create Alert Summary

   # SEO Alert System Summary
   
   **Domain**: [domain]
   **Configured**: [date]
   **Total Active Alerts**: [X]
   
   ## Alert Count by Category
   
   | Category | Critical | High | Medium | Low | Total |
   |----------|----------|------|--------|-----|-------|
   | Rankings | [X] | [X] | [X] | [X] | [X] |
   | Traffic | [X] | [X] | [X] | [X] | [X] |
   | Technical | [X] | [X] | [X] | [X] | [X] |
   | Backlinks | [X] | [X] | [X] | [X] | [X] |
   | Competitors | [X] | [X] | [X] | [X] | [X] |
   | GEO | [X] | [X] | [X] | [X] | [X] |
   | **Total** | **[X]** | **[X]** | **[X]** | **[X]** | **[X]** |
   
   ## Quick Reference
   
   ### If You Get a Critical Alert
   
   1. Don't panic
   2. Check alert details
   3. Follow response plan
   4. Document actions taken
   5. Update stakeholders
   
   ### Weekly Alert Review Checklist
   
   - [ ] Review all alerts triggered
   - [ ] Identify patterns
   - [ ] Adjust thresholds if needed
   - [ ] Update response plans
   - [ ] Clean up false positives
   

Validation Checkpoints

Input Validation

• Alert thresholds are based on realistic baseline data
• Critical keywords and pages clearly identified
• Response plans defined for each alert priority level
• Notification channels configured with appropriate recipients

Output Validation

• Every metric cites its data source and collection date
• Alert thresholds account for normal metric fluctuations
• Response plans are specific and time-bound
• Source of each alert trigger clearly stated (~~SEO tool API alert, ~~search console notification, ~~web crawler alert, or manual user check)

Example

User: "Set up ranking drop alerts for my top keywords"

Output:

## Ranking Alert Configuration

### Critical Keywords (Immediate Alert)

| Keyword | Current | Alert If | Priority |
|---------|---------|----------|----------|
| best project management software | 2 | Drops to 5+ | 🔴 Critical |
| project management tools | 4 | Drops to 8+ | 🔴 Critical |
| team collaboration software | 1 | Any drop | 🔴 Critical |

### Important Keywords (Same-Day Alert)

| Keyword | Current | Alert If | Priority |
|---------|---------|----------|----------|
| agile project management | 7 | Drops out of top 10 | 🔴 High |
| kanban software | 9 | Drops out of top 10 | 🔴 High |

### Alert Response Plan

**If Critical Keyword Drops**:
1. Check if page is still indexed (site:url)
2. Look for algorithm update announcements
3. Analyze what changed in SERP
4. Review competitor ranking changes
5. Check for technical issues on page
6. Create recovery action plan within 24 hours

**Notification**: Email + Slack to SEO team immediately

Tips for Success

1. Start simple - Don't create too many alerts initially
2. Tune thresholds - Adjust based on normal fluctuations
3. Avoid alert fatigue - Too many alerts = ignored alerts
4. Document response plans - Know what to do when alerts fire
5. Review regularly - Alerts need maintenance as your SEO matures
6. Include positive alerts - Track wins, not just problems

Alert Threshold Quick Reference

Metric	Warning	Critical	Frequency
Organic traffic	-15% WoW	-30% WoW	Daily
Keyword positions	>3 position drop	>5 position drop	Daily
Pages indexed	-5% change	-20% change	Weekly
Crawl errors	>10 new/day	>50 new/day	Daily
Core Web Vitals	"Needs Improvement"	"Poor"	Weekly
Backlinks lost	>5% in 1 week	>15% in 1 week	Weekly
AI citation loss	Any key query	>20% queries	Weekly
Security issues	Any detected	Any detected	Daily

Reference: See references/alert-threshold-guide.md for baseline establishment, threshold setting methodology, fatigue prevention, escalation paths, and response playbooks.

Reference Materials

• Alert Threshold Guide — Recommended thresholds by metric, fatigue prevention strategies, and escalation path templates

Related Skills

• rank-tracker — Ranking data for alerts
• backlink-analyzer — Backlink monitoring
• technical-seo-checker — Technical monitoring
• performance-reporter — Alert summaries in reports
• memory-management — Store alert history and thresholds in project memory
• content-refresher — Content decay alerts trigger refresh workflows