代理分析
- 作者仓库星标 2,964
- 作者仓库 buildwithclaude
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @davepoon · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 需要 · Vendor-specific
- 兼容的系统
- Windows
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 允许外网请求
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
npx @agent-analytics/cli experiments get exp_abc123
第 1 步:添加跟踪代码段
`create`命令返回带有您的项目令牌的跟踪片段 - 将其添加到`</body>`之前。它会自动跟踪包含路径、引荐来源网址、浏览器、操作系统、设备、屏幕尺寸和 UTM 参数的 `page_view` 事件。您不需要添加自定义 page_view 事件。
步骤 1b:发现现有事件(现有项目)
如果已设置跟踪,请检查哪些事件和属性键已在使用,以便匹配命名:
第 2 步:将自定义事件添加到重要操作中
在重要的元素上使用 `onclick` 处理程序:
步骤 2b:运行 A/B 实验
通过实验,您可以测试页面元素的哪种变体转换效果更好。整个生命周期是 API 驱动的——不需要仪表板 UI。
第 3 步:立即测试
添加跟踪后,验证其是否有效:
# Agent Analytics — Analytics your agent can actually use
You are adding analytics tracking using Agent Analytics — the analytics platform your AI agent can actually use. Built for developers who ship lots of projects and want their AI agent to track, analyze, experiment, and optimize across all of them.
**Website:** [agentanalytics.sh](https://agentanalytics.sh)
**GitHub:** [Agent-Analytics/agent-analytics](https://github.com/Agent-Analytics/agent-analytics)
**Docs:** [docs.agentanalytics.sh](https://docs.agentanalytics.sh)
## When to Use This Skill
- User wants to add analytics tracking to a website or app
- User wants to check how their projects are doing (traffic, conversions, engagement)
- User wants to run A/B experiments on headlines, CTAs, or flows
- User wants funnel analysis, retention cohorts, or traffic breakdowns
- User asks "how's my site doing?" or "are people visiting?"
## Philosophy
You are NOT Mixpanel. Don't track everything. Track only what answers: **"Is this project alive and growing?"**
For a typical site, that's 3-5 custom events max on top of automatic page views.
## First-time setup
**Get an API key:** Sign up at [agentanalytics.sh](https://agentanalytics.sh) and generate a key from the dashboard. Alternatively, self-host the open-source version from [GitHub](https://github.com/Agent-Analytics/agent-analytics).
If the project doesn't have tracking yet:
```bash
# 1. Login (one time — uses your API key)
npx @agent-analytics/cli login --token aak_YOUR_API_KEY
# 2. Create the project (returns a project write token)
npx @agent-analytics/cli create my-site --domain https://mysite.com
# 3. Add the snippet using the returned token
# 4. Deploy, click around, verify:
npx @agent-analytics/cli events my-site
```
The `create` command returns a **project write token** — use it as `data-token` in the snippet. This is separate from your API key (which is for reading/querying).
## Step 1: Add the tracking snippet
The `create` command returns a tracking snippet with your project token — add it before `</body>`. It auto-tracks `page_view` events with path, referrer, browser, OS, device, screen size, and UTM params. You do NOT need to add custom page_view events.
## Step 1b: Discover existing events (existing projects)
If tracking is already set up, check what events and property keys are already in use so you match the naming:
```bash
npx @agent-analytics/cli properties-received PROJECT_NAME
```
## Step 2: Add custom events to important actions
Use `onclick` handlers on the elements that matter:
```html
<a href="..." onclick="window.aa?.track('EVENT_NAME', {id: 'ELEMENT_ID'})">
```
### Standard events for 80% of SaaS sites
Pick the ones that apply. Most sites need 2-4:
| Event | When to fire | Properties |
|-------|-------------|------------|
| `cta_click` | User clicks a call-to-action button | `id` (which button) |
| `signup` | User creates an account | `method` (github/google/email) |
| `login` | User returns and logs in | `method` |
| `feature_used` | User engages with a core feature | `feature` (which one) |
| `checkout` | User starts a payment flow | `plan` (free/pro/etc) |
| `error` | Something went wrong visibly | `message`, `page` |
### What NOT to track
- Every link or button (too noisy)
- Scroll depth (not actionable)
- Form field interactions (too granular)
- Footer links (low signal)
### Property naming rules
- Use `snake_case`: `hero_get_started` not `heroGetStarted`
- The `id` property identifies WHICH element: short, descriptive
- Name IDs as `section_action`: `hero_signup`, `pricing_pro`, `nav_dashboard`
## Step 2b: Run A/B experiments
Experiments let you test which variant of a page element converts better. The full lifecycle is API-driven — no dashboard UI needed.
### Creating an experiment
```bash
npx @agent-analytics/cli experiments create my-site \
--name signup_cta --variants control,new_cta --goal signup
```
### Implementing variants
**Declarative (recommended):** Use `data-aa-experiment` and `data-aa-variant-{key}` HTML attributes. Original content is the control. The tracker swaps text for assigned variants automatically.
```html
<h1 data-aa-experiment="signup_cta" data-aa-variant-new_cta="Start Free Trial">Sign Up</h1>
```
**Programmatic (complex cases):** Use `window.aa?.experiment(name, variants)` — deterministic, same user always gets same variant.
### Checking results
```bash
npx @agent-analytics/cli experiments get exp_abc123
```
Returns Bayesian `probability_best`, `lift`, and a `recommendation`. The system needs ~100 exposures per variant before results are significant.
## Step 3: Test immediately
After adding tracking, verify it works:
```bash
# Click around, then check:
npx @agent-analytics/cli events PROJECT_NAME
# Events appear within seconds.
```
## CLI Reference
All commands use `npx @agent-analytics/cli`:
```bash
# Setup
login --token aak_YOUR_KEY # Save API key (one time)
projects # List all projects
create my-site --domain https://... # Create project
# Real-time
live # Live TUI dashboard across ALL projects
live my-site # Live view for one project
# Analytics
stats my-site --days 7 # Overview: events, users, daily trends
insights my-site --period 7d # Period-over-period comparison
breakdown my-site --property path --event page_view --limit 10 # Top pages/referrers/UTM
pages my-site --type entry # Landing page performance & bounce rates
sessions-dist my-site # Session engagement histogram
heatmap my-site # Peak hours & busiest days
events my-site --days 30 # Raw event log
sessions my-site # Individual session records
properties my-site # Discover event names & property keys
funnel my-site --steps "page_view,signup,purchase" # Funnel drop-off
retention my-site --period week --cohorts 8 # Cohort retention
# A/B experiments
experiments list my-site
experiments create my-site --name signup_cta --variants control,new_cta --goal signup
experiments get exp_abc123
experiments complete exp_abc123 --winner new_cta
```
## Which endpoint for which question
| User asks | Call | Why |
|-----------|------|-----|
| "How's my site doing?" | `insights` + `breakdown` + `pages` (parallel) | Full weekly picture |
| "Is anyone visiting right now?" | `live` | Real-time visitors across all projects |
| "What are my top pages?" | `breakdown --property path --event page_view` | Ranked page list |
| "Where's my traffic coming from?" | `breakdown --property referrer --event page_view` | Referrer sources |
| "Are people actually engaging?" | `sessions-dist` | Bounce vs engaged split |
| "When should I deploy?" | `heatmap` | Find low-traffic windows |
| "Where do users drop off?" | `funnel --steps "page_view,signup,purchase"` | Step-by-step conversion |
| "Are users coming back?" | `retention --period week --cohorts 8` | Cohort retention |
| "Which CTA converts better?" | `experiments create` + `experiments get` | A/B test lifecycle |
For any "how is X doing" question, **always call `insights` first** — it's the single most useful endpoint.
## Examples
Track custom events via `window.aa?.track()`:
```js
window.aa?.track('cta_click', {id: 'hero_get_started'});
window.aa?.track('signup', {method: 'github'});
window.aa?.track('feature_used', {feature: 'create_project'});
window.aa?.track('checkout', {plan: 'pro'});
```
## What this skill does NOT do
- No GUI dashboards — your agent IS the dashboard (or use `live` for a real-time TUI)
- No user management or billing
- No PII stored — IP addresses are not logged or retained. Privacy-first by design
章节与文件索引
按说明文件中的顺序排列。
何时使用此技能
理念
首次设置
第 1 步:添加跟踪代码段
步骤 1b:发现现有事件(现有项目)
文件/命令 -> create · data-token · </body> · page_view · onclick · cta_click · signup · method
内容校验值 -> df6b99f7d23a
当前原文的自动摘译,尚未人工审校。
何时使用此技能
用户想要向网站或应用程序添加分析跟踪 用户想要检查他们的项目的运行情况(流量、转化、参与度) 用户想要对标题、CTA 或流量运行 A/B 实验 用户想要漏斗分析、留存群组或流量细分 用户询问“我的网站表现如何?”或“有人来访吗?”
理念
你不是 Mixpanel。不要跟踪一切。仅跟踪以下答案:“这个项目还活着并且正在成长吗?”对于典型的网站,除了自动页面浏览之外,最多还有 3-5 个自定义事件。
首次设置
获取 API 密钥:在 agentanalytics.sh 上注册并从仪表板生成密钥。或者,从 GitHub 自行托管开源版本。如果项目还没有跟踪:
create命令返回项目写入令牌 - 将其用作代码片段中的data-token。这与您的 API 密钥(用于读取/查询)是分开的。