client-report-writer
Skill7 starsChanged 5 months agoMITView on GitHub
Turn GSC/GA4 performance data into a client-ready weekly or monthly narrative. Use when Codex needs to produce a professional SEO performance report with executive summary, metrics breakdown, trend analysis, and action recommendations.
In this repository22 other files it gives its agents.
- authority-mark-keyword-difficultySkill
- cannibalization-checkSkill
- competitor-serp-monitorSkill
- content-decay-monitor-setupSkill
- content-moat-plannerSkill
- content-refresh-briefSkill
- exceed-quality-thresholdSkill
- internal-link-builderSkill
- keyword-opportunity-finderSkill
- keyword-plannerSkill
- live-search-console-dataSkill
- proposal-builderSkill
- refresh-vs-new-contentSkill
- schema-fix-writerSkill
- seo-content-briefSkill
- seo-growth-loopSkill
- seo-offer-architectSkill
- seo-priority-scoreSkill
- seo-strategySkill
- technical-seo-triageSkill
- title-meta-rewriterSkill
- traffic-decay-detectorSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
Write the report in professional narrative form.
- Distinctive: line 35
Add a recommendations section with prioritized actions.
- Distinctive: line 77
Use professional, direct language.
- Distinctive: line 80
Call out what the client should be excited about and what needs attention.
- Distinctive: line 81
Keep the executive summary to 3-5 sentences — senior stakeholders should get the full picture from it.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Client Report Writer
Overview
Transforms raw GSC and GA4 data into a structured client-ready report. The report tells a clear story: what happened, why it happened, and what to do next. Works with live data or pasted exports.
Inputs
- Current period GSC data (clicks, impressions, CTR, avg position by page and query)
- Prior period GSC data for comparison
- Optional: GA4 data (sessions, users, conversions, landing pages)
- Optional: goals or KPIs the client tracks
- Optional: previous report for trend continuity
- Client name or brand voice preferences
Workflow
- Collect metrics for current and prior periods.
- Calculate period-over-period changes for all key metrics.
- Identify:
- Top-level trend (up, down, flat with magnitude).
- Pages that drove the change (top gainers, top decliners).
- Queries that drove the change.
- Technical issues detected (indexing drops, coverage changes).
- Categorize changes as:
- Expected (seasonal, planned launches, known ranking shifts).
- Actionable (fixable issues with clear ROI).
- Monitoring (needs observation before action).
- Write the report in professional narrative form.
- Add a recommendations section with prioritized actions.
Output Format
## SEO Performance Report
**Client:** [Name] | **Period:** [Range] | **Date:** [Date]
### Executive Summary
[3-5 sentence narrative of overall performance]
### Key Metrics
| Metric | Current | Prior | Change |
|---|---|---|---|
### What Changed
[Explanation of the main movements]
### Pages Driving Performance
#### Top Gainers
[Table with page, metric change, probable cause]
#### Top Decliners
[Table with page, metric change, probable cause]
### Query Trends
[Notable query movements, new opportunities, declining terms]
### Technical Health
[Index status, coverage issues, crawl stats if available]
### Recommendations
1. [Priority action with expected impact]
2. [Secondary action]
3. [Monitoring item]
### Appendix
Data sources, date ranges, methodology notes.Style Guidance
- Use professional, direct language. Avoid jargon where possible.
- Frame negative movements as situations with clear next actions, not failures.
- Include both absolute numbers and percentages.
- Call out what the client should be excited about and what needs attention.
- Keep the executive summary to 3-5 sentences — senior stakeholders should get the full picture from it.
- Separate signal from noise: if a 5% drop is normal fluctuation, say so.
Related Skills
traffic-decay-detector— feeds declining page data into the report.proposal-builder— for converting prospect data into a proposal (consulting version of this).marketingskills/seo/skills/live-search-console-data— live GSC/GA4 data bridge.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

