analytics-review
Website analytics with Pirsch. Use this skill when: - Reviewing website traffic and engagement - Analyzing visitor trends and patterns - Checking top pages and referrers - Comparing performance across time periods - Understanding UTM campaign effectiveness
What this skill does
# Analytics Review Skill
Analyze website performance with Pirsch using the **Overview-Drill Down-Insights** pattern.
## Phase 1: OVERVIEW (High-Level Metrics)
### List Available Domains
```javascript
mcp__pirsch__pirsch_list_domains({})
```
### Get Cached Overview
Quick snapshot of key metrics:
```javascript
mcp__pirsch__pirsch_overview({
domainId: "<domain-id>"
})
```
### Get Detailed Totals
```javascript
mcp__pirsch__pirsch_total({
domainId: "<domain-id>",
from: "2025-01-01",
to: "2025-01-31"
})
```
Returns:
- Visitors
- Views
- Sessions
- Bounces
- Bounce rate
- Conversion rate
### Get Growth Metrics
```javascript
mcp__pirsch__pirsch_growth({
domainId: "<domain-id>",
from: "2025-01-01",
to: "2025-01-31"
})
```
### Check Real-Time Activity
```javascript
mcp__pirsch__pirsch_active({
domainId: "<domain-id>",
seconds: 600 // Last 10 minutes
})
```
## Phase 2: DRILL DOWN (Detailed Analysis)
### Visitor Time Series
```javascript
mcp__pirsch__pirsch_visitors({
domainId: "<domain-id>",
from: "2025-01-01",
to: "2025-01-31",
scale: "day" // day, week, month
})
```
### Top Pages
```javascript
mcp__pirsch__pirsch_pages({
domainId: "<domain-id>",
from: "2025-01-01",
to: "2025-01-31",
limit: 20,
includeAvgTimeOnPage: true
})
```
### Traffic Sources (Referrers)
```javascript
mcp__pirsch__pirsch_referrers({
domainId: "<domain-id>",
from: "2025-01-01",
to: "2025-01-31",
limit: 20
})
```
### UTM Campaign Analysis
```javascript
// By source
mcp__pirsch__pirsch_utm({
domainId: "<domain-id>",
from: "2025-01-01",
to: "2025-01-31",
dimension: "source"
})
// By medium
mcp__pirsch__pirsch_utm({
domainId: "<domain-id>",
dimension: "medium"
})
// By campaign
mcp__pirsch__pirsch_utm({
domainId: "<domain-id>",
dimension: "campaign"
})
```
## Phase 3: INSIGHTS (Comparative Analysis)
### Period Comparison
Compare two time periods:
```javascript
mcp__pirsch__pirsch_compare({
domainId: "<domain-id>",
from: "2025-01-01",
to: "2025-01-31",
compareFrom: "2024-12-01",
compareTo: "2024-12-31",
scale: "day"
})
```
Returns:
- Visitor trends for both periods
- Delta values (absolute change)
- Growth percentages
## Report Formatting
### Dashboard Summary
```text
## Website Analytics Dashboard
verygoodplugins.com | January 2025
### Key Metrics
| Metric | Value | vs Last Month |
|--------|-------|---------------|
| Visitors | 12,450 | +21.7% |
| Pageviews | 45,230 | +17.6% |
| Bounce Rate | 42.3% | -2.8pp |
| Avg Duration | 2m 34s | +16.7% |
### Top Pages
1. /pricing - 4,230 views
2. /features - 3,890 views
3. /blog/getting-started - 2,450 views
4. /docs/api - 1,890 views
5. /about - 1,230 views
### Top Referrers
1. google.com - 5,230 visitors
2. twitter.com - 1,890 visitors
3. github.com - 1,450 visitors
4. reddit.com - 890 visitors
### UTM Sources
1. newsletter - 2,340 visitors
2. twitter-organic - 1,230 visitors
3. google-ads - 890 visitors
```
### Trend Analysis
```text
## Weekly Trend Analysis
Week 1: 2,890 visitors
Week 2: 3,120 visitors (+8%)
Week 3: 3,450 visitors (+11%)
Week 4: 3,780 visitors (+10%)
Overall trend: Steady growth, averaging +9.7% week-over-week
```
## Common Analysis Scenarios
### Traffic Spike Investigation
1. Get daily visitors to identify the spike date
2. Check referrers for that date range
3. Check UTM sources for campaign attribution
4. Review top pages to see what content drove traffic
### Campaign Performance
1. Filter by UTM campaign name
2. Compare visitors, bounce rate, and time on site
3. Check which pages campaign traffic landed on
4. Compare to organic traffic for baseline
### Content Performance
1. Get top pages by views
2. Check average time on page
3. Identify high-bounce pages for optimization
4. Find underperforming content
## Best Practices
### Do
- Start with overview before drilling down
- Use appropriate date ranges for context
- Compare periods of equal length
- Look at trends, not just absolute numbers
- Consider seasonality in comparisons
### Don't
- Draw conclusions from single data points
- Ignore context (holidays, launches, etc.)
- Compare weekends to weekdays
- Forget to check mobile vs desktop
- Overlook bounce rate on landing pages
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".