‹ 首页

analytics

@clawic · 收录于 昨天 · 上游提交 2 天前

Deploy privacy-first analytics with correct API patterns, rate limits, and GDPR compliance.

适合你,如果需要部署隐私合规并带速率控制的分析系统

/ 通过 npx 安装 校验哈希
npx oh-my-skill add clawic/skills/analytics
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- clawic/skills/analytics
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify clawic/skills/analytics
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
14GitHub stars
~409最小装载
~409含声明引用
~442文本包总量
索引托管

怎么用

商店整理自技能原文 · 版本 f825206 · 表述以原文为准
它做什么

安装后,Claude 能指导部署隐私优先分析工具(Umami、Plausible、PostHog),包括正确 API 用法、速率限制和 GDPR 合规要求。

什么时候触发

当你请求部署或配置分析工具,或询问 Umami、Plausible、PostHog 相关问题时触发。

装好后可以这样说
Claude 会提供 API 密钥和网站 ID 配置。
Claude 会提醒 JSON 序列化和避免 PII。
技能原文 SKILL.md作者撰写 · MIT · f825206
Critical Implementation Gotchas

Umami API timestamps: Use milliseconds, not seconds. Date.now() in JS, int(time.time() * 1000) in Python.

Plausible API v2: Requires site_id parameter, NOT domain name. Get site_id from dashboard URL first.

PostHog events: Properties must be JSON serializable. Never pass DOM elements or functions.

Rate limits: Umami 600/hour, Plausible 600/hour, PostHog 1000/minute. Implement exponential backoff on 429.

Environment-Specific Setup

Development: ALWAYS use separate project/site for local testing. Production data pollution is irreversible.

Tracking domains: Never hardcode. Use env vars to switch between localhost and production.

Bot filtering: Enable in settings. Privacy tools have weaker bot detection than Google Analytics.

GDPR Compliance Gotchas

EU visitors need explicit consent even for privacy-first tools. Check IP geolocation before tracking.

Data retention: Set automatic deletion - Umami in Settings > Data, Plausible 30 days max, PostHog in project settings.

Cookie-free warning: Umami/Plausible don't use cookies but still need consent for EU visitors if collecting identifiers.

Runtime Safety

Verify script loads before sending events. Check for umami, plausible, or posthog globals first.

Never track PII (email, names, IP) in custom events. Violates privacy principles.

Batch PostHog events via /batch endpoint. Umami/Plausible require individual requests.

Authentication Patterns

Store API keys in environment variables only. Never hardcode.

Umami: Requires website ID + API key combination.

Plausible: Uses Bearer token authentication.

PostHog: Uses project-specific API key.

按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。