本文へ移動
cccskills
無料GitHub で公開

typescript-analytics

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".

LazyIsEfficient/agentic-os
インストール方法を見る

含まれるファイル（8）

  • SKILL.md3.9 KB
  • references/error-tracking.md1.8 KB
  • references/event-tracking.md3.6 KB
  • references/feature-flags.md2.5 KB
  • references/properties-and-source-maps.md1.3 KB
  • references/setup-and-architecture.md4.6 KB
  • references/typed-analytics.md3.0 KB
  • references/user-identification.md1012 B

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

adversarial-claims-reviewer

無料

Use when adversarially reviewing a document that makes formal or technical claims — math derivations, physics papers, statistical analyses, benchmark reports, whitepapers. Inventories every equation and quantitative claim, verifies each AS NAMED in the text (never a paraphrase or a neighboring statement), and classifies VERIFIED / REFUTED / UNVERIFIABLE / VACUOUS. Triggers on "check this paper", "verify these claims", "is this derivation right", "review this proof", "audit this benchmark", "does the math hold up". For source-code review see code-review-and-quality; for skill/agent library audits see skill-library-review; for content quality scoring see content-ops.

日本語の概要は準備中です。原文の説明を表示しています。

LazyIsEfficient/agentic-os172026年7月17日 更新

autoresearch

無料

Run Karpathy-style autoresearch optimization on any content. Generates 50+ variants, scores with a 5-expert simulated panel, evolves winners through multiple rounds, outputs optimized version + full experiment log. Use when optimizing landing pages, email sequences, ad copy, headlines, form pages, CTA text, or any conversion-focused content. Triggers on "optimize this page", "run autoresearch", "score these variants", "A/B test this copy".

日本語の概要は準備中です。原文の説明を表示しています。

LazyIsEfficient/agentic-os172026年7月17日 更新

browser-testing-with-devtools

無料

Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.

日本語の概要は準備中です。原文の説明を表示しています。

LazyIsEfficient/agentic-os172026年7月17日 更新

code-review-and-quality

無料

Conducts multi-axis code review across correctness, readability, architecture, security, and performance. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Triggers on "review my PR", "review this diff", "code review", "review this changeset", "is this ready to merge", "pre-merge review".

日本語の概要は準備中です。原文の説明を表示しています。

LazyIsEfficient/agentic-os172026年7月17日 更新

codebase-cost-estimator

無料

Estimate the full development cost of an existing codebase from lines of code, architectural complexity, and team-composition overhead. Use for 'how much would this cost to build', 'what did this codebase cost', development-cost or build-cost estimates, calendar-time estimates, and Claude/AI ROI on a delivered codebase. Estimates by measured LOC and complexity, not by ticket volume.

日本語の概要は準備中です。原文の説明を表示しています。

LazyIsEfficient/agentic-os172026年7月17日 更新

content-ops

無料

Auto-assembles a domain-specific expert panel (7–10 experts), scores any content or strategy artifact against a typed rubric, and iterates until the aggregate hits 90+ (max 3 rounds). Use as a quality gate on copy, email sequences, landing-page drafts, strategy docs, charts, titles, or recruiting evaluations — or when another skill needs a final review gate on its output. Triggers on "expert panel this", "score this", "rate these variants", "quality check this", "panel review", "expert score", "evaluate this copy/strategy/page". For variant generation and multi-round conversion optimization see autoresearch; for live-URL CRO auditing see conversion-ops; for the scripted content-production pipeline see content-pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

LazyIsEfficient/agentic-os172026年7月17日 更新

LazyIsEfficient のスキルをすべて見る

このスキルの問題を報告する