Omnibus Instrument Product Analytics
PostHogOfficialCreated by PostHog
- Skill
- Tool integration
- Data and AI
- MIT
- Low risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured, step-by-step procedure for integrating PostHog product analytics into a wide variety of web, mobile, and backend frameworks. It handles the full lifecycle of the integration, from detecting the project's technology stack and installing the necessary SDKs to implementing event tracking, user identification, and error monitoring. The skill emphasizes non-intrusive changes, ensuring that new analytics code is added alongside existing logic without disrupting the project's architecture.
What it does
- Detects the project framework and language to determine the correct PostHog SDK.
- Installs the required PostHog SDK package automatically.
- Initializes the PostHog instance according to framework-specific best practices.
- Implements targeted event tracking for key user actions and business logic.
- Configures user identification flows for login and signup events.
- Sets up environment variables for secure API key and host management.
When to use it
- After implementing new features that require tracking for user engagement analysis.
- When reviewing pull requests to ensure critical user behaviors are being captured.
- When setting up product analytics for a new project from scratch.
- When migrating or adding analytics to an existing application.
Advantages
- Supports a broad range of modern frontend, backend, and mobile frameworks.
- Ensures consistent event naming and property capture across the codebase.
- Maintains architectural integrity by requiring minimal, targeted code additions.
- Automates the tedious aspects of SDK initialization and environment configuration.
Usage examples
- “Add PostHog analytics to my Next.js project.”
- The agent will detect the Next.js environment, install the PostHog SDK, initialize it in the appropriate root file, and guide you through adding capture calls to key user flows.
- “I need to track user signups in my Django application using PostHog.”
- The agent will identify the Django setup, configure the PostHog Python SDK, and implement identify calls within your authentication logic.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/posthog/omnibus-instrument-product-analytics/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip omnibus-instrument-product-analytics.zip -d .agents/skills
Documentation by PostHog
Add PostHog product analytics events
Use this skill to add product analytics events (capture calls) that track meaningful user actions in new or changed code. Use it after implementing features or reviewing PRs to ensure key user behaviors are captured. If PostHog is not yet installed, this skill also covers initial SDK setup. Supports any framework or language.
Supported frameworks: Next.js, React Router, Nuxt, Vue, TanStack Start, SvelteKit, Astro, Angular, Django, Flask, FastAPI, Laravel, Ruby on Rails, Android, iOS, React Native, Expo, and more.
Instructions
Follow these steps IN ORDER:
STEP 1: Analyze the codebase and detect the platform.
Look for dependency files (package.json, requirements.txt, Gemfile, composer.json, go.mod, etc.) to determine the framework and language.
Look for lockfiles (pnpm-lock.yaml, package-lock.json, yarn.lock, bun.lockb) to determine the package manager.
Check for existing PostHog setup. If PostHog is already installed and initialized, skip to STEP 5.
STEP 2: Research integration. (Skip if PostHog is already set up.) 2.1. Find the reference file below that matches the detected framework — it is the source of truth for SDK initialization, provider setup, and event capture patterns. Read it now. 2.2. If no reference matches, fall back to your general knowledge and web search. Use posthog.com/docs as the primary search source.
STEP 3: Install the PostHog SDK. (Skip if PostHog is already set up.)
Add the PostHog SDK package for the detected platform. Do not manually edit package.json — use the package manager's install command.
Always install packages as a background task. Don't await completion; proceed with other work immediately after starting the installation.
STEP 4: Initialize PostHog. (Skip if PostHog is already set up.)
Follow the framework reference for where and how to initialize. This varies significantly by framework (e.g., instrumentation-client.ts for Next.js 15.3+, AppConfig.ready() for Django, create_app() for Flask).
STEP 5: Plan event tracking.
From the project's file list, select between 10 and 15 files that might have interesting business value for event tracking, especially conversion and churn events.
Also look for files related to login that could be used for identifying users, along with error handling.
Find any existing
posthog.capture()code. Make note of event name formatting. Don't duplicate existing events; supplement them.Track actions only, not pageviews (those can be captured automatically). Exceptions can be made for "viewed"-type events at the top of a conversion funnel.
Server-side events are REQUIRED if the project includes any instrumentable server-side code (API routes, server actions, webhook handlers, payment/checkout completion, authentication endpoints).
STEP 6: Implement event capture.
For each planned event, add
posthog.capture()calls with useful properties.If a file already has existing integration code for other tools or services, don't overwrite or remove that code. Place PostHog code below it.
Do not alter the fundamental architecture of existing files. Make additions minimal and targeted.
You must read a file immediately before attempting to write it.
STEP 7: Identify users.
Add PostHog
identify()calls on the client side during login and signup events. Use the contents of login and signup forms to identify users on submit.If both frontend and backend exist, pass the client-side session and distinct ID using
X-POSTHOG-DISTINCT-IDandX-POSTHOG-SESSION-IDheaders to the server-side code. On the server side, make sure events have a matching distinct ID.
STEP 8: Add error tracking.
Add PostHog exception capture error tracking to relevant files, particularly around critical user flows and API boundaries.
STEP 9: Set up environment variables.
If an env-file-tools MCP server is connected, use check_env_keys to see which keys already exist, then use set_env_values to create or update the PostHog API key and host.
Reference these environment variables in code instead of hardcoding them.
STEP 10: Verify and clean up.
Check the project for errors. Look for type checking or build scripts in package.json.
Ensure any components created were actually used.
Run any linter or prettier-like scripts found in the package.json.
Reference files
references/EXAMPLE-next-app-router.md- next-app-router example project codereferences/EXAMPLE-next-pages-router.md- next-pages-router example project codereferences/EXAMPLE-react-react-router-6.md- react-react-router-6 example project codereferences/EXAMPLE-react-react-router-7-framework.md- react-react-router-7-framework example project codereferences/EXAMPLE-react-react-router-7-data.md- react-react-router-7-data example project codereferences/EXAMPLE-react-react-router-7-declarative.md- react-react-router-7-declarative example project codereferences/EXAMPLE-nuxt-3.6.md- nuxt-3.6 example project codereferences/EXAMPLE-nuxt-4.md- nuxt-4 example project codereferences/EXAMPLE-vue-3.md- vue-3 example project codereferences/EXAMPLE-react-tanstack-router-file-based.md- react-tanstack-router-file-based example project codereferences/EXAMPLE-react-tanstack-router-code-based.md- react-tanstack-router-code-based example project codereferences/EXAMPLE-tanstack-start.md- tanstack-start example project codereferences/EXAMPLE-sveltekit.md- sveltekit example project codereferences/EXAMPLE-astro-static.md- astro-static example project codereferences/EXAMPLE-astro-view-transitions.md- astro-view-transitions example project codereferences/EXAMPLE-astro-ssr.md- astro-ssr example project codereferences/EXAMPLE-astro-hybrid.md- astro-hybrid example project codereferences/EXAMPLE-angular.md- angular example project codereferences/EXAMPLE-django.md- django example project codereferences/EXAMPLE-flask.md- flask example project codereferences/EXAMPLE-fastapi.md- fastapi example project codereferences/EXAMPLE-python.md- python example project codereferences/EXAMPLE-laravel.md- laravel example project codereferences/EXAMPLE-ruby-on-rails.md- ruby-on-rails example project codereferences/EXAMPLE-ruby.md- ruby example project codereferences/EXAMPLE-android.md- android example project codereferences/EXAMPLE-swift.md- swift example project codereferences/EXAMPLE-react-native.md- react-native example project codereferences/EXAMPLE-expo.md- expo example project codereferences/next-js.md- Next.js - docsreferences/react-router-v6.md- React router v6 - docsreferences/react-router-v7-framework-mode.md- React router v7 framework mode (remix v3) - docsreferences/react-router-v7-data-mode.md- React router v7 data mode - docsreferences/react-router-v7-declarative-mode.md- React router v7 declarative mode - docsreferences/nuxt-js-3-6.md- Nuxt.js (v3.0 to v3.6) - docsreferences/nuxt-js.md- Nuxt.js - docsreferences/vue-js.md- Vue.js - docsreferences/tanstack-start.md- Tanstack start - docsreferences/svelte.md- Svelte - docsreferences/astro.md- Astro - docsreferences/angular.md- Angular - docsreferences/django.md- Django - docsreferences/flask.md- Flask - docsreferences/python.md- Python - docsreferences/posthog-python.md- PostHog python SDKreferences/laravel.md- Laravel - docsreferences/ruby-on-rails.md- Ruby on rails - docsreferences/ruby.md- Ruby - docsreferences/android.md- Android - docsreferences/ios.md- Ios - docsreferences/react-native.md- React native - docsreferences/identify-users.md- Identify users - docs
Each framework reference contains SDK-specific installation, initialization, and usage patterns. Find the one matching the user's stack.
Key principles
Environment variables: Always use environment variables for PostHog keys. Never hardcode them.
Minimal changes: Add PostHog code alongside existing integrations. Don't replace or restructure existing code.
Match the docs: Follow the framework reference's initialization and capture patterns exactly.
Files
- ATTRIBUTION.mdAdded by AutoGineer966 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md8.5 KiB
- references/EXAMPLE-android.md49.7 KiB
- references/EXAMPLE-angular.md23.4 KiB
- references/EXAMPLE-astro-hybrid.md26.8 KiB
- references/EXAMPLE-astro-ssr.md26.7 KiB
- references/EXAMPLE-astro-static.md19.4 KiB
- references/EXAMPLE-astro-view-transitions.md23.1 KiB
- references/EXAMPLE-django.md30.0 KiB
- references/EXAMPLE-expo.md35.5 KiB
- references/EXAMPLE-fastapi.md40.9 KiB
- references/EXAMPLE-flask.md32.0 KiB
- references/EXAMPLE-javascript-node.md9.0 KiB
- references/EXAMPLE-javascript-web.md11.7 KiB
- references/EXAMPLE-laravel.md59.5 KiB
- references/EXAMPLE-next-app-router.md17.3 KiB
- references/EXAMPLE-next-pages-router.md18.9 KiB
- references/EXAMPLE-nuxt-3.6.md22.1 KiB
- references/EXAMPLE-nuxt-4.md28.7 KiB
- references/EXAMPLE-python.md11.6 KiB
- references/EXAMPLE-react-native.md46.4 KiB
- references/EXAMPLE-react-react-router-6.md13.5 KiB
- references/EXAMPLE-react-react-router-7-data.md20.1 KiB
- references/EXAMPLE-react-react-router-7-declarative.md15.0 KiB
- references/EXAMPLE-react-react-router-7-framework.md32.2 KiB
- references/EXAMPLE-react-tanstack-router-code-based.md19.2 KiB
- references/EXAMPLE-react-tanstack-router-file-based.md18.0 KiB
- references/EXAMPLE-react-vite.md12.4 KiB
- references/EXAMPLE-ruby-on-rails.md37.6 KiB
- references/EXAMPLE-ruby.md10.3 KiB
- references/EXAMPLE-sveltekit.md18.4 KiB
- references/EXAMPLE-swift.md18.6 KiB
- references/EXAMPLE-tanstack-start.md28.4 KiB
- references/EXAMPLE-vue-3.md17.9 KiB
- references/android.md21.7 KiB
- references/angular.md12.5 KiB
- references/astro.md8.3 KiB
- references/django.md6.7 KiB
- references/flask.md2.9 KiB
- references/identify-users.md8.1 KiB
- references/ios.md5.4 KiB
- references/js.md12.3 KiB
- references/laravel.md2.1 KiB
- references/next-js.md12.5 KiB
- references/node.md28.8 KiB
- references/nuxt-js-3-6.md6.6 KiB
- references/nuxt-js.md7.2 KiB
- references/posthog-js.md42.3 KiB
- references/posthog-node.md23.4 KiB
- references/posthog-python.md31.3 KiB
- references/python.md31.1 KiB
- references/react-native.md43.8 KiB
- references/react-router-v6.md11.6 KiB
- references/react-router-v7-data-mode.md11.4 KiB
- references/react-router-v7-declarative-mode.md11.6 KiB
- references/react-router-v7-framework-mode.md14.9 KiB
- references/react.md18.5 KiB
- references/ruby-on-rails.md10.6 KiB
- references/ruby.md18.9 KiB
- references/svelte.md7.2 KiB
- references/tanstack-start.md5.1 KiB
- references/vue-js.md9.1 KiB
references/EXAMPLE-nuxt-3.6.md
PostHog nuxt-3.6 Example Project
Repository: https://github.com/PostHog/context-mill Path: basics/nuxt-3.6
README.md
PostHog Nuxt 3.6 example
This is a Nuxt 3.6 example demonstrating PostHog integration with product analytics, session replay, feature flags, and error tracking.
Nuxt 3.0 - 3.6 does not support the @posthog/nuxt package. You must use the posthog-js and posthog-node packages directly instead. This example also does not cover automatic source map uploads, only available through the @posthog/nuxt package.
Nuxt 2.x is also distinctly different, follow this guide instead.
Features
Product Analytics: Track user events and behaviors
Session Replay: Record and replay user sessions
Error Tracking: Capture and track errors
User Authentication: Demo login system with PostHog user identification
Server-side & Client-side Tracking: Examples of both tracking methods
SSR Support: Server-side rendering with Nuxt 3.6
Getting Started
1. Install Dependencies
npm install
# or
pnpm install2. Configure Environment Variables
Create a .env file in the root directory:
NUXT_PUBLIC_POSTHOG_PROJECT_TOKEN=your_posthog_project_token
NUXT_PUBLIC_POSTHOG_HOST=https://us.i.posthog.comGet your PostHog project token from your PostHog project settings.
3. Run the Development Server
npm run dev
# or
pnpm devOpen http://localhost:3000 with your browser to see the app.
Project Structure
├── assets/
│ └── css/
│ └── main.css # Global styles
├── components/
│ └── Header.vue # Navigation header with auth state
├── composables/
│ └── useAuth.ts # Authentication composable
├── pages/
│ ├── index.vue # Home/Login page
│ ├── burrito.vue # Demo feature page with event tracking
│ └── profile.vue # User profile with error tracking demo
├── plugins/
│ └── posthog.client.ts # Client-side PostHog plugin
├── server/
│ ├── api/
│ │ ├── auth/
│ │ │ └── login.post.ts # Login API with server-side tracking
│ │ └── burrito/
│ │ └── consider.post.ts # Burrito API with server-side tracking
│ └── utils/
│ └── users.ts # In-memory user storage utilities
├── types/
│ └── nuxt-app.d.ts # TypeScript declarations for PostHog
├── app.vue # Root component with error handling
└── nuxt.config.ts # Nuxt configurationKey Integration Points
Client-side initialization (plugins/posthog.client.ts)
import posthog from 'posthog-js'
import type { PostHog, PostHogInterface } from 'posthog-js'
export default defineNuxtPlugin((nuxtApp) => {
const runtimeConfig = useRuntimeConfig()
const posthogClient = posthog.init(runtimeConfig.public.posthog.publicKey, {
api_host: runtimeConfig.public.posthog.host,
defaults: runtimeConfig.public.posthog.posthogDefaults as any,
loaded: (posthog: PostHogInterface) => {
if (import.meta.env.MODE === 'development') posthog.debug()
},
})
nuxtApp.hook('vue:error', (error) => {
posthogClient.captureException(error)
})
return {
provide: {
posthog: posthogClient as PostHog,
},
}
})The session and distinct ID are automatically passed to the backend via the X-POSTHOG-SESSION-ID and X-POSTHOG-DISTINCT-ID headers when __add_tracing_headers is configured in the PostHog initialization.
Important: do not identify users on the server-side.
User identification (pages/index.vue)
The user is identified when the user logs in on the client-side.
const { $posthog: posthog } = useNuxtApp()
const handleSubmit = async () => {
const success = await auth.login(username.value, password.value)
if (success) {
// Identifying the user once on login/sign up is enough.
posthog?.identify(username.value)
// Capture login event
posthog?.capture('user_logged_in')
}
}The session and distinct ID are automatically passed to the backend via the X-POSTHOG-SESSION-ID and X-POSTHOG-DISTINCT-ID headers because we set the __add_tracing_headers option in the PostHog initialization.
Important: do not identify users on the server-side.
Server-side API routes (server/api/auth/login.post.ts, server/api/burrito/consider.post.ts)
Server-side API routes create a PostHog Node client for each request and extract session and user context from request headers:
import { PostHog } from 'posthog-node'
import { getHeader } from 'h3'
export default defineEventHandler(async (event) => {
const runtimeConfig = useRuntimeConfig()
// Relies on __add_tracing_headers being set in the client-side SDK
const sessionId = getHeader(event, 'x-posthog-session-id')
const distinctId = getHeader(event, 'x-posthog-distinct-id')
const posthog = new PostHog(
runtimeConfig.public.posthog.publicKey,
{
host: runtimeConfig.public.posthog.host,
}
)
await posthog.withContext(
{ sessionId: sessionId ?? undefined, distinctId: distinctId ?? undefined },
async () => {
posthog.capture({
event: 'server_login',
distinctId: distinctId ?? username,
})
}
)
// Always shutdown to ensure all events are flushed
await posthog.shutdown()
})Key Points:
Creates a new PostHog Node client for each request
Extracts
sessionIdanddistinctIdfrom request headers usinggetHeader()fromh3Uses
withContext()to associate server-side events with the correct session/userProperly shuts down the client after each request to ensure events are flushed
Event tracking (pages/burrito.vue)
const { $posthog: posthog } = useNuxtApp()
const handleConsideration = () => {
if (user.value) {
auth.incrementBurritoConsiderations()
posthog?.capture('burrito_considered', {
total_considerations: user.value?.burritoConsiderations + 1,
username: user.value?.username,
})
}
}Error tracking (app.vue, plugins/posthog.client.ts, pages/profile.vue)
Errors are captured in three ways:
Vue error hook - The
vue:errorhook inplugins/posthog.client.tsautomatically captures Vue errors:
nuxtApp.hook('vue:error', (error) => {
posthogClient.captureException(error)
})Error boundary - The
onErrorCapturedinapp.vuecaptures component errors:
onErrorCaptured((error) => {
posthog?.captureException(error)
return false // Let the error propagate
})Manual error capture in components (pages/profile.vue):
const triggerTestError = () => {
try {
throw new Error('Test error for PostHog error tracking')
} catch (err) {
posthog?.captureException(err as Error)
}
}Server-side tracking (server/api/auth/login.post.ts, server/api/burrito/consider.post.ts)
Server-side events use a PostHog Node client created per request:
const posthog = new PostHog(
runtimeConfig.public.posthog.publicKey,
{
host: runtimeConfig.public.posthog.host,
}
)
await posthog.withContext(
{ sessionId: sessionId ?? undefined, distinctId: distinctId ?? undefined },
async () => {
posthog.capture({
event: 'server_login',
distinctId: distinctId ?? username,
})
}
)
await posthog.shutdown()Key Points:
The PostHog Node client is created per request in each API route
Events are automatically associated with the correct user/session via
withContext()The
distinctIdandsessionIdare extracted from request headers and used to maintain context between client and serverAlways call
shutdown()to ensure events are flushed
Accessing PostHog in components
PostHog is accessed via useNuxtApp():
const { $posthog: posthog } = useNuxtApp()
posthog?.capture('event_name', { property: 'value' })TypeScript types are provided via types/nuxt-app.d.ts:
import type { PostHog } from 'posthog-js'
declare module '#app' {
interface NuxtApp {
$posthog: PostHog
}
}Learn More
.env.example
NUXT_PUBLIC_POSTHOG_PROJECT_TOKEN=
NUXT_PUBLIC_POSTHOG_HOST=app.vue
<template>
<div>
<NuxtRouteAnnouncer />
<Header />
<main>
<NuxtPage />
</main>
</div>
</template>
components/Header.vue
<template>
<header class="header">
<div class="header-container">
<nav>
<NuxtLink to="/">Home</NuxtLink>
<template v-if="user">
<NuxtLink to="/burrito">Burrito Consideration</NuxtLink>
<NuxtLink to="/profile">Profile</NuxtLink>
</template>
</nav>
<div class="user-section">
<template v-if="user">
<span>Welcome, {{ user.username }}!</span>
<button @click="handleLogout" class="btn-logout">
Logout
</button>
</template>
<template v-else>
<span>Not logged in</span>
</template>
</div>
</div>
</header>
</template>
<script setup lang="ts">
const auth = useAuth()
const user = computed(() => auth.user.value)
const { $posthog: posthog } = useNuxtApp()
const handleLogout = () => {
posthog?.capture('user_logged_out')
posthog?.reset()
auth.logout()
}
</script>
composables/useAuth.ts
interface User {
username: string
burritoConsiderations: number
}
const users = new Map<string, User>()
export const useAuth = () => {
const user = useState<User | null>('auth-user', () => {
if (typeof window !== 'undefined') {
const storedUsername = localStorage.getItem('currentUser')
if (storedUsername) {
const existingUser = users.get(storedUsername)
if (existingUser) {
return existingUser
}
}
}
return null
})
const login = async (username: string, password: string): Promise<boolean> => {
if (!username || !password) {
return false
}
try {
const response = await $fetch('/api/auth/login', {
method: 'POST',
body: { username, password },
})
if (response.success && response.user) {
// Update client-side state
user.value = response.user
users.set(username, response.user)
if (typeof window !== 'undefined') {
localStorage.setItem('currentUser', username)
}
return true
}
return false
} catch (err) {
console.error('Login error:', err)
return false
}
}
const logout = () => {
user.value = null
if (typeof window !== 'undefined') {
localStorage.removeItem('currentUser')
}
}
const setUser = (newUser: User) => {
user.value = newUser
users.set(newUser.username, newUser)
}
const incrementBurritoConsiderations = () => {
if (user.value) {
user.value.burritoConsiderations++
users.set(user.value.username, user.value)
// Trigger reactivity by creating a new object
user.value = { ...user.value }
}
}
return {
user,
login,
logout,
setUser,
incrementBurritoConsiderations
}
}
nuxt.config.ts
// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
compatibilityDate: '2025-07-15',
devtools: { enabled: true },
css: ['~/assets/css/main.css'],
runtimeConfig: {
public: {
posthog: {
publicKey: process.env.NUXT_PUBLIC_POSTHOG_PROJECT_TOKEN,
host: process.env.NUXT_PUBLIC_POSTHOG_HOST,
posthogDefaults: '2026-01-30',
},
},
},
})
pages/burrito.vue
<template>
<div class="container">
<h1>Burrito consideration zone</h1>
<p>Take a moment to truly consider the potential of burritos.</p>
<div style="text-align: center">
<button
@click="handleConsideration"
class="btn-burrito"
>
I have considered the burrito potential
</button>
<p v-if="hasConsidered" class="success">
Thank you for your consideration! Count: {{ user?.burritoConsiderations }}
</p>
</div>
<div class="stats">
<h3>Consideration stats</h3>
<p>Total considerations: {{ user?.burritoConsiderations }}</p>
</div>
</div>
</template>
<script setup lang="ts">
const auth = useAuth()
const user = computed(() => auth.user.value)
const router = useRouter()
const hasConsidered = ref(false)
const { $posthog } = useNuxtApp()
// Redirect to home if not logged in
watchEffect(() => {
if (!user.value) {
router.push('/')
}
})
const handleConsideration = async () => {
if (!user.value) return
try {
const response = await $fetch('/api/burrito/consider', {
method: 'POST',
body: { username: user.value.username },
})
if (response.success && response.user) {
auth.setUser(response.user)
hasConsidered.value = true
// Client-side tracking (in addition to server-side tracking)
$posthog?.capture('burrito_considered', {
total_considerations: response.user.burritoConsiderations,
username: response.user.username,
})
setTimeout(() => {
hasConsidered.value = false
}, 2000)
}
} catch (err) {
console.error('Error considering burrito:', err)
}
}
</script>
pages/index.vue
<template>
<div class="container">
<template v-if="user">
<h1>Welcome back, {{ user.username }}!</h1>
<p>You are now logged in. Feel free to explore:</p>
<ul>
<li>Consider the potential of burritos</li>
<li>View your profile and statistics</li>
</ul>
</template>
<template v-else>
<h1>Welcome to Burrito Consideration App</h1>
<p>Please sign in to begin your burrito journey</p>
<form @submit.prevent="handleSubmit" class="form">
<div class="form-group">
<label for="username">Username:</label>
<input
type="text"
id="username"
v-model="username"
placeholder="Enter any username"
/>
</div>
<div class="form-group">
<label for="password">Password:</label>
<input
type="password"
id="password"
v-model="password"
placeholder="Enter any password"
/>
</div>
<p v-if="error" class="error">{{ error }}</p>
<button type="submit" class="btn-primary">Sign In</button>
</form>
<p class="note">
Note: This is a demo app. Use any username and password to sign in.
</p>
</template>
</div>
</template>
<script setup lang="ts">
const auth = useAuth()
const user = computed(() => auth.user.value)
const username = ref('')
const password = ref('')
const error = ref('')
const { $posthog: posthog } = useNuxtApp()
const handleSubmit = async () => {
error.value = ''
const success = await auth.login(username.value, password.value)
if (success) {
// Identifying the user once on login/sign up is enough.
posthog?.identify(username.value)
// Capture login event
posthog?.capture('user_logged_in')
username.value = ''
password.value = ''
} else {
error.value = 'Please provide both username and password'
}
}
</script>
pages/profile.vue
<template>
<div class="container">
<h1>User Profile</h1>
<div class="stats">
<h2>Your Information</h2>
<p><strong>Username:</strong> {{ user?.username }}</p>
<p><strong>Burrito Considerations:</strong> {{ user?.burritoConsiderations }}</p>
</div>
<div style="margin-top: 2rem">
<button @click="triggerTestError" class="btn-primary" style="background-color: #dc3545">
Trigger Test Error (for PostHog)
</button>
</div>
<div style="margin-top: 2rem">
<h3>Your Burrito Journey</h3>
<template v-if="user">
<p v-if="user.burritoConsiderations === 0">
You haven't considered any burritos yet. Visit the Burrito Consideration page to start!
</p>
<p v-else-if="user.burritoConsiderations === 1">
You've considered the burrito potential once. Keep going!
</p>
<p v-else-if="user.burritoConsiderations < 5">
You're getting the hang of burrito consideration!
</p>
<p v-else-if="user.burritoConsiderations < 10">
You're becoming a burrito consideration expert!
</p>
<p v-else>
You are a true burrito consideration master! 🌯
</p>
</template>
</div>
</div>
</template>
<script setup lang="ts">
const auth = useAuth()
const user = computed(() => auth.user.value)
const router = useRouter()
const { $posthog: posthog } = useNuxtApp()
// Redirect to home if not logged in
watchEffect(() => {
if (!user.value) {
router.push('/')
}
})
const triggerTestError = () => {
try {
throw new Error('Test error for PostHog error tracking')
} catch (err) {
console.error('Captured error:', err)
posthog?.captureException(err as Error)
}
}
</script>
plugins/posthog.client.ts
import { defineNuxtPlugin, useRuntimeConfig } from '#imports'
import posthog from 'posthog-js'
import type { PostHog, PostHogInterface } from 'posthog-js'
export default defineNuxtPlugin((nuxtApp) => {
const runtimeConfig = useRuntimeConfig()
const posthogClient = posthog.init(runtimeConfig.public.posthog.publicKey, {
api_host: runtimeConfig.public.posthog.host,
defaults: runtimeConfig.public.posthog.posthogDefaults as any,
loaded: (posthog: PostHogInterface) => {
if (import.meta.env.MODE === 'development') posthog.debug()
},
})
nuxtApp.hook('vue:error', (error) => {
posthogClient.captureException(error)
})
return {
provide: {
posthog: posthogClient as PostHog,
},
}
})
public/robots.txt
User-Agent: *
Disallow:
server/api/auth/login.post.ts
import { getOrCreateUser } from '~/server/utils/users'
import { PostHog } from 'posthog-node'
import { useRuntimeConfig } from '#imports'
import { getHeader } from 'h3'
export default defineEventHandler(async (event) => {
if (event.node.req.method !== 'POST') {
throw createError({
statusCode: 405,
statusMessage: 'Method Not Allowed'
})
}
const body = await readBody(event)
const { username, password } = body
if (!username || !password) {
throw createError({
statusCode: 400,
statusMessage: 'Username and password required'
})
}
// Fake auth - just get or create user
const user = getOrCreateUser(username)
const runtimeConfig = useRuntimeConfig()
// Relies on __add_tracing_headers being set in the client-side SDK
const sessionId = getHeader(event, 'x-posthog-session-id')
const distinctId = getHeader(event, 'x-posthog-distinct-id')
const posthog = new PostHog(
runtimeConfig.public.posthog.publicKey,
{
host: runtimeConfig.public.posthog.host,
}
)
await posthog.withContext(
{ sessionId: sessionId ?? undefined, distinctId: distinctId ?? undefined },
async () => {
posthog.capture({
event: 'server_login',
distinctId: distinctId ?? username,
})
}
)
// Always shutdown to ensure all events are flushed
await posthog.shutdown()
return {
success: true,
user: { ...user }
}
})
server/api/burrito/consider.post.ts
import { users, incrementBurritoConsiderations } from '~/server/utils/users'
import { PostHog } from 'posthog-node'
import { useRuntimeConfig } from '#imports'
import { getHeader } from 'h3'
export default defineEventHandler(async (event) => {
if (event.node.req.method !== 'POST') {
throw createError({
statusCode: 405,
statusMessage: 'Method Not Allowed'
})
}
const body = await readBody(event)
const { username } = body
if (!username) {
throw createError({
statusCode: 400,
statusMessage: 'Username required'
})
}
if (!users.has(username)) {
throw createError({
statusCode: 404,
statusMessage: 'User not found'
})
}
// Increment burrito considerations (fake, in-memory)
const user = incrementBurritoConsiderations(username)
const runtimeConfig = useRuntimeConfig()
// Relies on __add_tracing_headers being set in the client-side SDK
const sessionId = getHeader(event, 'x-posthog-session-id')
const distinctId = getHeader(event, 'x-posthog-distinct-id')
const posthog = new PostHog(
runtimeConfig.public.posthog.publicKey,
{
host: runtimeConfig.public.posthog.host,
}
)
await posthog.withContext(
{ sessionId: sessionId ?? undefined, distinctId: distinctId ?? undefined },
async () => {
posthog.capture({
event: 'burrito_considered',
distinctId: distinctId ?? username,
})
}
)
// Always shutdown to ensure all events are flushed
await posthog.shutdown()
return {
success: true,
user: { ...user }
}
})
server/utils/users.ts
interface User {
username: string
burritoConsiderations: number
}
// Shared in-memory storage for users (fake, no database)
export const users = new Map<string, User>()
export function getOrCreateUser(username: string): User {
let user = users.get(username)
if (!user) {
user = {
username,
burritoConsiderations: 0
}
users.set(username, user)
}
return user
}
export function incrementBurritoConsiderations(username: string): User {
const user = users.get(username)
if (!user) {
throw new Error('User not found')
}
user.burritoConsiderations++
users.set(username, user)
return { ...user }
}
types/nuxt-app.d.ts
import type { PostHog } from 'posthog-js'
declare module '#app' {
interface NuxtApp {
$posthog: PostHog
}
}
export {}
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server, Needs an API key, Needs Python, Needs Node.js
Security
What our scanner noticed· Low risk
- Instructions that use the network
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- PostHog
- Publisher
- PostHog (Official)
- Source
- PostHog/skills · skills/posthog/integration/skills/all · commit a5d30e7
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Also distributed in
- PostHog/skills
AutoGineer is not affiliated with or endorsed by PostHog.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download omnibus-instrument-product-analytics.zip