web-stats

Generates privacy-respecting web traffic reports from server access logs without cookies or third parties.

2|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/odysseyalive/claude-watchman --skill web-stats-odysseyalive
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: web-stats
Source: https://github.com/odysseyalive/claude-watchman/tree/main/skills/rhetoric/web-stats
Command: npx skills add https://github.com/odysseyalive/claude-watchman --skill web-stats-odysseyalive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Website owners need traffic analytics but cannot use Google Analytics or similar trackers without privacy and GDPR concerns. This Skill turns the access logs your web server already keeps into a useful traffic report with zero new data exposure. ## Core Features & Use Cases - Log-Based Analytics: Computes page views, unique visitors, total requests, bandwidth, top pages, top referrers, status-code mix, and daily trends directly from access logs (including rotated and gzipped files). - Privacy by Design: Client IPs are correlated in memory only and never stored, printed, or hashed, producing pure anonymous aggregates with no cookies, beacons, or third parties. - Bots vs Humans: Separates bot traffic from human visitors so the human page-view numbers stay trustworthy. - Use Case: Run /watchman stats on a multi-vhost server to get per-site traffic reports, spot a 404-heavy path worth fixing, or notice a spike in the daily trend — all without installing any tracking JavaScript. ## Quick Start Ask the assistant to run the web-stats report on this server's access logs and summarize the top pages, unique visitors, and bot-versus-human traffic split.

Frequently Asked Questions about web-stats

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get website analytics without Google Analytics?▼

Parse the access logs your web server already keeps for security purposes. This Skill computes page views, unique visitors, top pages, referrers, and daily trends from those logs with no cookies, JavaScript beacons, or third-party services.

How to analyze web server access logs for traffic stats?▼

Run the webstats engine via the dispatcher, which uses awk to aggregate current, rotated, and gzipped access logs. It reports page views, unique visitors, bandwidth, status-code mix, top referrers, and a daily trend, with per-vhost breakdowns for multi-site hosts.

Is log-based web analytics GDPR compliant?▼

Log-based analytics avoids the GDPR issues of trackers because it adds no new data collection. Client IPs are correlated only transiently in memory and are never stored, hashed, or printed, so the report contains only anonymous aggregates.

Does this analytics approach work with rotated or gzipped log files?▼

Yes, the log discovery step finds current access logs plus rotated and .gz compressed files. The awk-based engine processes all of them so historical traffic is included in the aggregates and daily trend.

What are the limitations of access-log-based analytics?▼

It cannot track client-side behavior like session duration or click paths that JavaScript trackers capture, and it deliberately never exposes individual IPs. Blocking abusive IPs is a separate security workflow, not part of this anonymized report.