Name: simulate-new-user
Rating: 72 (1 reviews)
Author: PostHog

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.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and highly actionable, with concrete tool/parameter guidance and a clear result-interpretation workflow that includes error-recovery branches. The only minor weakness is a few explanatory sentences that slightly pad the otherwise efficient prose.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence (parameters with defaults, a compact JSON result sample), but a few explanatory sentences restating what 'verified: true' means in prose could be trimmed slightly.	4 / 5
Actionability	Fully actionable: specifies the exact MCP tool name ('simulate_new_user'), every parameter with types, defaults, and concrete example values, plus a real result JSONC block covering the common case.	5 / 5
Workflow Clarity	The 'Interpreting the result' section sequences verification into explicit decision branches (verified true, pageviews:0 -> run check_posthog_loading, non-2xx -> check ingestion limits), providing clear feedback loops for error recovery.	5 / 5
Progressive Disclosure	This is a simple single-purpose skill under 50 lines with no bundle files; content is well-organized into focused sections (When to use, How to invoke, Interpreting the result), meeting the simple-skill exception for a top score.	5 / 5
	Total	19 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong on completeness and distinctiveness, clearly stating both what it does and when to use it with concrete PostHog-specific triggers. Specificity is the weakest area: it names the domain and one core action but does not enumerate multiple concrete capabilities.

Suggestions

List 2-3 specific concrete actions in the description (e.g., drive fresh browser contexts, capture PostHog network requests, report per-visit event breakdowns) to lift specificity toward the score-4/5 anchors.

Dimension	Reasoning	Score
Specificity	Names the domain (synthetic first-time-visitor traffic, $pageview events) and one concrete action (confirm events fire), but does not list multiple specific actions like the score-4/5 anchors require.	3 / 5
Completeness	Explicitly answers 'what' ('Send synthetic first-time-visitor traffic... confirm that PostHog $pageview events fire') and 'when' ('Use when a customer wants to verify...', 'after deploying instrumentation changes', 'debugging reports') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user-facing phrases ('events not arriving', 'anonymous visitor tracking', 'debugging') and PostHog/$pageview terms; a few synonyms or alternative phrasings a user might say are missing.	4 / 5
Distinctiveness Conflict Risk	The PostHog new-user simulation niche is highly specific with distinct triggers (synthetic traffic, $pageview, anonymous visitor) and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: PostHog/posthog
Path: tools/traffic-sim/skills/simulate-new-user/SKILL.md
Commit: 6fca5f8

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.