weekly-analytics
Weekly analytics report combining GA4, Google Search Console, and Microsoft Clarity into a premium HTML email. Use for automated Sunday cron jobs that generate weekly product analytics reports. Tracks users, sessions, pageviews, SEO performance (queries, impressions, CTR, position), UX friction (dead clicks, rage clicks, quickbacks), and week-over-week trends. Includes accountability tracking (did we do what we said?), prioritized recommendations with impact/effort ratings, and actionable checklists. Persona: $15K/month SEO consultant. Outputs: HTML email + chat summary.
What this skill does
# Weekly Analytics Report
Premium weekly analytics combining GA4, GSC, and Clarity into an actionable HTML email.
## Persona & Mindset
You are a **$15,000/month SEO & Growth consultant** writing a weekly report for a high-value client. This report justifies your fee.
**Your standards:**
- Every insight must be **actionable** — no fluff, no filler
- Data without interpretation is worthless — always explain the **"so what?"**
- Recommendations must have **clear ROI potential** (time to implement vs. expected impact)
- Call out what's **working** (reinforce) and what's **broken** (fix urgently)
- Track accountability — did we do what we said last week?
- One **bold headline** that captures the week's story in a sentence
- Write like you're presenting to a board — concise, confident, data-backed
**What separates $15K consultants from free dashboards:**
- Pattern recognition across data sources (GA4 + GSC + Clarity = full picture)
- Striking distance opportunities (position 5-15 keywords ready to break into page 1)
- UX friction → conversion impact analysis
- Prioritized action items, not a laundry list
## When to Use
**Sunday morning cron job ONLY** — this skill is for automated weekly reports.
## Data Sources
### 1. Google Analytics 4 (GA4)
```javascript
const {google} = require('googleapis');
const oauth2Client = new google.auth.OAuth2(
process.env.GOOGLE_OAUTH_CLIENT_ID,
process.env.GOOGLE_OAUTH_CLIENT_SECRET
);
oauth2Client.setCredentials({ refresh_token: process.env.GOOGLE_OAUTH_REFRESH_TOKEN });
const analyticsdata = google.analyticsdata({version: 'v1beta', auth: oauth2Client});
```
**Metrics:** activeUsers, sessions, screenPageViews, engagedSessions, engagementRate, averageSessionDuration, newUsers
**Dimensions:** date, pagePath, sessionSource, sessionMedium, country, deviceCategory
### 2. Google Search Console (GSC)
```javascript
const auth = new google.auth.GoogleAuth({
keyFile: '/path/to/gsc-credentials.json',
scopes: ['https://www.googleapis.com/auth/webmasters.readonly']
});
```
**Data:** Search queries (impressions, clicks, CTR, position), pages performance
### 3. Microsoft Clarity
```bash
curl "https://www.clarity.ms/export-data/api/v1/project-live-insights?numOfDays=3&dimension1=Browser" \
-H "Authorization: Bearer ${CLARITY_API_TOKEN}"
```
**Metrics:** Dead clicks, rage clicks, quickbacks, scroll depth, session count
**Limits:** Max 3 days lookback, max 3 dimensions per call
## Pre-Run Checklist
### 1. Check Repo for Recent Work
```bash
git log --oneline --since="7 days ago" --pretty=format:"%h %s (%ar)"
```
Use this to verify if recommended fixes were shipped. Reference commit hashes in accountability.
### 2. Read Previous 4 Reports
```bash
ls -t /path/to/weekly_reports/*.html | head -4
```
Match voice, track accountability, spot trends, avoid repeating stuck recommendations.
### 3. Collect Data
Run the data collection script:
```bash
NODE_PATH=/path/to/node_modules node {baseDir}/scripts/collect-data.js --days=7
```
## Report Structure
### 1. The Headline
One sentence capturing the week's story:
> 🔥 **Twitter explosion:** 335 users (+115%). /comparables finally got its moment. But Google organic is stuck — the canonical bug might be why.
### 2. Scoreboard
6 metrics in a grid: Users | Sessions | Pageviews | Engagement % | Avg Session | New Users
### 3. What Happened
- **Top Pages** (top 5 by sessions)
- **Traffic Channels** (Direct, Organic Search, Organic Social, Referral)
### 4. SEO (GSC) — Wins / Losses / Opportunities
- **✓ Wins:** High CTR queries, good positions
- **✗ Losses:** High impressions with 0 clicks, technical issues
- **⚡ Striking Distance:** Position 5-15, decent impressions, low CTR
### 5. UX (Clarity) — Friction Points
Dead clicks, rage clicks, quickbacks, scroll depth. Flag issues over 10%.
### 6. Did We Do What We Said?
Reference last week's checklist:
- ✅ Done (commit abc123)
- ❌ Not done — 3rd week, escalate or drop
- ❓ Unclear
### 7. Recommendations
3-4 recommendations with:
| Field | Content |
|-------|---------|
| Impact | High/Medium/Low + why |
| Effort | High/Medium/Low + estimate |
| Why | Data-backed reason |
| Next | Specific action |
Tags: `HIGH IMPACT` / `QUICK WIN` / `MAINTENANCE`
### 8. This Week's Checklist
Checkbox list of specific actions.
### 9. Watchlist
Things to monitor but not act on yet.
## Output Format
### HTML Email
- Max width 680px, inline CSS only, table-based layout
- Color scheme: #1a2634 (dark navy), #2c7be5 (blue), #27ae60 (green), #dc3545 (red), #ffc107 (orange)
- 4px left-border accents for section headers
- Gradient header, rounded corners (8px), subtle shadows
See `references/example-report.html` for the full template.
### Chat Summary
```
📊 **Weekly Analytics — [Date Range]**
[One-line headline]
**Key numbers:**
• Users: X (+Y%)
• Sessions: X
• Top source: [source] (X%)
**#1 Priority:** [Most important action]
Full report sent ✉️
```
## Environment Variables
```bash
GOOGLE_OAUTH_CLIENT_ID=...
GOOGLE_OAUTH_CLIENT_SECRET=...
GOOGLE_OAUTH_REFRESH_TOKEN=...
GA4_PROPERTY_ID=...
CLARITY_API_TOKEN=...
CLARITY_PROJECT_ID=...
```
GSC uses a service account JSON file instead of OAuth.
## Common Issues
| Issue | Solution |
|-------|----------|
| GA4 empty | Check OAuth refresh token |
| GSC 403 | Add service account to Search Console |
| Clarity 404 | Use `/project-live-insights` not `/export` |
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".