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, multi-step workflow to integrate PostHog product analytics into a wide variety of software projects. It guides the user through detecting the project's framework, installing the appropriate SDK, initializing the service, and strategically placing event capture calls. The skill emphasizes non-intrusive implementation, requiring that new analytics code be added alongside existing logic without altering the project's fundamental architecture. It also covers user identification, error tracking, and secure environment variable management.
What it does
- Detects the project's framework and language to determine the correct PostHog SDK.
- Handles initial SDK installation and initialization based on framework-specific patterns.
- Identifies key user actions and business-critical events for tracking.
- Implements event capture calls and user identification logic.
- Configures environment variables securely for API tokens and host URLs.
- Verifies the integration and performs targeted linting on modified files.
When to use it
- After implementing new features that require tracking for product analytics.
- When reviewing pull requests to ensure meaningful user behaviors are captured.
- During the initial setup of a new project that needs product analytics.
- When migrating or adding analytics to an existing application.
Advantages
- Supports a broad range of frontend, backend, and mobile frameworks.
- Ensures consistent event naming and property usage across the codebase.
- Prioritizes non-breaking changes and minimal impact on existing code structure.
- Automates the complex setup of environment variables and SDK initialization.
Usage examples
- “Add PostHog analytics to my Next.js project.”
- The agent will analyze the project structure, install the PostHog SDK, initialize it in the appropriate client/server files, and prompt you to identify key events to track.
- “I need to track user signups and errors in my Django backend.”
- The agent will locate your authentication logic, add identify calls, implement exception capture, and ensure the PostHog project tokens are managed via environment variables.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/posthog/instrument-product-analytics/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip 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 and languages: Next.js, React Router, Nuxt, Vue, TanStack Start, SvelteKit, Astro, Angular, Django, Flask, FastAPI, Laravel, PHP, Ruby on Rails, Go, Elixir, Android, iOS, Flutter, 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, pubspec.yaml, Podfile, Package.swift, requirements.txt, Gemfile, composer.json, go.mod, mix.exs, etc.) to determine the framework and language.
Look for lockfiles (pnpm-lock.yaml, package-lock.json, yarn.lock, bun.lockb, go.sum, pubspec.lock, Podfile.lock, Package.resolved, mix.lock) 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.
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.
Check if the project already has PostHog environment variables configured (e.g. in
.env,.env.local, or framework-specific env files). If valid values already exist, skip this step.If the PostHog project token is missing, use the PostHog MCP server's
projects-gettool to retrieve the project'sapi_token. If multiple projects are returned, ask the user which project to use. If the MCP server is not connected or not authenticated, ask the user for their PostHog project token instead.For the PostHog host URL: check the
projects-getMCP response for aregionfield —USmaps tohttps://us.i.posthog.com,EUmaps tohttps://eu.i.posthog.com. If the region is not available from the MCP response or from existing project configuration, ask the user: "Are you on PostHog US Cloud or EU Cloud?" Do not assume US Cloud.Write these values to the appropriate env file using the framework's naming convention.
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, but ONLY on the files you have edited or created during this session. Never run formatting or linting across the entire project's codebase.
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-php.md- php 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.jsreferences/react-router-v6.md- React router v6references/react-router-v7-framework-mode.md- React router v7 framework mode (remix v3)references/react-router-v7-data-mode.md- React router v7 data modereferences/react-router-v7-declarative-mode.md- React router v7 declarative modereferences/nuxt-js-3-6.md- Nuxt.js (v3.0 to v3.6)references/nuxt-js.md- Nuxt.jsreferences/vue-js.md- Vue.jsreferences/tanstack-start.md- Tanstack startreferences/svelte.md- Sveltereferences/astro.md- Astroreferences/angular.md- Angularreferences/django.md- Djangoreferences/flask.md- Flaskreferences/python.md- Pythonreferences/posthog-python.md- PostHog python SDKreferences/dotnet.md- .netreferences/elixir.md- Elixirreferences/go.md- Goreferences/laravel.md- Laravelreferences/php.md- Phpreferences/ruby-on-rails.md- Ruby on railsreferences/ruby.md- Rubyreferences/android.md- Androidreferences/ios.md- Iosreferences/usage.md- Ios SDK usagereferences/configuration.md- Ios SDK configurationreferences/flutter.md- Flutterreferences/react-native.md- React nativereferences/identify-users.md- Identify usersreferences/COMMANDMENTS.md- Framework-specific rules the integration must follow
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 AutoGineer970 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md9.6 KiB
- references/COMMANDMENTS.md1.5 KiB
- references/EXAMPLE-android.md49.8 KiB
- references/EXAMPLE-angular.md23.1 KiB
- references/EXAMPLE-astro-hybrid.md27.5 KiB
- references/EXAMPLE-astro-ssr.md27.6 KiB
- references/EXAMPLE-astro-static.md19.6 KiB
- references/EXAMPLE-astro-view-transitions.md23.3 KiB
- references/EXAMPLE-django.md30.7 KiB
- references/EXAMPLE-expo.md35.1 KiB
- references/EXAMPLE-fastapi.md40.9 KiB
- references/EXAMPLE-flask.md32.4 KiB
- references/EXAMPLE-laravel.md59.3 KiB
- references/EXAMPLE-next-app-router.md17.6 KiB
- references/EXAMPLE-next-pages-router.md19.1 KiB
- references/EXAMPLE-nuxt-3-6.md22.3 KiB
- references/EXAMPLE-nuxt-4.md28.9 KiB
- references/EXAMPLE-php.md13.0 KiB
- references/EXAMPLE-python.md11.6 KiB
- references/EXAMPLE-react-native.md46.0 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.5 KiB
- references/EXAMPLE-react-tanstack-router-code-based.md19.6 KiB
- references/EXAMPLE-react-tanstack-router-file-based.md18.3 KiB
- references/EXAMPLE-ruby-on-rails.md38.0 KiB
- references/EXAMPLE-ruby.md10.0 KiB
- references/EXAMPLE-sveltekit.md18.6 KiB
- references/EXAMPLE-swift.md18.8 KiB
- references/EXAMPLE-tanstack-start.md29.9 KiB
- references/EXAMPLE-vue-3.md17.9 KiB
- references/android.md33.3 KiB
- references/angular.md16.5 KiB
- references/astro.md15.8 KiB
- references/configuration.md17.2 KiB
- references/django.md14.9 KiB
- references/dotnet.md25.8 KiB
- references/elixir.md17.6 KiB
- references/flask.md8.1 KiB
- references/flutter.md42.8 KiB
- references/go.md20.1 KiB
- references/identify-users.md12.2 KiB
- references/ios.md8.0 KiB
- references/laravel.md13.1 KiB
- references/next-js.md18.3 KiB
- references/nuxt-js-3-6.md11.4 KiB
- references/nuxt-js.md15.1 KiB
- references/php.md23.7 KiB
- references/posthog-python.md69.3 KiB
- references/python.md52.2 KiB
- references/react-native.md59.9 KiB
- references/react-router-v6.md13.6 KiB
- references/react-router-v7-data-mode.md13.5 KiB
- references/react-router-v7-declarative-mode.md13.7 KiB
- references/react-router-v7-framework-mode.md20.2 KiB
- references/ruby-on-rails.md19.7 KiB
- references/ruby.md25.5 KiB
- references/svelte.md14.6 KiB
- references/tanstack-start.md12.8 KiB
- references/usage.md29.2 KiB
- references/vue-js.md13.4 KiB
references/EXAMPLE-php.md
PostHog php Example Project
Repository: https://github.com/PostHog/context-mill Path: example-apps/php
README.md
PostHog PHP Example - CLI Todo App
A simple command-line todo application built with plain PHP (no framework) demonstrating PostHog integration for CLIs, scripts, data pipelines, and non-web PHP applications.
Purpose
This example serves as:
Verification that the context-mill wizard works for plain PHP projects
Reference implementation of PostHog best practices for non-framework PHP code
Working example you can run and modify
Features Demonstrated
SDK initialization - Uses
PostHog::init(...)once with environment-based configurationEvent tracking - Captures user actions with
distinctIdand propertiesUser identification - Associates properties with users via
PostHog::identify(...)Error tracking - Enables automatic PHP error tracking and manually captures handled exceptions
Proper flushing - Calls
PostHog::flush()before CLI exit
Quick Start
1. Install Dependencies
composer install2. Configure PostHog
# Copy environment template
cp .env.example .env
# Edit .env and add your PostHog project token
# POSTHOG_PROJECT_TOKEN=phc_your_project_token_here
# POSTHOG_HOST=https://us.i.posthog.com3. Run the App
# Add a todo
php todo.php add "Buy groceries"
# List all todos
php todo.php list
# Complete a todo
php todo.php complete 1
# Delete a todo
php todo.php delete 1
# Show statistics
php todo.php statsWhat Gets Tracked
The app tracks these events in PostHog:
| Event | Properties | Purpose |
|---|---|---|
todo_added | todo_id, todo_length, total_todos | When user adds a new todo |
todos_viewed | total_todos, completed_todos | When user lists todos |
todo_completed | todo_id, time_to_complete_hours | When user completes a todo |
todo_deleted | todo_id, was_completed | When user deletes a todo |
stats_viewed | total_todos, completed_todos, pending_todos | When user views stats |
$exception | exception details and command context | When handled errors occur |
Code Structure
example-apps/php/
├── todo.php # Main CLI application
├── composer.json # PHP dependencies
├── .env.example # Environment variable template
├── .gitignore # Git ignore rules
└── README.md # This fileKey Implementation Patterns
1. Initialize Once
PostHog::init($projectToken, [
'host' => $host,
'error_tracking' => [
'enabled' => true,
],
]);2. Event Tracking Pattern
PostHog::capture([
'distinctId' => 'user_123',
'event' => 'event_name',
'properties' => ['key' => 'value'],
]);3. Identifying Users
PostHog::identify([
'distinctId' => 'user_123',
'properties' => ['app_language' => 'php'],
]);4. Exception Tracking
try {
riskyOperation();
} catch (Throwable $e) {
PostHog::captureException($e, 'user_123', [
'command' => 'example_command',
]);
}5. Flush Before CLI Exit
PostHog::flush();Running Without PostHog
The app works fine without PostHog configured - it simply won't track analytics. You'll see a warning message but the app continues to function normally.
Next Steps
Modify
todo.phpto experiment with PostHog trackingAdd new commands and track their usage
Explore feature flags:
PostHog::isFeatureEnabled('flag-name', 'user_id')Check your PostHog dashboard to see tracked events
Learn More
.env.example
# PostHog configuration
POSTHOG_PROJECT_TOKEN=phc_your_project_token_here
POSTHOG_HOST=https://us.i.posthog.com
todo.php
<?php
declare(strict_types=1);
// Simple CLI Todo App with PostHog Analytics
//
// A minimal plain PHP CLI application demonstrating PostHog integration
// for non-framework PHP projects (CLIs, scripts, data pipelines, etc.).
require __DIR__ . '/vendor/autoload.php';
use PostHog\PostHog;
const DATA_FILE = '.todo_app_php.json';
function loadEnvFile(string $path): void
{
if (!file_exists($path)) {
return;
}
foreach (file($path, FILE_IGNORE_NEW_LINES | FILE_SKIP_EMPTY_LINES) ?: [] as $line) {
$line = trim($line);
if ($line === '' || str_starts_with($line, '#') || !str_contains($line, '=')) {
continue;
}
[$key, $value] = explode('=', $line, 2);
$key = trim($key);
$value = trim($value, " \t\n\r\0\x0B\"'");
if ($key !== '' && getenv($key) === false) {
putenv($key . '=' . $value);
$_ENV[$key] = $value;
}
}
}
function dataFilePath(): string
{
$home = getenv('HOME') ?: sys_get_temp_dir();
return rtrim($home, DIRECTORY_SEPARATOR) . DIRECTORY_SEPARATOR . DATA_FILE;
}
function initializePostHog(): bool
{
loadEnvFile(__DIR__ . '/.env');
$projectToken = getenv('POSTHOG_PROJECT_TOKEN');
if (!$projectToken || str_starts_with($projectToken, 'phc_your_')) {
echo "WARNING: PostHog not configured (POSTHOG_PROJECT_TOKEN not set)\n";
echo " App will work but analytics won't be tracked\n";
return false;
}
PostHog::init($projectToken, [
'host' => getenv('POSTHOG_HOST') ?: 'https://us.i.posthog.com',
'error_tracking' => [
'enabled' => true,
'context_provider' => static function (array $payload): array {
return [
'distinctId' => getUserId(),
'properties' => [
'app' => 'php_todo_cli',
'runtime' => PHP_VERSION,
'$exception_source' => $payload['source'] ?? null,
],
];
},
],
]);
return true;
}
function getUserId(): string
{
$path = dataFilePath();
if (file_exists($path)) {
$data = json_decode((string) file_get_contents($path), true);
if (is_array($data) && isset($data['user_id'])) {
return (string) $data['user_id'];
}
}
return 'user_' . bin2hex(random_bytes(4));
}
function loadTodos(): array
{
$path = dataFilePath();
if (!file_exists($path)) {
return ['user_id' => getUserId(), 'todos' => []];
}
$data = json_decode((string) file_get_contents($path), true);
if (!is_array($data)) {
return ['user_id' => getUserId(), 'todos' => []];
}
$data['todos'] = $data['todos'] ?? [];
$data['user_id'] = $data['user_id'] ?? getUserId();
return $data;
}
function saveTodos(array $data): void
{
file_put_contents(dataFilePath(), json_encode($data, JSON_PRETTY_PRINT) . PHP_EOL);
}
function identifyUser(bool $posthogEnabled): void
{
if (!$posthogEnabled) {
return;
}
PostHog::identify([
'distinctId' => getUserId(),
'properties' => [
'app_language' => 'php',
'app_type' => 'cli',
],
]);
}
function trackEvent(bool $posthogEnabled, string $eventName, array $properties = []): void
{
if (!$posthogEnabled) {
return;
}
PostHog::capture([
'distinctId' => getUserId(),
'event' => $eventName,
'properties' => $properties,
]);
}
function cmdAdd(string $text, bool $posthogEnabled): void
{
$data = loadTodos();
$todo = [
'id' => count($data['todos']) + 1,
'text' => $text,
'completed' => false,
'created_at' => date(DATE_ATOM),
];
$data['todos'][] = $todo;
saveTodos($data);
echo "Added todo #{$todo['id']}: {$todo['text']}\n";
trackEvent($posthogEnabled, 'todo_added', [
'todo_id' => $todo['id'],
'todo_length' => strlen($todo['text']),
'total_todos' => count($data['todos']),
]);
}
function cmdList(bool $posthogEnabled): void
{
$data = loadTodos();
if (count($data['todos']) === 0) {
echo "No todos yet! Add one with: php todo.php add 'Your task'\n";
return;
}
echo "\nYour Todos (" . count($data['todos']) . " total):\n\n";
foreach ($data['todos'] as $todo) {
$status = $todo['completed'] ? 'X' : ' ';
echo " [{$status}] #{$todo['id']}: {$todo['text']}\n";
}
echo "\n";
trackEvent($posthogEnabled, 'todos_viewed', [
'total_todos' => count($data['todos']),
'completed_todos' => count(array_filter($data['todos'], static fn (array $todo): bool => (bool) $todo['completed'])),
]);
}
function cmdComplete(int $id, bool $posthogEnabled): void
{
$data = loadTodos();
foreach ($data['todos'] as &$todo) {
if ((int) $todo['id'] !== $id) {
continue;
}
if ($todo['completed']) {
echo "Todo #{$id} is already completed\n";
return;
}
$todo['completed'] = true;
$todo['completed_at'] = date(DATE_ATOM);
saveTodos($data);
echo "Completed todo #{$todo['id']}: {$todo['text']}\n";
$timeToComplete = (strtotime($todo['completed_at']) - strtotime($todo['created_at'])) / 3600;
trackEvent($posthogEnabled, 'todo_completed', [
'todo_id' => $todo['id'],
'time_to_complete_hours' => $timeToComplete,
]);
return;
}
echo "ERROR: Todo #{$id} not found\n";
}
function cmdDelete(int $id, bool $posthogEnabled): void
{
$data = loadTodos();
foreach ($data['todos'] as $index => $todo) {
if ((int) $todo['id'] !== $id) {
continue;
}
unset($data['todos'][$index]);
$data['todos'] = array_values($data['todos']);
saveTodos($data);
echo "Deleted todo #{$id}\n";
trackEvent($posthogEnabled, 'todo_deleted', [
'todo_id' => $todo['id'],
'was_completed' => $todo['completed'],
]);
return;
}
echo "ERROR: Todo #{$id} not found\n";
}
function cmdStats(bool $posthogEnabled): void
{
$data = loadTodos();
$total = count($data['todos']);
$completed = count(array_filter($data['todos'], static fn (array $todo): bool => (bool) $todo['completed']));
$pending = $total - $completed;
$rate = $total > 0 ? number_format($completed / $total * 100, 1) : '0.0';
echo "\nStats:\n\n";
echo " Total todos: {$total}\n";
echo " Completed: {$completed}\n";
echo " Pending: {$pending}\n";
echo " Completion rate: {$rate}%\n\n";
trackEvent($posthogEnabled, 'stats_viewed', [
'total_todos' => $total,
'completed_todos' => $completed,
'pending_todos' => $pending,
]);
}
function printUsage(): void
{
echo <<<USAGE
Simple todo app with PostHog analytics
Usage:
php todo.php add "Todo text" Add a new todo
php todo.php list List all todos
php todo.php complete <id> Mark todo as completed
php todo.php delete <id> Delete a todo
php todo.php stats Show statistics
USAGE;
}
$posthogEnabled = false;
try {
$posthogEnabled = initializePostHog();
identifyUser($posthogEnabled);
$command = $argv[1] ?? null;
if (!$command) {
printUsage();
exit(0);
}
switch ($command) {
case 'add':
$text = $argv[2] ?? null;
if (!$text) {
echo "ERROR: Please provide todo text\n";
echo "Usage: php todo.php add \"Your task\"\n";
exit(1);
}
cmdAdd($text, $posthogEnabled);
break;
case 'list':
cmdList($posthogEnabled);
break;
case 'complete':
$id = (int) ($argv[2] ?? 0);
if ($id <= 0) {
echo "ERROR: Please provide a valid todo ID\n";
echo "Usage: php todo.php complete <id>\n";
exit(1);
}
cmdComplete($id, $posthogEnabled);
break;
case 'delete':
$id = (int) ($argv[2] ?? 0);
if ($id <= 0) {
echo "ERROR: Please provide a valid todo ID\n";
echo "Usage: php todo.php delete <id>\n";
exit(1);
}
cmdDelete($id, $posthogEnabled);
break;
case 'stats':
cmdStats($posthogEnabled);
break;
default:
echo "ERROR: Unknown command '{$command}'\n";
printUsage();
exit(1);
}
} catch (Throwable $e) {
echo "ERROR: {$e->getMessage()}\n";
if ($posthogEnabled) {
PostHog::captureException($e, getUserId(), [
'command' => $argv[1] ?? null,
'app' => 'php_todo_cli',
]);
}
exit(1);
} finally {
if ($posthogEnabled) {
PostHog::flush();
}
}
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 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/omnibus/instrument-product-analytics · commit a5d30e7
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by PostHog or PostHog.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download instrument-product-analytics.zip