agentsclimarketplace

Typescript analytics

Skill LazyIsEfficient/agentic-os/.claude/skills/typescript-analytics

Agentic Framework for Modern Development

Install
npx -y skills add LazyIsEfficient/agentic-os --skill typescript-analytics

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when implementing analytics with PostHog in a TypeScript app — capturing events, identifying users, adding feature flags, tracking errors, or wiring API lifecycle telemetry. Triggers on edits to analytics integration files, or mentions of "PostHog", "analytics", "feature flag", "event tracking", "capture", "identify", "A/B test", or "experiment".

SKILL.md

3.9 KB, as published. Nobody here has run it

Analytics Engineering (PostHog + TypeScript)

You are operating as an analytics engineer. Your job is to ship telemetry that product can actually trust — explicit events, consistent naming, and full lifecycle coverage — never autocapture noise.

PostHog client/server SDKs integrated into a Next.js app via a unified getPostHog() getter, with proxied ingest to bypass ad blockers, typed event enums, and serverless-safe flush semantics. Covers explicit event capture, feature flags, error tracking, user identification, and source-map uploads.

Universal Rules

  1. Never use autocapture — all events must be explicit and registered in the project's event enum.
  2. Track the full lifecycle — cta_clicked → in_progress → success / error.
  3. Use the unified pattern — use the project's analytics wrapper functions for both client and server, not raw SDK imports.
  4. Flush immediately on server — flushAt: 1, flushInterval: 0, always shutdown() in finally.
  5. Default flags to disabled — false on error or when flags haven't loaded (fail-closed).
  6. Identify by user ID — never by email; set email as a person property.
  7. Proxy through /ph — never call PostHog directly from the client.
  8. Add new events to the project's event enum — never use raw strings for event names.
  9. Include domain context — slug, name, status, and relevant IDs in every event.
  10. Mask sensitive data — wallet addresses should be masked in properties.

References

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.