PostHog
AnalyticsCommonly used with
Skills using PostHog (121)
analytics
Use when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing. NOT charting that data (that is dashboard), NOT choosing which metrics matter (that is kpi-framework), NOT experiment math (that is ab-testing), NOT cookie-policy text (that is gdpr-privacy).
clickhouse-analytics
Use when running a ClickHouse server for high-volume OLAP: choosing a MergeTree engine and ORDER BY/PARTITION BY keys, ingesting billions of event/log/metric rows, pre-aggregating with materialized views, or fixing a query that scans instead of pruning. NOT in-process file analytics (that is `duckdb`), NOT OLTP CRUD indexing (that is `postgresdb`).
add-custom-domain
Add a custom domain to a Temps project and provision an automatic SSL/TLS certificate via Let's Encrypt, driven entirely from the `@temps-sdk/cli` CLI. Handles subdomains, apex domains, HTTP-01 and DNS-01 challenges, and wildcard domains. Use when the user wants to: (1) Add a custom domain to their Temps app, (2) Set up HTTPS/SSL for a deployment, (3) Point their own domain at a Temps project, (4) Add a wildcard domain, (5) Configure DNS for Temps. Triggers: "add custom domain", "point my domain at temps", "set up ssl", "https for my app", "wildcard domain", "add domain to project".
add-error-tracking
Add Temps error tracking to applications using the Sentry-compatible SDK. Temps exposes a Sentry-compatible DSN that works with the official Sentry SDK for each language/framework — no code changes beyond initialization are required. Use when the user wants to: (1) Add error tracking to any app (React, Next.js, Vue, Svelte, Angular, Node.js, Python, Go, Rust, Ruby, Java, PHP, .NET, React Native, Flutter), (2) Wire up uncaught exception and unhandled promise rejection capture, (3) Configure session replay for errors, (4) Upload source maps for readable stack traces, (5) Report releases and environments, (6) Capture custom errors/messages. Triggers: "add error tracking", "add sentry", "track exceptions", "report errors", "temps error tracking", "wire up error monitoring".
add-node-sdk
Integrate the Temps Node.js SDKs for server-side platform access, KV storage, and Blob storage. Use when the user wants to: (1) Call the Temps platform API from Node.js (deployments, projects, analytics, session replay, etc.), (2) Use Temps KV (key-value) storage, (3) Use Temps Blob storage for files, (4) Server-side integration with a Temps project, (5) Backend access to Temps resources. Triggers: "temps node sdk", "temps kv", "temps blob", "backend integration", "node.js temps", "@temps-sdk/node-sdk".
add-react-analytics
Add Temps analytics to React applications with comprehensive tracking capabilities including page views, custom events, scroll tracking, engagement monitoring, session recording, and Web Vitals performance metrics. Use when the user wants to: (1) Add analytics to a React app (Next.js App Router, Next.js Pages Router, Vite, Create React App, or Remix), (2) Track user events or interactions, (3) Monitor scroll depth or element visibility, (4) Add session recording/replay, (5) Track Web Vitals or performance metrics, (6) Measure user engagement or time on page, (7) Set up product analytics or telemetry. Triggers: "add analytics", "track events", "session recording", "web vitals", "user tracking", "temps analytics", "react analytics".
add-session-recording
Add privacy-aware session recording and replay to React applications using the Temps SDK. Captures user interactions for playback while respecting privacy through input masking, element blocking, and GDPR-compliant consent flows. Use when the user wants to: (1) Add session recording to their app, (2) Implement session replay functionality, (3) Record user sessions for debugging, (4) Add privacy-compliant screen recording, (5) Debug user issues with visual replay, (6) Implement rrweb-based recording, (7) Set up GDPR-compliant session capture. Triggers: "session recording", "session replay", "record sessions", "user replay", "screen recording", "rrweb", "session capture".
deploy-to-temps
Deploy applications to the Temps platform with automatic framework detection, Dockerfile generation, and container orchestration. Supports Next.js, Vite, React, Node.js, Python, Go, Rust, Java, and C# applications. Use when the user wants to: (1) Deploy their app to Temps, (2) Set up CI/CD with Temps, (3) Configure deployment settings, (4) Create a Dockerfile for Temps, (5) Deploy a containerized application, (6) Set up automatic deployments from Git. Triggers: "deploy to temps", "temps deployment", "push to temps", "containerize for temps", "temps ci/cd".
estimate-temps-savings
Audit a project's infrastructure and SaaS stack, then produce a cost report showing what the user currently pays and what they would save by consolidating onto Temps (self-hosted or Temps Cloud). Detects hosting platforms (Vercel, Netlify, Railway, Render, Heroku, Fly.io), analytics (PostHog, Plausible, Mixpanel, Amplitude, Fathom), error tracking (Sentry, Bugsnag, Rollbar, Honeybadger), session replay (LogRocket, FullStory, Hotjar, Highlight), uptime monitoring (Pingdom, UptimeRobot, Better Stack, Checkly), managed databases (Supabase, Neon, PlanetScale, MongoDB Atlas, Upstash, RDS), and transactional email (SendGrid, Postmark, Resend, Mailgun) from dependencies, config files, and env var names. Use when the user wants to: (1) Know how much they would save by switching to Temps, (2) Audit their SaaS/infrastructure spend, (3) Compare their current stack's cost against self-hosting, (4) Decide whether Temps is worth it, (5) Build a business case for consolidating tools. Triggers: "how much would I save", "temp
start-temps
Start (or restart) a local Temps control plane built from this checkout, and the web dev server (`bun dev`) in `<checkout>/web`. Invoke when the user says "start temps", "restart temps", "launch the server", "kill and restart temps", or asks to bring the local server up after backend changes. Ports, database and data dir are allocated PER CHECKOUT (a "slot") so several worktrees/branches run side by side without killing each other or corrupting each other's schema — the first checkout you start in claims slot 0 (the familiar `:8080` / `:3000`); every other worktree gets its own slot and its own `temps_s<N>` database. Uses the `fast` cargo profile (release semantics, no debug symbols, parallel codegen) for quick rebuilds. Pass `split` (e.g. "start temps split", "/start-temps split") to launch the two-process proxy/console topology for testing that feature.
start-temps-cluster
Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + `temps agent`, wired with the real multi-host overlay (VXLAN, compute_cidr allocation) via `tools/dev-cluster/` in whichever checkout/worktree you run it from. Invoke when the user says "start the temps cluster", "spin up a multi-node dev cluster", "test this with multiple workers", "bring up worker nodes locally", "docker in dind cluster", or wants to verify cross-node behavior (node targeting, cluster DNS, overlay networking, node join/mTLS) that a single-node `start-temps` server cannot exercise. Distinct from `start-temps` (single-node, native binary, port-slot based) and `start-temps-ee` (single-node EE binary) — this is the only path that actually has more than one node.
temps
Manage, deploy, operate, and instrument applications with Temps. Use this skill whenever the user mentions Temps, `@temps-sdk/cli@0.1.36`, deploying or migrating an app to Temps, projects, environments, services, domains, backups, logs, monitoring, analytics, browser Performance Insights/Core Web Vitals, observability, error tracking, OpenTelemetry, tracing, session replay, or Temps Cloud. Also use it when preparing an application for production on Temps even if the user does not explicitly ask for the CLI. Route to focused references, proactively detect missing observability during create/link/deploy journeys, and use pinned `bunx` or `npx` CLI invocations with explicit target contexts.
temps-best-practices
Best-practices reference for preparing and instrumenting applications on Temps. Covers the app runtime contract (`.temps.yaml` health, HOST/PORT, readiness, SIGTERM, replicas, migrations) and production observability (errors, traces, metrics, logs, analytics, privacy, sampling, cardinality, credential boundaries). Use whenever building or reviewing an app for Temps, configuring health checks, adding telemetry, diagnosing missing/noisy signals, or checking OTLP/Sentry/analytics ingestion. Triggers include "temps best practices", "prepare this app for Temps", ".temps.yaml health", "temps health check", "ignore health checks in otel", "temps observability", "wire up telemetry", and "instrument this app for temps". Prefer focused setup skills for a single SDK. Use temps-cli for executing deploy and resource-management commands.
temps-cli
Operate Temps through the pinned `@temps-sdk/cli` package with bunx or npx. Use when the user mentions Temps CLI, `@temps-sdk/cli`, a CLI command, or asks to deploy, configure, inspect, automate, or administer Temps from a terminal. Covers contexts, projects, deployments, environments, services, domains, monitoring, backups, telemetry, browser Performance Insights/Core Web Vitals, Cloud, platform administration, and read-only managed-data browsing. Apply the target-context, secret-handling, confirmation, and verification rules for every agentic CLI operation.
temps-design-system
Classify a console screen (list/record/form), build it on @temps-sdk/ds templates and the shared shadcn primitives in @temps-sdk/ui, and follow the console's status vocabulary and status colour rules. Use for any new or changed console UI in web/src, and when building or extending web/packages/ds itself.
temps-mcp-setup
Configure Temps as an MCP (Model Context Protocol) server so AI assistants can interact with a Temps instance directly -- listing/inspecting projects and deployments, and (when write mode is enabled) triggering deployments with human confirmation. Use when the user wants to: (1) Set up the Temps MCP server, (2) Connect Claude Code/Desktop, Codex, Cursor, VS Code, Windsurf, or Zed to Temps, (3) Add Temps tools to an AI assistant, (4) Test the MCP wizard locally, (5) Manage multiple Temps MCP connections (dev, staging, prod, or several local dev slots) side by side. Triggers: "temps mcp", "configure temps tools", "add temps to claude", "temps ai assistant", "mcp server setup", "mcp add", "test the mcp wizard".
temps-platform-setup
Provision, verify, and connect a self-hosted Temps platform instance on an explicitly authorized machine. Use when the user wants an agent to install Temps with the official deploy script, configure a local CLI context, start browser device authorization, present the approval URL, wait for approval, or perform initial platform, DNS, TLS, user, and service setup without exposing credentials.
temps-plugin
Design, build, test, and distribute external Temps plugins with TypeScript/Bun; provide development and local-testing guidance for existing Rust plugins. Use for creating a plugin, adding an embedded console UI or deployment-event automation, testing host permissions and AI, installing from GitHub, or submitting a plugin to the public catalog. End-to-end publishing covers TypeScript GitHub-source plugins, not Rust native-package releases or in-process TempsPlugin backend crates.
privacy-check
Use to detect personal-data collection signals (email forms, payment fields, telemetry libraries) before shipping. Surfaces missing privacy notes. Not a legal review. Triggers on /privacy-check.
data-warehouse-experimentation
Running experiments out of the data warehouse instead of via dedicated experiment platforms. SQL-based assignment, exposure logging discipline, metric definitions in dbt models, statistical analysis in SQL or Python, variance reduction with CUPED, sequential testing, and the operational tradeoffs vs platforms like Statsig and Optimizely. Triggers on warehouse-native experimentation, run experiments in BigQuery, run experiments in Snowflake, dbt experiments, SQL t-test, CUPED variance reduction, exposure log, sample ratio mismatch, sequential testing, mSPRT, doubly robust estimation, build vs buy experimentation. Also triggers when the team is choosing between platform and warehouse, building warehouse-native experiment infrastructure, auditing one, or running an experiment with a custom metric the platform cannot handle.
experiment-design
A discipline for designing experiments (A/B tests, multivariate, holdouts) so the results actually answer the question you asked. Hypothesis writing, sample size, duration, segment analysis, running discipline, matching a result to a pre-committed decision rule, and the common failure modes that produce confidently wrong shipping decisions. Use this skill whenever the user is planning a test that has not run yet: framing a hypothesis, sizing the sample, setting duration, choosing guardrails, or deciding whether something is worth testing at all. Triggers on design an experiment, experiment plan, A/B test, split test, multivariate test, holdout, experiment hypothesis, sample size, minimum detectable effect, MDE, test duration, guardrail metric, no peeking, pre-committed decision rule, is this worth testing. Use `experimentation-analytics` instead when the test has already run and the question is how to read the result panel.
experimentation-platform-orchestrator
A platform decision framework for experimentation. When to use Statsig vs PostHog vs GrowthBook vs Optimizely vs Amplitude vs Eppo vs Kameleoon. How to migrate between them. How to coordinate when multi-platform is genuinely warranted. The decisions that compound for years and the ones you can defer. Triggers on which experimentation platform, choose Statsig vs PostHog, evaluate experimentation tools, switch experimentation platform, migrate from Optimizely, consolidate experimentation tools, multi-platform experimentation, experimentation platform decision, ab test platform selection, feature flag platform vs experiment platform, warehouse-native experiments, vendor lock-in experimentation. Also triggers when a team is asking about cost, governance, or migration cost across experimentation tools, or when an evaluation is starting.
feature-flagging
Operational discipline for feature flags as production infrastructure. Flag types, naming, targeting rules, rollout strategy, lifecycle, governance, stale flag management, and the technical debt patterns that bite teams who weren't deliberate about it.
site-launch-checklist
Pre-launch checklist for shipping a new website. Orchestrates analytics setup (GA4, PostHog, Google Search Console, Ahrefs), legal compliance, security headers and audit, SEO and GEO with keyword research validated against Google Trends (robots.txt, sitemaps, llms.txt, AI policy, schema markup, hreflang), copywriting consistency via a TONE.md and a humanizer pass in the matching language, OpenGraph and social previews, full favicon set with manifest, quality gates (Lighthouse, Core Web Vitals, WCAG accessibility, mobile testing), and setup of a weekly SEO agent. Use this skill whenever the user mentions launching a site/app, deploying a domain to production, pre-launch audit, shipping a marketing/docs/SaaS site or lead magnet, or says "checklist for the site", "ready to ship", "before I go live", "audit before launch", "ready for prod", or asks for a site review.
event-analytics
Customer event analytics across every GTM system — Intercom, Zendesk, Salesforce, HubSpot, Segment, Amplitude, Mixpanel, PostHog, and custom event pipelines. Covers event taxonomy design, tracking implementation, event-driven workflows, and unified customer views. Use when implementing event tracking, building a customer data pipeline, or designing event-driven GTM automations. Triggers on: "event analytics", "customer events", "event tracking", "product analytics", "Segment setup", "event pipeline".
tracking-plan
Master analytics tracking plan for PLG and B2B SaaS — unified event taxonomy, pixel strategy (1P and 3P tagging), marketing attribution architecture, CDP implementation (Segment, Rudderstack), product analytics (Amplitude, Mixpanel, PostHog), CRM tracking (HubSpot, Salesforce), and analytics infrastructure design. Use when building a complete tracking plan, designing analytics architecture, implementing product analytics, or aligning marketing and product tracking. Triggers on: "tracking plan", "analytics plan", "event tracking architecture", "pixel strategy", "analytics for PLG", "SaaS analytics".
data-telemetry-expert
Expert guide for observability, analytics, telemetry, and data pipelines (OpenTelemetry, PostHog, Mixpanel) / Panduan ahli untuk observabilitas, telemetri, dan analitik.
feature-flag-analytics-expert
Expert guide for Feature Flags & Progressive Rollout (PostHog, LaunchDarkly, GrowthBook), A/B testing orchestration, and canary releases / Panduan ahli Feature Flags, A/B testing, dan rilis bertahap.
review-logging-patterns
Review code for logging patterns and suggest evlog adoption. Guides setup on Nuxt, Next.js, SvelteKit, Nitro, TanStack Start, React Router, NestJS, Express, Hono, Fastify, Elysia, Cloudflare Workers, and standalone TypeScript. Detects console.log spam, unstructured errors, and missing context. Covers wide events, structured errors, drain adapters (Axiom, OTLP, HyperDX, PostHog, Sentry, Better Stack, Datadog), sampling, enrichers, and AI SDK integration (token usage, tool calls, streaming metrics, telemetry integration, cost estimation, embedding metadata).
feature-flags-audit
Audit and inventory all feature flags declared in the Packmind codebase. Use when the user asks to list, audit, review, or inventory feature flags, asks which flags are active, wants to know what a flag gates, or asks which flags are opened to a given domain/user. Produces a synthetic markdown table with each flag key, its audience, an inferred functional description, its active/orphan status, and its usage locations.
solo-legal
Use when "privacy policy", "terms of service", "legal pages", "GDPR", "CCPA", "app store legal", or project needs compliance documents. Do NOT use for NDA or contracts.
solo-metrics-track
Use when "set up metrics", "track KPIs", "PostHog events", "funnel analysis", "when to kill or scale", "success metrics", or need analytics plan. Do NOT use for SEO metrics (/seo-audit).
insforge-cli
Use this skill whenever someone needs a backend, or a task touches InsForge backend or cloud infrastructure through the InsForge CLI: projects, SQL, migrations, RLS policies, functions, storage, backups, deployments, compute, secrets, config, schedules, logs, diagnostics, advisor scans and suppressions, import/export, AI/OpenRouter setup and usage overview, Stripe/Razorpay payments, Apify web scraping / data sources, PostHog product analytics, backend branches, organization membership (invite, leave, delete), agent memory (remember/recall project facts and decisions), reporting InsForge-side bugs or doc discrepancies (feedback), or CLI docs. For app code with InsForge or @insforge/sdk, use the insforge app-integration skill instead.
analytics-product
Analytics de produto — PostHog, Mixpanel, eventos, funnels, cohorts, retencao, north star metric, OKRs e dashboards de produto.
posthog
Session replays, product events, error tracking, feature flags and HogQL over a connected PostHog project. Use when the user asks what a user did before a bug, for a session recording or replay, for product analytics, for who an exception hit, or about a feature flag's rollout.
ios-logging
Enterprise skill for iOS production error observability and logging (iOS 15+, Swift 5.5+). The trigger is OBSERVABILITY intent — the user wants errors captured and visible in production, not just handled. Use when: adding os.Logger or replacing print() with structured logging; setting up or integrating a crash SDK (Sentry, Crashlytics, PostHog); auditing error handling for silent failures (catch blocks with no Logger/ErrorReporter call, try? on network/auth/payment operations, Task {} with no do-catch, Combine .replaceError() killing error visibility); adding privacy annotations to logs; integrating MetricKit for OOM/hang detection; or asking why errors are disappearing silently in production. Also use when reviewing any catch block, try?, or Task {} specifically to ensure errors reach a remote crash reporting service — not just for writing error handling in general.
grimmemchat-log-search
(grim:mem:chat-log-search): (Chat Log Search): Search and summarize past Codex Desktop, Claude Code, and Cursor chat logs with layered detail (prompts, messages, final replies, tools, full). Use when asked to find prior conversations, prompts, decisions, tool calls, or to locate a session by keyword/date/session id.
analytics
Product analytics implementation — event tracking, funnel analysis, A/B testing, Segment/Amplitude/Mixpanel/PostHog, privacy-compliant instrumentation.
rum-tracking
Guides product analytics and RUM (Real User Monitoring) event tracking in web (React/Next.js) and mobile (React Native/Expo) apps. Decides what user interactions are valuable to capture, what's noise, what's PII to avoid, and how to implement, audit, update, and remove tracking code cleanly. Covers event naming, property schemas, tracking plans, GDPR/CCPA/DPDPA compliance, OpenTelemetry semantic conventions for browser and mobile RUM, and platforms (PostHog, Segment, Mixpanel, Amplitude, Datadog RUM, Sentry, OTel, Dash0). Modes: guide (default), implement, audit, remove, plan. Triggers on "track this event", "add analytics", "what should I track", "is this PII", "tracking plan", "remove tracking", "audit analytics", "/rum-tracking".
analytics-product
Analytics de produto — PostHog, Mixpanel, eventos, funnels, cohorts, retencao, north star metric, OKRs e dashboards de produto.
eve-registry-porting
Port a tool, connection or skill from a public eve/Flue agent registry — atomeve.dev, evex.sh, agentcn, eveagents.dev, the "shadcn for agents" registries — into a multi-tenant eve app WITHOUT adopting the registry's standalone-agent runtime model. Its core is the conformance checklist that makes third-party eve code tenant-safe. Use when the user wants to "install / use / borrow an agent from atomeve (or evex / agentcn / eveagents)", "add a Stripe/PostHog/Sentry/GitHub tool or connection from a registry", "reuse a skill from a shadcn-for-agents registry", or asks whether a registry agent is usable and how to adapt it. Not for: scaffolding a fresh tool/connection/skill slot (use `eve-agent`), building the Next.js app or its pages (use design-md-to-app / screenshot-to-page / module-add), or wiring the monorepo (monorepo-bootstrap).
business-investigation
Root cause analysis for business problems — why no signups, why churn, why stalled pipeline. Use when diagnosing WHY something is broken. For choosing between strategic options, use strategic-review instead.
metrics-briefing
CEO-level metrics interpretation through 9-category framework (market learning, product value, usage, pipeline, retention, B2C->B2B, execution, economics, PMF). For raw analytics data queries, use your analytics skill (e.g., posthog-analytics) instead.
posthog-analytics
Raw PostHog data queries via MCP — event catalog, query recipes, dashboards, funnels, experiments. Use for specific data questions. For CEO-level metric interpretation and frameworks, use metrics-briefing instead.
geo-master
Complete GEO (Generative Engine Optimization) audit, implementation, and monitoring system. Battle-tested on a real SaaS product that achieved DAU 2x growth in 7 days. Use when user wants to optimize for AI search engines (ChatGPT, Perplexity, Google AI Overviews, Gemini, Claude, Copilot), get cited by LLMs, improve AI visibility, or audit their GEO implementation. Triggers on: 'GEO', 'AI SEO', 'AEO', 'LLMO', 'AI visibility', 'llms.txt', 'AI citation', 'answer engine', 'generative engine', 'optimize for ChatGPT', 'AI Overviews', 'get cited by AI', 'AI crawler', 'AI search ranking'.
api-analytics-posthog-analytics
PostHog event tracking, user identification, group analytics for B2B, GDPR consent patterns. Use when implementing product analytics, tracking user behavior, setting up funnels, or configuring privacy-compliant tracking.
feature-flags
Feature flags and toggles management. Trigger when the user wants to implement feature flagging, A/B testing, or progressive deployment.
api-analytics-setup-posthog
PostHog analytics and feature flags setup
saas-analytics
SaaS uygulaması için PostHog analytics ve ürün analizi kur. Event tracking, kullanıcı tanımlama, feature flag, session replay, funnel analizi ve gizlilik uyumlu yapılandırma. Bu skill'i kullanıcı analytics, PostHog, event tracking, kullanıcı davranışı, feature flag, A/B test, dönüşüm analizi veya metrik takibi ile ilgili bir şey istediğinde kullan. "Analytics kur", "kullanıcıları takip et", "PostHog ekle", "feature flag yap" gibi ifadeler tetikler.
saas-launcher
Sıfırdan production-ready bir SaaS uygulaması kur. Ödeme, kimlik doğrulama, veritabanı, e-posta, landing page, SEO ve API güvenliği dahil tüm katmanları kapsar. Kullanıcı SaaS kurmak, web uygulaması başlatmak, AI aracı oluşturmak veya online ürün çıkarmak istediğinde bu skill'i kullan — "startup kur", "proje başlat", "uygulama yap" gibi ifadeler dahil. Mevcut bir projeye tek bir katman eklemek (sadece ödeme, sadece auth vb.) için ilgili alt skill'e yönlendir.
ccc-data
complete data ecosystem — 8 skills in one. Data pipelines, SQL optimization, visualization, machine learning, data quality, analytics, reporting, and vector search.
ccc-harden
Production hardening audit across 11 pillars (Vercel, GitHub, Sentry, PostHog, Stripe, Cloudflare, Secrets/PII). Read-only; --fix applies safe auto-fixes. Use pre-launch. NO PII.
structured-log
Write structured entries to daily memory log with facts, concepts, and files — use after any meaningful work, research, or decision
ai-persona
Create, replace or adjust a consistent AI-generated persona (the recurring face of a UGC account, a carousel series or a video ad) and verify it with a test shot through the real pipeline prompt. Covers the dense English face description, the reference portrait sent as an image on every face shot, the "plain but pretty, girl or boy next door, not a model" calibration, adults only, generating two portraits for the user to pick, and the known pitfalls (a phone drawn in the frame, the too-beautiful AI face, the too-tired face, identity drift). Use it whenever the user wants "a girl" or "a guy" for an account, a reference face, a portrait, asks to make someone "prettier", "plainer", "blonde", "less tired", starts a new selfie-style account, wants the same person across several images, or complains that a generated person "looks AI", even if they never say "persona" or "face reference".
app-store-metadata
Write, translate, check and publish the text of an iOS App Store listing (app name, subtitle, keywords field, description, promotional text, release notes / whatsNew, marketing, support and privacy URLs) for every locale, from one JSON file per locale kept in the repo, with a dependency-free script that checks Apple's limits and ASO rules offline, diffs against App Store Connect, pushes only after an explicit OK, and verifies. Use it whenever the user wants to change the App Store title or subtitle, rewrite the description, add or translate a store language, update promo text or release notes, "push the metadata", "sync the listing", prepare the listing for a new version, or asks why an App Store Connect edit is refused, even if they never say "metadata" or "App Store Connect API". Not for screenshots (app-store-screenshots), keyword research (aso-keywords), builds or submitting for review.
app-store-screenshots
Plan, produce, translate and check iPhone and iPad App Store screenshot sets that App Store Connect accepts - the right pixel sizes (6.5-inch 1284x2778 or 1242x2688, iPad 13-inch 2048x2732), locale coverage and inheritance, translated captions checked visually per language, and no unverifiable claims that App Review can reject. Use it whenever the user talks about App Store screenshots, store slides, captions, "redo the screenshots in Italian", an upload refused for its size, or a new screenshot series, even if they don't say "screenshots". If the project has its own screenshot pipeline, this skill follows it. Not for the app preview video or for the listing text (app-store-metadata).
apple-search-ads
Run Apple Search Ads (Apple Ads, ASA) campaigns through the Campaign Management API v5 with a bundled read-only CLI - campaign status and serving reasons, impressions / taps / installs / spend, CPT and CPI, per-country and per-day reports, keyword and search-term reports, negatives, plus documented payloads to create manual campaigns (exact / broad keywords, Search Match discovery, Search tab, product pages), pause, relaunch, change budgets and bids after an explicit yes. Use it whenever the user mentions Apple Ads, Search Ads, ASA, App Store ads, an auto campaign that doesn't deliver, Apple keywords, CPT, paid installs, "pause / relaunch / raise / lower the Apple campaign", or asks what their App Store ads cost, even if they don't say "API". Not for ChatGPT or TikTok ads (sibling skills), not for the App Store listing's own ASO keywords, and not for judging the in-app funnel (posthog-growth:posthog-paid-funnel). There is no Apple Ads MCP server; don't look for one.
aso-keywords
App Store keyword research (ASO) with the free, open-source aso-mcp MCP server - where the app ranks for each query and country, who leads and with how many ratings, keyword gaps against competitors, off-intent queries to drop, and concrete swaps for the name, subtitle and 100-character keywords field, then measuring the effect a few weeks after release. Use it whenever the user asks "what keywords should I use", "why doesn't my app show up in search", "analyze my competitors on the App Store", "ASO audit", "which title / subtitle", "are my keywords good", wants to enter a new country, or is about to change the listing text, even if they never say "ASO". Not for writing and pushing the listing itself (app-store-metadata) nor for Apple Search Ads bidding.
chatgpt-ads
Run ChatGPT Ads (OpenAI Ads Manager) campaigns through the OpenAI Advertiser API with a bundled stdlib Python CLI - campaign status, spend, impressions, clicks, CPC, attributed conversions, pixel health, pause, activate, daily budget, attach conversion events, and create a per-country campaign with localized ad copy and UTMs. Use it whenever the user mentions ChatGPT ads, OpenAI Ads, Ads Manager, sponsored answers in ChatGPT, the oaiq pixel, CPC or budget on ChatGPT, "pause / relaunch / lower / prepare the campaign", or asks what their ads cost this week, even if they don't say "OpenAI" or "API". Not for Apple Search Ads or TikTok (sibling skills), not for installing the pixel in site code, and not for judging the funnel in analytics (posthog-growth:posthog-paid-funnel). There is no OpenAI Ads MCP server; don't look for one.
decision-model-batch
Run massive closed questions (classify, filter, tag, route, score, yes/no, link or not) over hundreds or thousands of items at near-zero cost with a typed decision model instead of a text LLM - Jev by TypeSafe through OpenRouter (`typesafe/jev-1.13`, endpoint POST https://openrouter.ai/api/alpha/decisions, not chat/completions). Covers the exact call format, the three question types (noul, choice, score), how to write questions, stacking dozens of questions per call, calibrating on a sample then deciding in code with explicit thresholds, caching raw probabilities, cost and throughput, and the pitfalls. Use it whenever a task is "the same closed question N times", when the user mentions Jev, TypeSafe or a decision model, or complains about what an LLM costs on a bulk job, even if they just say "classify all these" or "filter this list".
image-prompt-porting
Port an external photoreal image prompt (a viral JSON prompt from a tweet, another creator's "photorealistic" template, a prompt pasted by the user) into your own image pipeline, or add a new shot type (camera angle, framing, face shot) to it. Keeps the structure that makes these prompts work (subject, pose, wardrobe, setting, light, camera, realism, micro-details, negatives, priorities, output), replaces the domain content, adds your invariants (no readable text or logos, camera never visible, one light source, calm zone for overlay text), keeps the JSON valid after placeholder filling, keeps prompts in files instead of code, and walks the checklist so the new shot type is actually used by the pipeline. Use it whenever the user shares an image prompt or a link to one and says "take inspiration", "rework ours like this", "use this style", or asks for a new angle, framing or photo style for carousels or ads, even if they never say "prompt" or "shot type".
paid-ads-setup
Create or refresh the project's paid-ads config, a short private markdown file (.claude/paid-ads-config.md) that holds everything the ads skills need to know about this project - which ad platforms are used, account / org / app / pixel ids, landing URL and locales, UTM conventions, budgets and approval rules, copy rules, the campaign table and its history, cost benchmarks already observed, and where credentials live (never the secrets themselves). Use it the first time someone asks anything about their ChatGPT Ads, Apple Search Ads or TikTok Ads in a project that has no such file, when the user says "set up my ads", "configure paid ads", "connect my ad accounts", or when another ads skill finds a missing fact. The chatgpt-ads, apple-search-ads and tiktok-ads-manager skills read this file instead of guessing.
posthog-experiment-reader
Read a PostHog A/B test or feature flag split honestly at indie-hacker volumes - "can I call it?", "did the variant win?", "should I ship this paywall / pricing / onboarding change?", "is the new version better than the old one?" - by checking the setup (exposures per variant, sample ratio mismatch, people in both arms), pulling per-variant exposures and conversions, computing absolute and relative lift with its margin of error, flagging peeking, short runs and mix-shift, reading replays per variant, and returning a verdict (ship, wait until N, redesign, investigate) instead of a false positive. Also use it for informal before/after comparisons of two versions when the user asks whether a change "worked". Not for designing a new experiment from scratch.
posthog-funnel-map
Build or refresh the funnel map of a PostHog project, a short markdown file (.claude/posthog-funnel-map.md) that holds the business profile (model, price, traffic, what "converted" means), the real event names of each funnel step, the goals, dashboards and insights that already exist, the UTM conventions, the feature flags, the noise to exclude (bots, app reviewers, internal accounts) and what PostHog cannot see. Use it the first time someone asks for any PostHog funnel, conversion, replay, experiment or paid-traffic analysis in a project that has no funnel map yet, when the user says "set me up", "map my funnel", "set up PostHog analysis", "what are my events", or when an investigation finds an event missing from the map. Every other skill of this plugin reads this file instead of guessing.
posthog-investigation
Investigate what happened to a product's funnel over a period with PostHog, and name the one bottleneck with evidence. Reads the dashboards and goals the founder already built, rules out false alarms (incomplete period, normal variance), walks a list of causes (deploy, flag, traffic mix, tracking bug, new vs returning users, device, outage), finds who dropped and where they went instead, reads event timelines, session replays and heatmaps of representative visitors, compares before and after a deploy, cross-checks on a control segment, and writes a prioritized report with a confidence level. Use it whenever the user asks "why no conversions / no sales / no signups", "what happened in the last 24-72 h", "conversion dropped", "analyze my sessions / replays / dashboard / traffic", "is the new onboarding working", "did the deploy break something", or has just turned on ads, even if they never say "funnel". For one paid campaign judged by its UTMs, use posthog-paid-funnel; for an A/B test, posthog-experiment-reade
posthog-paid-funnel
Judge a paid campaign or channel (Google Ads, Meta, TikTok, Apple Search Ads, ChatGPT Ads, Reddit, newsletters, influencers…) by what its visitors actually do in the product, using PostHog filtered on utm_source / utm_campaign - visitors, CTA clicks, signups, paywall, checkout, paying customers, cost per signup and per customer - and read the replays of paid visitors who dropped. Use it whenever the user asks "is this campaign converting", "how many signups / customers come from the ads", "why do clicks give nothing", "was it worth it", "should I kill this campaign", including when the ad platform already shows conversions - platform numbers are flattering, only the product analytics follow people to the payment. For a broad "what happened this week" across all sources, use posthog-investigation.
posthog-weekly-brief
Produce a short recurring growth brief from PostHog (daily or weekly) for a solo founder - traffic, signups, paying customers, funnel rates, sources, errors, experiments - scored against the product's own recent baseline, reporting only what moved beyond normal variance, with links to the replays that explain it. Keeps a watchlist of flows and baselines in a file so each run is cheaper and compares like with like. Use it when the user asks for "a weekly brief / morning brief / growth report", "what moved this week", "keep an eye on my funnel", or wants a scheduled task or routine that reports on PostHog. If a number looks alarming, it hands off to posthog-investigation instead of speculating.
pseo-internal-linking
Internal linking for programmatic SEO sites with thousands of generated pages (lessons, glossaries, city pages, recipes, docs) - candidate retrieval in code (TF-IDF plus labels of other pages already written in the text), a cheap decision model answering two closed questions per candidate, deterministic decisions in code (thresholds, caps, same language, closest level), links placed at render time only on anchors that already exist in the text, a cached audit you can re-tune for free, a report to read before applying, and the sitemap rule that keeps thin pages out. Use it whenever pages are generated or regenerated, a new language or country is added, or the user talks about internal links, orphan pages, "related articles", previous / next links, link juice, "Discovered, currently not indexed", or the sitemap of generated pages, even if they only say "relink the new pages" or "rerun the interlink".
tiktok-ads-manager
Drive TikTok Ads Manager from a browser tool (the built-in browser pane or Claude in Chrome) for an indie app - register the app in Events Manager, create or edit an iOS app-install campaign, add videos to an existing ad for a hook test, go through a pre-publish checklist, publish only after an explicit yes, read results per video (6-second view rate, CTR, CPM, SKAN installs) and cross them with product analytics. Use it whenever the user talks about TikTok ads, launching / updating / analyzing TikTok campaigns, adding a creative to an ad, TikTok budget or results, "how are the TikTok ads doing", even if they don't say "Ads Manager". No TikTok API or MCP is assumed; everything happens in the browser where the user is already signed in.
ugc-video-ad
Produce or iterate a 9:16 UGC-style video ad (TikTok, Reels, Shorts) with AI personas and no video SaaS - persona, still photos, image-to-video clips through an API (for example Kling via the OpenRouter video endpoint), a deterministic HTML timeline rendered frame by frame with Playwright, then H.264 with music and synthesized sound design through ffmpeg. Includes the creative rules learned from real campaigns (nobody talks, no breathing or sighing, plain faces, a new setting and topic per video, product only at the end, three hooks per persona, caption safe zones, AI-content disclosure) and the ffmpeg contact-sheet commands to check frames before rendering. Use it whenever the user talks about a video ad, a TikTok or Reels creative, UGC video, a new variant or hook, a new persona for an ad ("a student", "a mom"), a low 6-second view rate, or says a video "looks AI", even if they don't name the pipeline.
checkout-audit
Audit an ecommerce checkout flow against the 2026 conversion playbook. Triggers: "checkout audit", "checkout optimization", "Shopify checkout", "Stripe checkout", "Apple Pay".
analyze-posthog-usage
Query PostHog product analytics with read-only HogQL, explore anonymous user activity and journeys, model feature adoption and cross-feature behavior, audit instrumentation quality, and turn evidence into product hypotheses. Use when Codex needs to answer whether a product still has users, what users do before or after an event or surface, which features or combinations they use, how internal and external usage differ, whether an analytics event model is sufficient, or what product and instrumentation questions to investigate next.
analytics-product
Analytics de produto — PostHog, Mixpanel, eventos, funnels, cohorts, retencao, north star metric, OKRs e dashboards de produto.
launch-strategist
Plan and execute the launch — Product Hunt, Hacker News, X/Twitter, LinkedIn, newsletters, communities — sequenced for compounding signal.
metric-framework-designer
Define the measurement framework BEFORE launch. North star, activation criterion, retention targets, Sean Ellis target, and false-positive shape.
pricing-optimizer
Iterate pricing post-PMF based on real data — willingness to pay, expansion revenue, packaging tweaks, annual upsell, enterprise pricing.
retention-analyst
Analyze retention curves, identify churn drivers, and propose interventions. Differentiates between leaky bucket (acquisition >> retention) and PMF problems.
scaffold
One-shot a new product — folders, Next.js starter, product.config.json, CLAUDE.md, scope.md, PRD skeleton, SETUP.md checklist. The Lovable-like ignition.
support-triage
Triage incoming support — categorize, prioritize, draft responses, identify product bug vs user-error vs feature-request. Routes to engineering when needed.
telemetry-aggregator
Pull metrics across all products into a single view. Powers the dashboard and the daily/weekly briefings.
observability-and-growth
Full instrumentation from day one. PostHog consolidates product analytics + feature flags + error tracking (one platform, one bill). GA4 via GTM (14-step automation, custom dimensions over events, server-side tagging). Sentry (deep error tracking + performance). Stripe (webhook-first with idempotent processing). Listmonk on Coolify (newsletters via Amazon SES SMTP relay). PLG 7-layer framework. Programmatic SEO (5 page types). Incident auto-remediation via Sentry→Inngest pipeline. AI search (GEO) awareness. Local business conversions (phone_click, direction_click, form_submit, booking_click) with CRO patterns for both SaaS and local.
cluster-link-validator
Validates the internal link topology of a content cluster before publish. Confirms every spoke links back to the pillar, the pillar links to every spoke, anchor text is descriptive and keyword-rich, and no external competitor links have leaked through. Use this skill after the writer has produced posts and the quality-checker has passed them, but before publish. Trigger on phrases like "validate links", "check the link topology", "audit cluster links", "is the cluster bidirectional", "are there any broken internal links", or any handoff that asks for the link-level gate before publishing. This skill produces a pass/fail report and does not edit content. The blog manager or writer fixes any issues before publish.
cluster-orchestrator
Master orchestrator for building complete SEO content clusters for competitor comparisons of the product described in product-context.md. Use this skill whenever the user asks to build a content cluster, run the cluster system, create a "[Product] vs [Competitor]" content set, build a comparison cluster, run the hub-and-spoke playbook, or starts a request with "{{PRODUCT}} vs", "[Product] vs [Competitor]", "build cluster for", "compete with", or "[Competitor] alternatives cluster". This skill reads the cluster name from the user, confirms scope, and then orchestrates the full chain of cluster skills (planner, writer, quality-checker, visual-designer, link-validator, performance-tracker, performance-optimizer) by telling Claude which skill to invoke at each stage. The blog-manager-sop is a static reference doc, not invoked. Trigger this skill aggressively for ANYTHING related to building a competitor comparison content cluster. This is the master skill, so do NOT invoke individual cluster skills directly when
cluster-performance-optimizer
Analyzes published cluster posts against fresh GSC performance data and outputs specific, actionable change recommendations to improve rankings and AEO citations. Use this skill after the performance-tracker has produced a 15-day report, when the blog manager asks "what should we change to improve [post/cluster]", when a post has been flagged as significantly degraded, or when a cluster has had 3+ stable cycles and the team wants to push gains further. Trigger on phrases like "optimize this post", "what changes will improve ranking", "AEO recommendations", "GSC-based optimization", "improve cluster performance", or any request to translate GSC data into editorial action. This skill produces recommendations only. It does not edit content. The blog manager implements minor changes; the cluster-writer handles major rewrites.
cluster-planner
SERP analyst and content planner for competitor comparison clusters ({{PRODUCT}} vs {Competitor}). Use this skill when the orchestrator delegates planning, OR when the user asks to "plan a cluster", "research SERPs for", "do keyword research for", "analyze competitors for", "build a content plan for", or wants a content brief for a competitor comparison topic. This skill performs deep SERP analysis on parallel competitor pairs (since head-to-head {{PRODUCT}} vs X queries usually have no organic data), pulls People Also Ask, identifies content gaps, references the product's help center or knowledge base, and outputs a complete cluster plan as both markdown and a Google Sheets-compatible TSV tracker. It reads product-context.md for every product fact and runs a short intake to create it if missing. Trigger this skill aggressively for ANYTHING involving SERP research, content planning, keyword analysis, or hub-and-spoke architecture for competitor comparison clusters. The output is the input to cluster-writer, s
cluster-quality-checker
Audits cluster posts against the 13 strict PostHog template rules and outputs a pass/fail report with specific corrections. Use this skill after the writer hands off a draft and before the post goes to publish. Trigger on phrases like "QA this post", "quality check the pillar", "audit the listicle", "did the writer follow the rules", "run the checklist on these posts", or any handoff from the writer or orchestrator that asks for verification before publish. This skill does not rewrite content. It produces a structured report that the writer or human editor uses to fix issues. Trigger aggressively on any cluster post entering the QA stage.
cluster-visual-designer
Designs the small, specific set of visuals that a PostHog-style cluster post actually needs. Use this skill when the orchestrator hands off a written post (or set of posts) for visual treatment. Triggers on phrases like "design the visuals for the pillar", "generate the hero image", "create the CTA banner for this post", "visualize the cluster post", or any handoff from cluster-writer with a complete post. This skill follows PostHog's verified visual pattern (1 hero image per post, 1 product screenshot per main listicle entry, 2 repeated CTA promo banners, 1 newsletter banner). It does NOT produce infographics, decision trees, comparison flowcharts, or feature-section diagrams because PostHog does not. The output is SVG specs and image briefs that can be handed to a designer or rendered programmatically.
cluster-writer
Writes publish-ready posts for a {{PRODUCT}} SEO content cluster following the strict PostHog hub-and-spoke template. Use this skill whenever the orchestrator hands off a post type (pillar, alternatives listicle, migration guide, narrative, pricing explainer, 3-way comparison, B2B review, or category explainer) for a {{PRODUCT}}-vs-competitor cluster. Trigger on phrases like "write the pillar", "write the listicle", "write the migration guide", "write post 4 of the cluster", "draft the comparison post", or any handoff from cluster-orchestrator with a confirmed plan and SERP analysis. This skill codifies the strict line-by-line PostHog rules verified by direct fetches of posthog.com/blog/posthog-vs-mixpanel and posthog.com/blog/best-mixpanel-alternatives. Do not invent features, do not add quick-answer blocks, do not use years in headlines, do not link to external competitor sites. Every product claim must be documented in product-context.md.
seo-blog-writer
Produces top 1% on-page SEO blog posts for SaaS and B2B brands using the hub-and-spoke topic cluster model. Use this skill whenever the user asks to write a blog post, comparison post, alternatives post, listicle, product review, or any long-form content that needs to rank on Google. Also trigger on: 'write a blog', 'SEO blog', 'comparison post', 'alternatives post', 'vs post', 'best X tools', 'X vs Y', 'competitor comparison', 'topic cluster', 'pillar page', 'hub and spoke content', 'rank for keyword', 'on-page SEO', 'write content that ranks', 'blog post outline', 'SEO outline', 'content brief', or any request to produce a blog post optimized for organic search. Trigger aggressively -- if there is any mention of blog writing, SEO content, comparison content, or ranking for keywords, use this skill.
posthog_query
Turn a product or analytics question into the right PostHog query — trends, funnels, or retention — with the correct events, breakdowns, and date range.
mcp-per-project
Set up or fix per-project MCP isolation in Cursor and Claude Code, so concurrent agent sessions for different products (e.g. Acme vs Globex vs Initech) each get their own Railway, Postgres, Logfire, PostHog, etc. Use when the user mentions MCP bleed across projects, global mcp.json pollution, multiple Railway accounts/tokens on one machine, wants project-scoped MCP servers, or when onboarding a product repo (invoked from the onboard-repo skill).
onboard-repo
Onboard a Cursor repo into the hot-path/cold-path standards system: sync second-brain-workflow rules, add a thin always-apply onboarding rule, point at relevant second-brain practices, and wire project-scoped MCP (Railway / Postgres / Logfire / PostHog) — never global mcp.json. Use when the user says onboard repo, onboard this repo, set up cursor standards, sync rules into this project, or wire best practices into a new codebase. Covers quiet onboarding too — rendering into a repo you do not own, so the rules work locally and the remote never sees them: use when the user says render this quietly, keep it out of the remote, don't commit the rules, onboard someone else's repo, or local only.
awesome-design-md
Design guidelines and brand identity references from top companies. Use when researching design systems, brand identity, UI patterns, or visual language from companies like Apple, Figma, Framer, Nike, Tesla, Notion, Linear, Vercel, Stripe, and 60+ others.
analytics-review
Pull PostHog funnel metrics and Supabase/Postgres usage data, compare against previous baselines, and surface actionable insights. Use when the user asks to check analytics, review funnel, compare metrics, or see how users are doing.
hlzd-customer-profile
B2B 客户 360° 画像 —— 4 层字段模型（基础/交易/行为/画像）+ AI 跟进建议 + AI 客群聚合 + 5 维评级（A/B/C/D）。与 hlzd-customer-due-diligence 互补：due-diligence = 合规粗筛，customer-profile = 深度画像。
web-tracking-auditor
Audit a website's analytics and tracking deployment — verify that GA4, GTM, Adobe Analytics/Launch, Mixpanel, PostHog, server-side tracking (GTM SS, Segment), and ad pixels (Meta, TikTok, LinkedIn) are firing correctly, check consent/GDPR/CCPA/CPRA/UK PECR/LGPD compliance, detect suspicious or malicious tags, and produce a clean audit report plus a structured tracking plan. Use this skill whenever the user asks to audit, QA, validate, check, review, or troubleshoot tracking, tags, analytics, pixels, dataLayer, consent mode, GTM container, or a "tracking implementation" on any website — even if they don't say the word "audit." Also use when they hand over a URL and mention any analytics vendor, ask why their events aren't showing up, or want a tracking plan built from what's on their site. Also handles offline inputs — point it at a HAR file from Chrome/Firefox DevTools or a Google Tag Assistant "Export session" recording and it analyzes that instead of (or alongside) a live crawl, so trigger it whenever the u
saas-data-analysis
Comprehensive product and marketing analytics guide for developers and technical founders building SaaS products, developer tools/APIs, and enterprise software. Use this skill for any question about analytics setup, event tracking, conversion tracking, GA4, Google Tag Manager, Mixpanel, Amplitude, PostHog, Heap, Pendo, product metrics, marketing attribution, funnel analysis, cohort analysis, retention analysis, activation metrics, pirate metrics (AARRR), defining KPIs, building dashboards, connecting marketing data to product data, understanding which acquisition channels produce the best customers, or figuring out what to measure and how. Trigger whenever a user asks about setting up analytics, choosing analytics tools, understanding their metrics, tracking user behavior, measuring product-market fit, analyzing funnels, or any data-driven decision-making for a SaaS product — even if they just say "I don't know what to track" or "my analytics are a mess."
tracking-plan-discovery
Walk any app hands-on and build or update a real product-analytics tracking plan from what you actually see. Use this whenever someone needs an event taxonomy, a tracking plan, a measurement plan, an analytics spec, an event dictionary, instrumentation for GA4 / Firebase / Amplitude / Mixpanel / Segment / PostHog, or wants to audit or extend tracking that already exists. Use it when the ask is "what should we track", "our analytics are broken", "we have no funnel data", "design the events for this feature", "map the user journeys", or "the dev team needs a spec". It drives an Android emulator, an iOS simulator, a browser or a Figma file, screenshots every surface, groups parameters into reusable attribute packs, grades every event by how strong the evidence for it actually is, and ships a phased, buildable Excel workbook with embedded screenshots. Works for any app in any industry. Reach for it even when the person only says "events" or "instrumentation" and has not used the words tracking plan.
posthog-voice
Write in PostHog's house voice and style – clear, specific, opinionated, funny, anti-corporate developer content. Covers blog posts, newsletters, docs, tutorials, changelogs, landing pages, handbook pages, UI microcopy, and social. Use this skill whenever the user asks to write like PostHog, mentions PostHog's style, voice, blog, or handbook, OR whenever they want developer-facing content that sounds human instead of corporate – dev tool blog posts, open-source docs, engineering deep-dives, changelogs, product announcements, developer marketing copy, or "make this sound less like a SaaS company wrote it." Also use when editing or reviewing existing copy for buzzwords, hedging, passive voice, or AI-slop tone, even if PostHog is never mentioned by name.
posthog_experiment
Set up a sound PostHog A/B experiment or feature flag rollout — hypothesis, primary metric, exposure, and a sample-size check before launch.
Showing top 100 of 121 skills using PostHog by quality score.
See all 121 skills via search →Integration detected automatically from skill content. Some results may be false positives.