Menu
Deploy privacy-first analytics with correct API patterns, rate limits, and GDPR compliance.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Reckless versus prudent categorization, tracking the inventory, and a payoff cadence that does not freeze delivery.
Scheduling review of material at expanding intervals to optimize long-term retention.
Orchestrates the announcement, assets, channels, and timing for shipping a product, covering the arc from teaser to launch day to post-launch momentum.
Logs, metrics, and traces as complementary signals, high-cardinality dimensions, and the instrumentation budget.
Writing objectives and key results, setting cadence, and avoiding common stretch-goal failures.
Set type for screen and print: measure, leading, tracking, optical sizes, weight axes, and the difference between display and text cuts.
| name | Analytics |
| description | Deploy privacy-first analytics with correct API patterns, rate limits, and GDPR compliance. |
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.
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.
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.
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.
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.
