thatrebeccarae/claude-marketing / skills/google-analytics
google-analytics
VerifiedAnalyze Google Analytics data, review website performance metrics, identify traffic patterns, and suggest data-driven improvements. Use when the user asks about analytics, website metrics, traffic analysis, conversion rates, user behavior, or performance optimization.
| File | Kind | Size |
|---|---|---|
| .env.example | other | 1.1 KB |
| EXAMPLES.md | markdown | 13.5 KB |
| LICENSE | other | 1.0 KB |
| REFERENCE.md | markdown | 8.6 KB |
| SKILL.md | skill md | 5.0 KB |
| requirements.txt | manifest | 152 B |
| scripts/analyze.pyexecutable | script | 16.0 KB |
| scripts/ga_client.pyexecutable | script | 11.6 KB |
.env.example
View on GitHub# Google Analytics API Configuration
# Copy this file to .env and fill in your actual values
# Your Google Analytics 4 Property ID
# Find this in GA4: Admin > Property Settings > Property ID
# Format: 123456789 (numeric only, not the "G-" measurement ID)
GOOGLE_ANALYTICS_PROPERTY_ID=your-property-id-here
# Path to your Google Cloud service account JSON key file
# Create a service account in Google Cloud Console and download the JSON key
# Store this file OUTSIDE your git repository for security
# Example: /home/user/.config/google-analytics/service-account-key.json
GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account-key.json
# How to set up:
# 1. Go to Google Cloud Console (console.cloud.google.com)
# 2. Create or select a project
# 3. Enable the Google Analytics Data API
# 4. Create a service account (IAM & Admin > Service Accounts)
# 5. Download the JSON key file
# 6. Go to GA4 Admin > Property Access Management
# 7. Add the service account email with "Viewer" role
# 8. Update the values above with your property ID and key file path
# 9. Rename this file to .env
# 10. NEVER commit .env or the JSON key file to version control!
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| deprecation-and-migrationaddyosmani/agent-skillsManages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset existing code. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| performance-optimizationaddyosmani/agent-skillsOptimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| agent-cost-reportthedotmack/claude-memBelievable agent cost report for any period, default the last 7 full days PT, not counting today. Measured tokens from Claude Code transcripts priced at OpenRouter list prices (ESTIMATED), measured provider spend when a sanctioned source exists, note-taker cost separate, Timing-style HTML/PDF plus report.json, line-items.csv, evidence.json. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |