performance-reporter

name	performance-reporter
description	Use when the user asks to "generate an SEO report" or "出月报"; builds multi-metric stakeholder reports and dashboards spanning traffic, rankings, authority, and content progress. Not for raw ranking deltas — use rank-tracker. 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 generating multi-metric SEO/GEO performance reports, traffic summaries, stakeholder dashboards, SEO报告, 流量报告, 月报, 周报, or 汇报给老板. Not for raw ranking deltas — use rank-tracker.
argument-hint	<domain> [date range]
metadata	{"author":"aaron-he-zhu","version":"9.9.12","geo-relevance":"medium"}

Performance Reporter

Aggregates SEO/GEO data, builds stakeholder reports, benchmarks goals/competitors, calculates ROI, and turns deltas into prioritized recommendations.

Quick Start

Create an SEO performance report for [domain] for [time period]
Generate an executive summary of SEO performance for [month/quarter]
Create a GEO visibility report for [domain]
Generate a content performance report

Skill Contract

Expected output: a delta summary, alert/report output, and a short handoff summary ready for memory/monitoring/.

• Reads: current and prior-period metrics across traffic/rankings/authority/content, report audience, date range, and any user-provided or tool data.
• Writes: a user-facing monitoring deliverable plus a reusable summary that can be stored under memory/monitoring/.
• Promotes: significant changes, confirmed anomalies, follow-up actions, and pending decisions to memory/open-loops.md.
• Done when: each in-scope section (traffic, rankings, GEO, authority, backlinks, content) is present or marked "Not yet evaluated"; every metric is source-tagged and compared to the prior period; and recommendations carry owner, priority, and expected impact.
• Primary next skill: use the Next Best Skill below when a change needs action.

Handoff Summary

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

Data Sources

All integrations optional (see CONNECTORS.md). With tools connected, aggregates traffic from ~~analytics, search data from ~~search console, rankings/backlinks from ~~SEO tool, and AI visibility from ~~AI monitor. Without tools, ask user for analytics exports, Search Console data, ranking data, and KPIs.

Zero-dependency measurement loop: every reported change should come from a computed delta, not an eyeballed estimate. Store each reporting period's KPIs and let the ledger compute period-over-period movement: python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/ledger.py" record <domain> --source report --data '{"sessions": ..., "clicks": ..., ...}', then ledger.py diff <domain> --source report for the period delta and ledger.py trend <domain> --source report --field <kpi> for the trend line. Label every figure Measured / User-provided / Estimated accordingly, and attribute outcome movements against a control rather than to the latest change by default — see . See .