القائمة
Use when the user asks to "set SEO alerts"; configures ranking, traffic, technical, competitor, and notification thresholds. SEO预警/排名监控
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | alert-manager |
| description | Use when the user asks to "set SEO alerts"; configures ranking, traffic, technical, competitor, and notification thresholds. SEO预警/排名监控 |
| version | 9.9.9 |
| license | Apache-2.0 |
| compatibility | Claude Code, skills.sh, ClawHub, Vercel Labs, Cursor, Windsurf, Codex CLI, Amp, Gemini CLI, Kimi Code, Qwen Code, CodeBuddy |
| 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.9","geo-relevance":"low","tags":["seo","geo","seo-alerts","ranking-alerts","traffic-monitoring","competitor-alerts","automated-monitoring","anomaly-detection","SEO预警","SEOアラート","SEO알림","alertas-seo"],"triggers":["set up SEO alerts","monitor rankings","traffic alerts","competitor alerts","alert me if rankings drop","notify me of traffic changes","watch my keywords for changes","how to monitor my rankings","how to set up SEO alerts","SEO预警","排名监控","流量报警","竞品变动提醒","排名掉了提醒我","流量异常","有变化通知我","SEOアラート","ランキング監視","SEO 알림","순위 모니터링","alertas SEO","monitoreo de rankings","alertas de SEO"]} |
Sets up proactive monitoring alerts for ranking, traffic, technical, backlink, competitor, and GEO changes.
Set up SEO monitoring alerts for [domain]
Create ranking drop alerts for my top 20 keywords
Expected output: an alert configuration summary plus the standard handoff summary for memory/monitoring/.
memory/open-loops.md.Emit the standard shape from skill-contract.md §Handoff Summary Format.
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.
When a user requests alert setup:
Reference: See references/alert-configuration-templates.md for the full category tables, thresholds, and response-plan templates.
Sample outcome: a keyword alert matrix with Critical vs High thresholds, a response plan for drops, and notification routing to email + Slack.
Start simple, tune thresholds to normal volatility, avoid alert fatigue, and review the system regularly.
| 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 threshold setting, fatigue prevention, escalation paths, and response playbooks.
Ask "Save these results?" If yes, write memory/monitoring/YYYY-MM-DD-<topic>.md with headline finding, actions, and open loops.
Reporting cadence requested → performance-reporter. Standalone setup → Terminal. Visited-set rule applies per skill-contract.md.
Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no p
AI-optimized browser automation CLI with context-efficient snapshots. Use for long autonomous sessions, self-verifying workflows, video recording, and cloud browser testing (Browserbase).
Audit Flowser context routing, shared-skill discoverability, and Claude/Codex wiring. Use when context docs or skill surfaces move, split, or drift.
Audit active Flowser plan files for staleness, completion, and routing truth. Use when cleaning up plans, reconciling active work, or archiving completed artifacts.
Audit agent harness health: Claude/Codex agent parity, skill registry consistency, README.md sync, and protocol file wiring. Use when agents, skills, README.md, or development-protocol files move, split, or drift.
Autonomous iterative optimization loop for measurable metrics like coverage, performance, or bundle size. Use when repeated experiments can be judged by a mechanical score.