simulate-new-user
/simulate-new-user
Send synthetic first-time-visitor traffic to a URL and confirm that PostHog $pageview events fire. Use when a customer wants to verify that anonymous visitor tracking works, after deploying instrumentation changes, or when debugging "events not arriving" reports.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 4
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Send synthetic first-time-visitor traffic to a URL and confirm that PostHog $pageview events fire. Use when a customer wants to verify that anonymous visitor tracking works, after deploying instrumentation changes, or when debugging "events not arriving" reports.
Triggers from the description
Original author description
Send synthetic first-time-visitor traffic to a URL and confirm that PostHog $pageview events fire. Use when a customer wants to verify that anonymous visitor tracking works, after deploying instrumentation changes, or when debugging "events not arriving" reports.
How it works
- When to use
- How to invoke
- Interpreting the result
SKILL.md preview
---
name: simulate-new-user
description: >
Send synthetic first-time-visitor traffic to a URL and confirm that PostHog
$pageview events fire. Use when a customer wants to verify that anonymous
visitor tracking works, after deploying instrumentation changes, or when
debugging "events not arriving" reports.
---
# Simulate new-user traffic
Drives a fresh browser context for each visit (no cookies, no localStorage),
goes to the given URL, scrolls a bit, and reports which PostHog events fired.
Each visit looks to PostHog like a brand-new anonymous visitor.
## When to use
- Confirm `$pageview` fires on the first visit (no cookies present).
- Confirm an anonymous `distinct_id` is generated and a PostHog request
is sent within a few seconds of page load.
- Reproduce "events not showing up for new users" reports.
## How to invoke
Call the `simulate_new_user` MCP tool with:
- `url` (required) — the page to visit, e.g. `https://example.com/pricing`.
- `visits` (default `3`) — number of fresh-context visits.
- `interval` (default `5.0`) — seconds between visits.
- `posthog_host` (default `https://us.i.posthog.com`) — set to
`https://eu.i.posthog.com` for the EU cloud, or your self-hosted host
(e.g. `https://ph.example.com`).
Each visit takes ~10s of Playwright time plus the interval, so plan accordingly.
## Interpreting the result
The tool returns a structured summary:
```jsonc
{
"run_id": "a1b2c3d4",
"scenario": "new-user",
"total_visits": 3,
"posthog_requests": 6,
"posthog_requests_ok": 6,
"events_by_type": { "$pageview": 3, "$autocapture": 3 },
"pageviews": 3,
"errors": [],
"verified": true,
}
```
- `verified: true` means at least one `$pageview` was captured per visit and
no errors occurred — the new-user flow works.
- `verified: false` with `pageviews: 0` means PostHog isn't firing pageviews.
Run `check_posthog_loading` next to see whether the snippet is even loaded.
- `posthog_requests_ok < posthog_requests` means PostHog returned non-2xx
responses. Check the project's ingestion limits and api_host configuration.
Versions
The database has no other skills named simulate-new-user.
Database snapshot: 13.11.2026 · package version 5d0662b64b4b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90simulate-returning-user
Send synthetic single-session multi-page traffic to a URL and confirm PostHog $pageview events fire across page views. Use when verifying that cookies persist correctly, that the same distinct_id is reused across navigations, or when debugging session-stitching issues. - 90verify-posthog-instrumentation
Use this skill to verify that PostHog instrumentation is firing correctly on a website. Drives a real browser at one or more URLs, observes which PostHog events actually arrive, and reports a pass/fail summary. Use after installing the PostHog SDK on a site, after a deploy that… - 100posthog-webhooks
Receive and verify PostHog webhooks from the Webhook destination (CDP). Use when setting up PostHog webhook handlers, debugging Standard Webhooks signature verification (webhook-id, webhook-timestamp, webhook-signature), choosing a signing secret, or handling events like… - 93posthog-debugger
Debug and inspect PostHog implementations on any website. Use this skill when a user wants to understand how PostHog is implemented on a page, troubleshoot tracking issues, verify configuration, check what events are being sent, or audit a PostHog setup. Works with Chrome… - 100posthog-onboarding
Help existing PostHog customers improve their PostHog instance. Triggers on "help [customer] improve their PostHog setup", "audit [company]'s PostHog instance", "create tracking plan for [company]", "design data schema for [customer]", or requests to improve analytics coverage,… - 100posthog-webhooks-events
Build and verify PostHog realtime webhook destinations and bounded private-API or HogQL event queries. Use when delivering selected events to another system or investigating event data. Trigger with "PostHog webhook", "PostHog destination", or "PostHog HogQL query".