survey-sdk-audit
Audit PostHog survey SDK features and version requirements, and implement survey changes across the backend, UI, and SDK repositories.
signals-scout-feature-flags
>
signals-scout-ai-observability
>
signals-scout-session-replay
>
signals-scout-error-tracking
>
finding-replay-for-issue
>
signals-scout-tasks
>
finding-sessions-to-watch
>
review-hog-authoring
>
signals-scout-customer-analytics-billing-and-usage
>
signals-scout-customer-analytics
>
signals-scout-experiments
>
signals-scout-data-pipelines
>
signals-scout-data-warehouse
>
inbox-exploration
>
signals-scout-apm
>
signals-scout-revenue-analytics
>
signals-scout-anomaly-detection
>
creating-box-plot-insights
>-
exploring-scouts
>
signals-scout-skills-store
>
formatting-insight-axes
>
signals-scout-logs
>
signals-scout-conversations
>
signals-scout-web-analytics
>
signals-scout-mcp-tool-calls
>
signals-scout-replay-vision
>
signals-scout-csp-violations
>
signals-scout-health-checks
>
investigating-replay
>
signals-scout-observability-gaps
>
creating-replay-vision-scanners
Guides agents through creating and safely sizing a Replay Vision scanner: choosing the scanner type (monitor/classifier/scorer/summarizer), shaping the RecordingsQuery that selects sessions, and — crucially — estimating the credits it will spend and checking the org's remaining budget before creating, so a broad scanner doesn't exhaust the budget on its first scheduled sweep.\nTRIGGER when: user asks to create, set up, or configure a Replay Vision scanner, OR when you are about to call vision-scanners-create, OR when widening an existing scanner's query, sampling_rate, or sampling_mode (or moving it to a pricier model) via vision-scanners-update.\nDO NOT TRIGGER when: only reading scanners or observations, deleting a scanner, or running an existing scanner against sessions on demand (vision-scanners-scan-session/-scan-sessions). For a one-off question about sessions you already have, use vision-scanners-inline-scan rather than creating a scanner — the skill's first section covers when that applies.
investigate-metric
>
signals-scout-surveys
>
authoring-scouts
>
managing-reminders
Create and manage PostHog reminders — private, human-paced nudges that fire as in-app notifications on a schedule, optionally linked to a PostHog resource. Use when the user says "remind me to…", wants a one-off or recurring nudge (daily/weekly/monthly/yearly, a cron schedule, or a specific date/time), wants to be reminded to look at a dashboard, insight, experiment, feature flag, survey, notebook, replay, or error, or wants to list, change, or cancel their reminders. Covers when to pick a reminder over an alert or subscription, the one-off vs recurring vs cron schedule field mappings, timezones, and attaching a resource.
signals-scout-insight-alerts
>
querying-posthog-data
>
signals-scout-product-analytics
>
writing-simplified-technical-english
Write English that a reader cannot misread: one meaning per word, active voice, simple tenses, one idea per sentence, short sentences. Based on ASD-STE100 (Simplified Technical English), the controlled-language standard written for aircraft maintenance manuals. Use it for any prose an agent produces that someone else acts on. That covers reports and findings, PR descriptions and commit messages, instructions handed to another agent, tool descriptions, error messages, status summaries, and prompts. Also use it on request, with triggers like "simplify this", "make this readable", "too dense", "rewrite in STE", "simplified technical english", "ASD-STE100".
review-hog-perspective-contracts-security
>
signals-scout-pr-follow-up
>
review-hog-blind-spots-general
>
review-hog-perspective-performance-reliability
>
review-hog-validation-criteria
>
review-hog-perspective-logic-correctness
>
review-hog-resolution-criteria
>
exploring-replay-vision-observations
Guides agents through pulling a Replay Vision scanner's observations, reading the findings, and acting on them — summarizing patterns across sessions, drilling into individual recordings, and turning real, corroborated issues into PostHog tasks, insights, or an investigating-replay hand-off.\nTRIGGER when: user wants to pull/read/triage Replay Vision observations, asks \"what has my scanner found\", wants to act on or summarize scanner findings, turn observations into tasks/work, or points at a /replay-vision/<scanner-id> URL.\nDO NOT TRIGGER when: creating or sizing a scanner (use creating-replay-vision-scanners), running a one-off scan you don't then analyse, or authoring a signals scout.
signals-scout-general
>
exploring-autocapture-events
>
Page 37 of 1736 · 86768 results
