analytics-interpretation

A tool for interpreting Google Analytics 4, which measures activity on a website, and Google Search Console, which reports how a site appears in Google Search. It compares metrics with stated benchmarks and suggests actions.

In plain words
What is it for?
Use it to review content performance, traffic patterns, search visibility, engagement, rankings, click-through rates, mobile usability, and Core Web Vitals.
Why use it?
It turns traffic and search data into status indicators and practical decisions instead of leaving you to interpret raw numbers alone.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/nicepkg/ai-workflow/analytics-interpretation
Any agent
npx skills add nicepkg/ai-workflow --skill analytics-interpretation
Clone the repo
git clone --depth 1 https://github.com/nicepkg/ai-workflow

Made for: Claude Code, Codex.

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,493 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00021 $0.01493
Opus 5 $0.00010 $0.00746
Sonnet 5 $0.00004 $0.00299
Haiku 4.5 $0.00002 $0.00149

Measured 2d ago against content hash 0ebb066ce383, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

analytics-interpretation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

workflows/marketing-pro-workflow/.claude/skills/analytics-interpretation/SKILL.md · 200 lines

How it starts

The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analytics Interpretation

When to Use

  • Analyzing content performance reports
  • Understanding traffic patterns
  • Interpreting search console data
  • Making data-driven content decisions
  • Explaining metrics to stakeholders

Metric Benchmarks

Google Analytics 4 (GA4)

Metric Good Warning Poor Action When Poor
Avg Time on Page >3 min 1-3 min <1 min Improve content depth, add multimedia
Bounce Rate <40% 40-70% >70% Add internal links, improve intro hook
Engagement Rate >60% 30-60% <30% Review content quality, add CTAs
Scroll Depth >75% 50-75% <50% Add visual breaks, improve structure
Pages/Session >2.5 1.5-2.5 <1.5 Improve internal linking

Google Search Console (GSC)

Metric Good Warning Poor Action When Poor
CTR >5% 2-5% <2% Improve title/meta description
Avg Position 1-3 4-10 >10 Strengthen content, build links
Impressions Trend Growing Stable Declining Refresh content, target new keywords
Mobile Usability PASS - FAIL Fix mobile issues immediately
Core Web Vitals GOOD NEEDS_IMPROVEMENT POOR Optimize performance

Interpreting Combined Signals

Traffic Quality Matrix

                    High Engagement
                          │
           ┌──────────────┼──────────────┐
           │  HIDDEN GEM  │   STAR       │
           │  Low traffic │   High traffic│
           │  High quality│   High quality│
           │  → Promote   │   → Maintain  │
Low ───────┼──────────────┼──────────────┼─── High
Traffic    │              │              │   Traffic
           │  UNDERPERFORM│   LEAKY      │
           │  Low traffic │   High traffic│
           │  Low quality │   Low quality │
           │  → Rework    │   → Optimize  │
           └──────────────┼──────────────┘
                          │
                    Low Engagement

Read the full file on GitHub · 200 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 200 lines · 21 tokens per session scan A 0ebb066ce383

Subscribe to this mod's changes

analytics-interpretation is a skill published in the GitHub repository nicepkg/ai-workflow (282 stars, last pushed 7mo ago), licensed MIT. It adds 21 tokens to every session and 1,493 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.