Proactive monitoring and alert system for SEO and GEO metrics with threshold-based notifications.
Works with
Monitors rankings, traffic, technical issues, backlinks, competitor movements, and brand mentions across seven alert categories
Configures custom thresholds and priority levels (Critical, High, Medium, Low) with severity-based response plans
Supports multiple notification channels (Email, SMS, Slack) with recipient routing, suppression rules, and escalation paths
Includes alert fatigu
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionalert-managerExecute the skills CLI command in your project's root directory to begin installation:
Fetches alert-manager from aaron-he-zhu/seo-geo-claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate alert-manager. Access via /alert-manager in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
873
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
873
stars
SEO & GEO Skills Library · 20 skills for SEO + GEO · ClawHub · skills.sh System Mode: This monitoring skill follows the shared Skill Contract and State Model.
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.
System role: Monitoring layer skill. It turns performance changes into deltas, alerts, and next actions.
Use this when the conversation involves any of these situations — even if the user does not use SEO terminology:
Use this whenever the task needs time-aware change detection, escalation, or stakeholder-ready visibility.
Start with one of these prompts. Finish with a short handoff summary using the repository format in Skill Contract.
Set up SEO monitoring alerts for [domain]
Create ranking drop alerts for my top 20 keywords
Alert me when [specific condition]
Set up competitor monitoring for [competitor domains]
Review and optimize my current SEO alerts
Expected output: a delta summary, alert/report output, and a short handoff summary ready for memory/monitoring/.
memory/monitoring/.memory/open-loops.md and memory/decisions.md.Next Best Skill below when a change needs action.Note: All integrations are optional. This skill works without any API keys — users provide data manually when no tools are connected.
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:
Proceed with the alert configuration using provided parameters. User will need to manually check metrics and report changes for alert triggers.
When a user requests alert setup:
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 |
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.
Define Alert Response Plans
Map each priority level (Critical, High, Medium, Low) to a response time and immediate action steps.
Set Up Alert Delivery
Configure notification channels (Email, SMS, Slack), recipient routing by role, suppression rules (duplicate cooldown, maintenance windows), and escalation paths.
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
User: "Set up ranking drop alerts for my top keywords"
Output:
## Ranking Alert Configuration
### Critical Keywords (Immediate Alert)
| Keyword | Current | Alert If | Priority |Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Solid pick for teams standardizing on skills: alert-manager is focused, and the summary matches what you get after install.
Registry listing for alert-manager matched our evaluation — installs cleanly and behaves as described in the markdown.
alert-manager has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in alert-manager — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend alert-manager for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added alert-manager from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
We added alert-manager from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
alert-manager fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
alert-manager fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
alert-manager is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 31