Before querying, the skill verifies authentication with a trivial query and notes that dashboard API helpers read credentials from a local JSON file rather than any hardcoded project id, even though it names the project's current PostHog environment and region for reference. Event-level queries run directly through posthog-cli's experimental query command with a HogQL string, while dashboard metadata or cached insight results go through two bundled shell scripts because the CLI has no dedicated dashboard command.
A shell-quoting rule calls for wrapping HogQL in single quotes whenever it references a property like $app_version or $os, since double quotes let the shell expand the dollar sign before the CLI sees it. A set of ready-made HogQL queries covers recent events, top events and pageview pages over the last 7 days, click targets, app versions and an OS breakdown, and the skill expects every answer to report the exact command used, the key rows or aggregates, and any caveats such as partial-day data or test-account filtering.