Real-time GEO metrics monitoring and alerting orchestrator. Use this skill whenever the user wants to track, visualize, and react to AI GEO performance metri...
An orchestration skill for GEO core-metrics monitoring and alerting that turns static GEO analysis into a living, time-based observability system.
This skill focuses on:
It does not directly pull data from third-party tools or models. Instead, it:
Invoke this skill whenever:
geo-report-builder or similar skillsThis skill is especially relevant if the user says things like:
Do not limit triggering only to the exact keywords above; trigger whenever the intent is: “Design or improve an ongoing GEO metrics tracking and alert system for AI visibility.”
This skill should coordinate with (not replace) other GEO skills:
geo-report-builder:
geo-studio:
geo-content-optimizer / geo-content-publisher:
geo-site-audit:
If these skills are not present, still follow the same monitoring shape and clearly explain:
When designing the monitoring system, consistently define and use the following concepts:
AIGVR (AI-Generated Visibility Rate):
SoM (Share of Model):
Citation volume:
Coverage & footprint:
Latency & change detection:
You do not need to impose a single rigid formula for each metric. Instead:
When this skill is invoked, follow this 8-step workflow unless the user explicitly asks for only a subset.
Briefly but explicitly identify:
Output a short “Monitoring Brief” section summarizing this in 5–10 bullet points.
Create a metrics catalog that is:
Output as a markdown table, e.g.:
| Metric | Description | Formula / Approximation | Dimensions | Cadence |
|------------------|-----------------------------------------------|--------------------------------------------------|-------------------------------|---------|
| AIGVR | AI-generated visibility rate | brand-answers / total sampled answers | platform, intent, locale | weekly |
| SoM | Share of Model vs. competitors | brand answers / all brand+competitor answers | platform, intent, competitor | weekly |
| Citation Volume | Count of AI citations of our brand/resources | number of links/mentions in sampled outputs | platform, page, intent | daily |
| Intent Coverage | # of intents where we appear at all | count of intents with ≥1 brand citation | platform, intent cluster | monthly |
Where the user already has internal metric names, map them into this table and keep both labels.
Design the data model for storing GEO metrics:
Output:
## Tracking Schema & Storage containing:
For each metric and platform, design the data collection plan:
geo-report-builder (periodic static snapshots)Output:
## Data Sources & Collection with:
Translate the metrics and schema into practical dashboards for different audiences:
Output:
## Dashboards & Views that includes:
Design alerts so the team is notified when something important changes:
Output:
## Alerts & Anomaly Rules with:
```yaml
alert: low_aigvr_core_intents
metric: aigvr
scope: [platform: "ChatGPT", intent_cluster: "core-product"]
condition: "current_3d_avg < 0.7 * previous_14d_avg"
severity: critical
channel: "Slack #geo-alerts"
### 7. Establish operational routines & playbooks
Define **how the team should use the dashboards and alerts**:
- **Cadences**:
- Daily check: quick scan of key dashboards and alerts
- Weekly/bi-weekly review: deeper dive into trends, experiments, and incidents
- Monthly/quarterly retro: adjustments to metrics, targets, and tooling
- **Playbooks**:
- What to do when:
- AIGVR drops significantly for a key intent
- SoM falls vs. a specific competitor
- Citation volume suddenly spikes (positive anomaly)
- How to **tie actions back** to content, schema, or distribution changes
Output:
- A section `## Operational Routines` that includes:
- A checklist-style **runbook** for daily/weekly/monthly workflows
- 1–3 short **incident playbooks** (“If X happens, do Y and Z”).
### 8. Integrate with GEO reports and strategy
Show how this monitoring layer fits into the broader GEO system:
- Connect to `geo-report-builder`:
- Use its reports as **snapshots** that can be logged and compared over time.
- Suggest which sections or metrics from reports should be **logged into the tracking schema**.
- Connect to `geo-studio` and `geo-content-*` skills:
- Use monitoring insights to **prioritize new content**, **optimize underperformers**, or
**double-down on winners**.
- Close the loop:
- Define how periodic reports and real-time dashboards should **inform each other**.
Output:
- A section `## Integration with GEO Strategy` that:
- Summarizes feedback loops between monitoring and execution
- Lists **3–7 concrete examples** of how a change in metrics should trigger GEO actions.
---
## Output format
Unless the user explicitly requests a different format, structure your answer as:
1. `## Monitoring Brief`
2. `## Metrics Catalog`
3. `## Tracking Schema & Storage`
4. `## Data Sources & Collection`
5. `## Dashboards & Views`
6. `## Alerts & Anomaly Rules`
7. `## Operational Routines`
8. `## Integration with GEO Strategy`
Use:
- **Markdown headings and tables** for structure
- Bulleted lists instead of dense paragraphs
- Short, actionable sentences suitable for copying into dashboards/BI briefs, runbooks, or tickets
If the user only asks for a **subset** (e.g., “just define metrics and alerts for AIGVR”), still keep
the headings but clearly mark skipped sections (e.g., “Not in scope for this request”).
---
## Examples of triggering prompts
These are **example user prompts** that should trigger this skill (for reference; not user-facing):
- “We already use geo-report-builder once a month. Help us design a real-time GEO metrics dashboard
for AIGVR and SoM, with alerts when our AI citations spike or crash.”
- “Our Perplexity citations suddenly fell off a cliff last week. Can you help us set up a system to
monitor AI citation volume across ChatGPT/Perplexity/Gemini and alert us on future drops?”
- “Leadership wants a weekly ‘AI visibility health’ board. Design the metrics, tables, dashboards,
and alert rules so we can track SoM and AIGVR for our top 50 intents.”
- “We’re launching several GEO campaigns each month. Build a monitoring framework that ties campaign
launches to changes in AI citations, SoM, and coverage over time.”
You do **not** need to surface this list directly to the user; it is here to clarify intent.
---
ZIP package — ready to use