performance-reporter▌
aaron-he-zhu/seo-geo-claude-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Comprehensive SEO and GEO performance reports combining rankings, traffic, backlinks, and AI visibility metrics.
- ›Aggregates data from multiple sources (analytics, search console, SEO tools, AI monitors) into executive summaries, detailed analyses, and visual presentations
- ›Generates 11-section reports covering organic traffic, keyword rankings, domain authority, content quality (CORE-EEAT), backlinks, and GEO/AI citation performance
- ›Includes period-over-period trend analysis, benchmar
Performance Reporter
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.
This skill creates comprehensive SEO and GEO performance reports that combine multiple metrics into actionable insights. It produces executive summaries, detailed analyses, and visual data presentations for stakeholder communication.
System role: Monitoring layer skill. It turns performance changes into deltas, alerts, and next actions.
When This Must Trigger
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.
- Monthly/quarterly SEO reporting
- Executive stakeholder updates
- Client reporting for agencies
- Tracking campaign performance
- Combining multiple SEO metrics
- Creating GEO visibility reports
- Documenting ROI from SEO efforts
What This Skill Does
- Data Aggregation: Combines multiple SEO data sources
- Trend Analysis: Identifies patterns across metrics
- Executive Summaries: Creates high-level overviews
- Visual Reports: Presents data in clear formats
- Benchmark Comparison: Tracks against goals and competitors
- Content Quality Tracking: Integrates CORE-EEAT scores across audited pages
- ROI Calculation: Measures SEO investment returns
- Recommendations: Suggests actions based on data
Quick Start
Start with one of these prompts. Finish with a short handoff summary using the repository format in Skill Contract.
Generate Performance Report
Create an SEO performance report for [domain] for [time period]
Executive Summary
Generate an executive summary of SEO performance for [month/quarter]
Specific Report Types
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 metrics, previous baselines, alert thresholds, and reporting context from CLAUDE.md and the shared State Model when available.
- Writes: a user-facing monitoring deliverable plus a reusable summary that can be stored under
memory/monitoring/. - Promotes: significant changes, confirmed anomalies, and follow-up actions to
memory/open-loops.mdandmemory/decisions.md. - Next handoff: use the
Next Best Skillbelow when a change needs action.
Data Sources
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 ~~analytics + ~~search console + ~~SEO tool + ~~AI monitor connected: Automatically aggregate traffic metrics from ~~analytics, search performance data from ~~search console, ranking and backlink data from ~~SEO tool, and GEO visibility metrics from ~~AI monitor. Creates comprehensive multi-source reports with historical trends.
With manual data only: Ask the user to provide:
- Analytics screenshots or traffic data export (sessions, users, conversions)
- Search Console data (impressions, clicks, average position)
- Keyword ranking data for the reporting period
- Backlink metrics (referring domains, new/lost links)
- Key performance indicators and goals for comparison
- AI citation data if tracking GEO metrics
Proceed with the full analysis using provided data. Note in the output which metrics are from automated collection vs. user-provided data.
Instructions
When a user requests a performance report:
-
Define Report Parameters -- Domain, report period, comparison period, report type (Monthly/Quarterly/Annual), audience (Executive/Technical/Client), focus areas.
-
Create Executive Summary -- Overall performance rating, key wins/watch areas/action required, metrics at a glance table (traffic, rankings, conversions, DA, AI citations), SEO ROI calculation.
-
Report Organic Traffic Performance -- Traffic overview (sessions, users, pageviews, bounce rate), traffic trend visualization, traffic by source/device, top performing pages.
-
Report Keyword Rankings -- Rankings overview by position range, distribution change visualization, top improvements and declines, SERP feature performance.
-
Report GEO/AI Performance -- AI citation overview, citations by topic, GEO wins, optimization opportunities.
-
Report Domain Authority (CITE Score) -- If a CITE audit has been run, include CITE dimension scores (C/I/T/E) with period-over-period trends and veto status. If no audit exists, note as "Not yet evaluated."
-
Content Quality (CORE-EEAT Score) -- If content-quality-auditor has been run, include average scores across all 8 CORE-EEAT dimensions with trends. If no audit exists, note as "Not yet evaluated."
-
Report Backlink Performance -- Link profile summary, weekly link acquisition, notable new links, competitive position.
-
Report Content Performance -- Publishing summary, top performing content, content needing attention, content ROI.
-
Generate Recommendations -- Immediate/short-term/long-term actions with priority, expected impact, and owner. Goals for next period.
-
Compile Full Report -- Combine all sections with table of contents, appendix (data sources, methodology, glossary).
Reference: See references/report-output-templates.md for complete output templates for all 11 report sections.
Validation Checkpoints
Input Validation
- Reporting period clearly defined with comparison period
- All required data sources available or alternatives noted
- Target audience identified (executive/technical/client)
- Performance goals and KPIs established for benchmarking
Output Validation
- Every metric cites its data source and collection date
- Trends include period-over-period comparisons
- Recommendations are specific, prioritized, and actionable
- Source of each data point clearly stated (~~analytics data, ~~search console data, ~~SEO tool data, user-provided, or estimated)
Example
User: "Create a monthly SEO report for cloudhosting.com for January 2025"
Output (abbreviated -- full report uses templates from all 11 steps):
# CloudHosting SEO & GEO Performance Report — January 2025
## Executive Summary — Overall Performance: Good
| Metric | Jan 2025 | Dec 2024 | Change | Target | Status |
|--------|----------|----------|--------|--------|--------|
| Organic Traffic | 52,100 | 45,200 | +15.3% | 50,000 | On track |
| Keywords Top 10 | 87 | 79 | +8 | 90 | Watch |
| Organic Conversions | 684 | 612 | +11.8% | 700 | Watch |
| Domain Rating | 54 | 53 | +1 | 55 | Watch |
| AI Citations | 18 | 12 | +50.0% | 20 | Watch |
**SEO ROI**: $8,200 invested / $41,040 organic revenue = 400%
**Immediate**: Fix 37 crawl errors on /pricing/ pages
**This Month**: Optimize mobile LCP; publish 3 AI Overview comparison pages
**This Quarter**: Build Wikidata entry for CloudHost Inc.
Tips for Success
- Lead with insights - Start with what matters, not raw data
- Visualize data - Charts and graphs improve comprehension
- Compare periods - Context makes data meaningful
- Include actions - Every report should drive decisions
- Customize for audience - Executives need different info than technical teams
- Track GEO metrics - AI visibility is increasingly important
Save Results
After delivering monitoring data or reports to the user, ask:
"Save these results for future sessions?"
If yes, write a dated summary to memory/monitoring/YYYY-MM-DD-<topic>.md containing:
- One-line headline finding or status change
- Top 3-5 actionable items
- Open loops or anomalies requiring follow-up
- Source data references
If any findings should influence ongoing strategy, recommend promoting key conclusions to memory/hot-cache.md.
Reference Materials
- Report Output Templates — Complete output templates for all 11 report sections
- KPI Definitions — SEO/GEO metric definitions with benchmarks, good ranges, warning thresholds, trend analysis, and attribution guidance
- Report Templates by Audience — Copy-ready templates for executive, marketing, technical, and client audiences
Next Best Skill
- Primary: alert-manager — turn reporting insights into ongoing monitoring rules.
How to use performance-reporter on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add performance-reporter
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches performance-reporter from GitHub repository aaron-he-zhu/seo-geo-claude-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate performance-reporter. Access the skill through slash commands (e.g., /performance-reporter) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★31 reviews- ★★★★★Amina Thomas· Dec 16, 2024
Solid pick for teams standardizing on skills: performance-reporter is focused, and the summary matches what you get after install.
- ★★★★★Yuki Brown· Dec 4, 2024
performance-reporter is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Mia Martin· Nov 7, 2024
We added performance-reporter from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Mia Menon· Oct 26, 2024
performance-reporter fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Oshnikdeep· Sep 25, 2024
performance-reporter is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Piyush G· Sep 17, 2024
performance-reporter has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Isabella Chen· Sep 17, 2024
Registry listing for performance-reporter matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Olivia Huang· Sep 9, 2024
Solid pick for teams standardizing on skills: performance-reporter is focused, and the summary matches what you get after install.
- ★★★★★Nia Singh· Sep 5, 2024
performance-reporter is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Henry Mehta· Aug 28, 2024
performance-reporter has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 31