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.
npx skills add arturseo-geo/claude-code-skills --skill analytics-reportinggit clone --depth 1 https://github.com/arturseo-geo/claude-code-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/arturseo-geo/claude-code-skills/analytics-reporting)<a href="https://agentmods.dev/skills/arturseo-geo/claude-code-skills/analytics-reporting"><img src="https://agentmods.dev/badge/skills/arturseo-geo/claude-code-skills/analytics-reporting/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/arturseo-geo/claude-code-skills/analytics-reporting"><img src="https://agentmods.dev/badge/skills/arturseo-geo/claude-code-skills/analytics-reporting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00935 |
| Opus 5 | $0.00000 | $0.00467 |
| Sonnet 5 | $0.00000 | $0.00187 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
analytics-reporting 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics & Reporting Skill
When This Skill Activates
This skill loads automatically when you mention:
- analytics, reporting, traffic metrics, performance reports
- weekly reports, monthly reports, dashboards, data analysis
- traffic drops, traffic spikes, content performance, page performance
- user behavior, conversion analysis, cross-source data correlation
- why did traffic drop, what content is performing, performance anomaly detection
- trend analysis, root cause analysis, traffic investigation
- combined reporting, GSC + GA4 analysis, search traffic, organic traffic trends
- bounce rate analysis, engagement metrics, landing page analysis
- session analysis, revenue correlation, goal conversion
- heat maps, user journeys, content audit performance, traffic forecasting
- any multi-source data analysis and reporting task
Data Sources
Real-time APIs:
- Google Search Console API (impressions, clicks, CTR, position, queries)
- Google Analytics 4 API (property 528383456) — sessions, users, conversions, events
- PostgreSQL OpenSEO DB (100.87.191.9:5432) — internal metrics, backlinks, keywords
- Redis cache (100.87.191.9:6379) — geolab-links queue state, job timing
WordPress & VPS:
- WordPress REST API (thegeolab.net) — post metadata, publish dates, author
- VPS Service APIs (100.87.191.9):
- seo-intelligence (:3001) — rank tracking data
- geolab-links (:3002) — link profile, authority scores
- geolab-backlinks (:4000) — backlink snapshots, competitor data
- geolab-keywords (:4001) — keyword clustering, SERP features
- geolab-writer (:4002) — published content, performance tags
Core Responsibilities
- Multi-Source Correlation — Join data from GSC, GA4, PostgreSQL, WordPress, Redis using lag-aware joins and confidence scoring
- Anomaly Detection — Z-score, moving averages, seasonality adjustment, algorithm change detection, composite anomaly scoring
- Report Generation — Weekly summaries, monthly deep-dives, investigation reports, audit snapshots, page-level breakdowns
- Actionable Insights — Root cause analysis, content recommendations, traffic recovery strategies, opportunity detection
- Data Validation — Check data completeness, lag detection, source freshness, accuracy within confidence bounds
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 91 lines · 0 tokens per session scan A 83b355bd6559
analytics-reporting is a skill published in the GitHub repository arturseo-geo/claude-code-skills (11 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 935 tokens. 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.
Other skills, from other repositories
security-compliance
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and risk assessments, managing security operations and incident response, and embedding security throughout the SDLC.
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
stride-analysis-patterns
Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.
cache-components
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). PROACTIVE ACTIVATION: Use this skill automatically when working in Next.js projects that have cacheComponents: true in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best…
blind-spot-pass
Use before starting work in a domain you don't know well, to surface the "unknown unknowns" — the things you don't even know to ask about — and learn just enough to prompt and decide well. Implements the "blind spot pass" pattern from Anthropic's Fable "finding your unknowns" field guide. Triggers when you say "I'm…
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.