web-analytics
/web-analytics
Analyze Umami or GA4 traffic with evidence-backed specialist reviews and deliver a concise portfolio pulse, decision brief, or deep dive. Use when the user asks to check analytics, explain a traffic change, inspect funnels, compare site performance, or prepare an analytics report. Trigger with "/analytics", "check my analytics", "how's my traffic", "site stats", "traffic report", or "analytics brief".
- Author
- jeremylongshore ↗
- Repository
- tons-of-skills-marketplace ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Analyze Umami or GA4 traffic with evidence-backed specialist reviews and deliver a concise portfolio pulse, decision brief, or deep dive. Use when the user asks to check analytics, explain a traffic change, inspect funnels, compare site performance, or prepare an analytics report. Trigger with "/analytics", "check my analytics", "how's my traffic", "site stats", "traffic report", or "analytics brief".
Triggers from the description
Arguments
/web-analytics [mini|medium|full] [--site=name] [--period=7d] [--email] [--slack]
Original author description
Analyze Umami or GA4 traffic with evidence-backed specialist reviews and deliver a concise portfolio pulse, decision brief, or deep dive. Use when the user asks to check analytics, explain a traffic change, inspect funnels, compare site performance, or prepare an analytics report. Trigger with "/analytics", "check my analytics", "how's my traffic", "site stats", "traffic report", or "analytics brief".
How it works
- Overview
- Prerequisites
- Authentication and Safety
- Workflow
- Error Handling
- Output
- Examples
- Resources
SKILL.md preview
---
name: web-analytics
description: >-
Analyze Umami or GA4 traffic with evidence-backed specialist reviews and deliver a
concise portfolio pulse, decision brief, or deep dive. Use when the user asks to
check analytics, explain a traffic change, inspect funnels, compare site performance,
or prepare an analytics report. Trigger with "/analytics", "check my analytics",
"how's my traffic", "site stats", "traffic report", or "analytics brief".
allowed-tools: Read, Bash(date:*), Bash(curl:*), Bash(python3:*), Bash(source:*), Agent
version: 1.5.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
- analytics
- umami
- traffic
- reporting
- intelligence
argument-hint: '[mini|medium|full] [--site=name] [--period=7d] [--email] [--slack]'
compatibility: Designed for Claude Code
model: inherit
effort: high
user-invocable: true
---
# Web Analytics Intelligence
## Overview
Turn portfolio analytics into a decision-ready report by collecting a bounded dataset, preserving
the comparison window, separating observed facts from hypotheses, and routing deeper requests
through specialist agents. This is a push-based analysis workflow, not a dashboard replacement.
Read the [operating contract](references/operating-contract.md) before making authenticated
requests or delivering a report.
## Prerequisites
- Configure sites and thresholds in `${CLAUDE_PLUGIN_ROOT}/references/site-registry.md`.
- Store Umami credentials in the operator's approved secret store; this installation uses
`UMAMI_PASSWORD` from `~/.env`.
- Confirm `/email` or `/slack` independently before requesting those delivery channels.
- Use `${CLAUDE_PLUGIN_ROOT}/references/reporting-tiers.md` and
`${CLAUDE_PLUGIN_ROOT}/references/interpretation-guide.md` for medium and full reports.
## Authentication and Safety
1. Confirm the analytics base URL is the expected operator-controlled host before sending a
credential.
2. Load `UMAMI_PASSWORD` only for the command that needs it. Never print, log, persist, or pass
the password or bearer token to a specialist agent.
3. Use `curl --fail-with-body --silent --show-error`; stop if authentication fails or the token
is empty.
4. Treat email and Slack delivery as external side effects. Preview the destination and report,
and obtain confirmation when the user has not explicitly requested delivery.
5. Never send messages, modify analytics configuration, or write baseline state during a read-only
request. A full-tier memory update requires an explicit writable scope.
## Workflow
### 1. Parse the Request
| Parameter | Default | Accepted values |
|---|---|---|
| Tier | `mini` | `mini`, `medium`, `full` |
| Site | `all` | Registry name or `all` |
| Period | `7d` | `today`, `yesterday`, `7d`, `30d`, `mtd`, `qtd` |
| Delivery | `console` | `console`, `email`, `slack`, `all` |
| Compare | prior equivalent | An explicit comparison window |
Use defaults when they preserve the user's intent. Ask before continuing if the site, time window,
or external destination would materially change the result.
### 2. Load Configuration
Read only the files needed for the selected tier:
1. `${CLAUDE_PLUGIN_ROOT}/references/site-registry.md` for site IDs, baselines, and thresholds.
2. `${CLAUDE_PLUGIN_ROOT}/references/mcp-tool-reference.md` for supported data operations.
3. `${CLAUDE_PLUGIN_ROOT}/references/reporting-tiers.md` for output contracts.
4. `${CLAUDE_PLUGIN_ROOT}/references/interpretation-guide.md` for evidence language.
### 3. Collect the Minimum Dataset
For direct Umami access, authenticate and fail closed:
```bash
set -euo pipefail
source ~/.env
analytics_url="https://analytics.intentsolutions.io"
token=$(curl --fail-with-body --silent --show-error "${analytics_url}/api/auth/login" \
-X POST -H "Content-Type: application/json" \
-d '{"username":"admin","password":"'"${UMAMI_PASSWORD}"'"}' | \
python3 -c "import json,sys; print(json.load(sys.stdin).get('token',''))")
test -n "${token}" || { printf 'Umami authentication returned no token\n' >&2; exit 1; }
curl --fail-with-body --silent --show-error \
"${analytics_url}/api/websites/<site-id>/stats?startAt=<start-ms>&endAt=<end-ms>&compare=prev" \
-H "Authorization: Bearer ${token}"
unset token UMAMI_PASSWORD
```
Record the source, site, timezone, exact start and end timestamps, comparison window, and any
missing endpoint. Do not infer missing values as zero.
### 4. Route by Tier
- **Mini:** Collect aggregate stats and active visitors inline. Return totals, per-site metrics,
comparison deltas, and one material signal in at most 15 lines.
- **Medium:** Use `Agent` to run `data-collector`; after it returns, run `traffic-intelligence`,
`content-seo`, and `anomaly-detector` concurrently. Give `reporting-narrative` their outputs,
the exact period, and the requested delivery format.
- **Full:** Run `data-collector` for aggregate, event, technology, and geography data. Then run all
five analysis specialists concurrently, pass their claims to `verification-agent`, and compile
only verified or explicitly qualified findings with `reporting-narrative`.
Agent definitions live under `${CLAUDE_PLUGIN_ROOT}/agents/`. Give agents collected results, not
credentials. Bound every assignment to the requested sites and period. If an agent fails, report
that coverage gap and continue only when the remaining evidence can support the requested output.
### 5. Verify and Deliver
Before delivery, apply the [operating contract](references/operating-contract.md):
1. Recalculate headline deltas from the raw totals.
2. Label each statement as observation, comparison, hypothesis, or recommendation.
3. Check anomaly claims against baselines and low-volume noise.
4. Name unavailable sources and incomplete windows.
5. Preview external destinations, then invoke `/email` or `/slack` only when authorized.
For a full-tier report, run `memory-agent` only if the user authorized baseline-state updates.
Persist the period, source, and evidence receipt so a later report can reproduce the comparison.
## Error Handling
Stop without exposing secret material when authentication fails. For partial endpoint, site, agent,
or delivery failures, retain successful evidence, name the exact coverage gap, and avoid complete-
portfolio or trend claims that the remaining data cannot support. The operating contract defines
the required fallback for each failure class.
## Output
Return the tier, sites, exact period, comparison window, sources consulted, coverage gaps, and
delivery result. Lead with the strongest verified signal, show the supporting metrics, distinguish
hypotheses from facts, and end with prioritized actions that each have an owner or next check.
## Examples
- `/analytics --period=today` produces a mini console pulse for every configured site.
- `/analytics medium --site=tonsofskills --period=7d` explains material traffic and content shifts.
- `/analytics full --period=30d --email` previews an evidence-checked deep dive before email delivery.
## Resources
- [Operating contract](references/operating-contract.md) — auth, evidence, failure, and delivery gates.
- `${CLAUDE_PLUGIN_ROOT}/references/site-registry.md` — configured properties and thresholds.
- `${CLAUDE_PLUGIN_ROOT}/references/reporting-tiers.md` — detailed report schemas.
- `${CLAUDE_PLUGIN_ROOT}/references/interpretation-guide.md` — analytical voice and caveats.
- `${CLAUDE_PLUGIN_ROOT}/references/delivery-channels.md` — email and Slack adapters.
Files in this package (2)
- SKILL.md 7 KB
- references/operating-contract.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| devpilotX/ai-skill-ai | 98 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 89139c061775 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95analytics
Privacy-first analytics knowledge base - Plausible, PostHog, Umami, Vercel Analytics, cookie consent. Use when setting up analytics, tracking events, measuring conversions, or integrating analytics tools. - 90google-analytics-tool
When the user wants traffic data, conversion tracking, user behavior on location pages, GBP traffic attribution, or geographic traffic patterns. Trigger on "Google Analytics," "GA4," "traffic," "conversions," "how many leads," "phone calls," "form submissions," "where is my… - 100google-analytics
Pull GA4 reports, traffic data, and insights from the Google Analytics Data API. Use when asked about website traffic, user behavior, acquisition channels, conversions, or audience segments. Trigger phrases: "google analytics", "GA4", "traffic report", "analytics data", "user… - 95google-analytics-cli
Google Analytics 4 data analysis and reporting via google-analytics-cli. Use when the user wants to check GA4 traffic, run reports with dimensions and metrics, monitor realtime users, explore account structure, or analyze user behavior. Triggers: "Google Analytics", "GA4",… - 100google-analytics
Analyze Google Analytics 4 data — review website performance, identify traffic patterns, diagnose high-bounce pages, compare time periods, and suggest data-driven improvements. Use when the user asks about analytics, website metrics, traffic analysis, conversion rates, user… - 100google-analytics
Query Google Analytics 4 (GA4) reports via the Analytics Data API v1 and list properties via the Admin API. Use when the user mentions Google Analytics, GA4, website traffic / sessions / users, top pages or sources, conversions, or a realtime report.