2.6k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill agent-analytics- _meta.json2.2 KB
- SKILL.md36.6 KB
Overview
This skill adds lightweight, privacy-first analytics to any website so you can quickly know whether a project is alive and growing. It auto-tracks page views and lets you record 3–5 high-signal custom events, then query aggregated results via CLI or API. The focus is interpretation: the agent acts as your dashboard and surfaces trends, spikes, and issues.
How this skill works
Install a single client-side snippet that auto-sends page_view events and accepts a public project write token for custom events. Use the CLI or API with a read-only API key to fetch precomputed aggregations (insights, breakdowns, pages, sessions, heatmap). The skill interprets those responses into concise headlines and actionable recommendations rather than dumping raw numbers.
When to use it
- You want a quick alive-or-dead check for a project without full analytics overhead.
- You need simple, privacy-friendly tracking that’s safe to embed in client HTML.
- You want an agent to summarize weekly trends, top pages, and landing page quality.
- You manage many small projects and need a lightweight multi-project overview.
- You want automated anomaly detection (spikes, drops, inactive projects).
Best practices
- Track only 2–5 custom events in addition to page_view to avoid noise.
- Name properties in snake_case and use short descriptive ids (section_action).
- Use cta_click, signup, login, feature_used, checkout, and error as standard events when applicable.
- Verify with a manual test event and then confirm via CLI events output.
- Always call insights first when answering 'how is X doing' questions.
Example use cases
- Weekly report: run insights + top pages + entry pages and return a concise headline with trends.
- Quick health check: run insights --period 7d to see if traffic is growing, stable, or declining.
- Landing page audit: pages --type entry to compare bounce rates and average session duration.
- Launch timing: heatmap to find peak hours and low-traffic windows for deploys.
- Multi-project status: list projects and pull insights per project for a one-line summary each.
FAQ
Yes. The write token only writes to a single project, is rate-limited, revocable, and cannot read data.
What should I avoid tracking?
Avoid tracking every link, scroll depth, form field interactions, and footer clicks — they create low-signal noise.