This skill sets up session recordings, heatmaps and event analytics so the next round of product work starts from what people did after release. Microsoft Clarity runs with cookies off and storage consent denied from the page. PostHog is added when a question names an event.
It covers the analytics policy line, the content security policy origins, tagging only the landing page, proof that nothing loads before consent, and reading the data back through the vendor’s MCP server so the owner need not send screenshots.
What You Get
- A default of Clarity with cookies off, plus the PostHog option and its reference file
- Six binding rules: off without a project id, the denial queued first, a gated policy sentence, CSP origins, landing page only, agent read-back
- Unit and browser tests that read cookies and storage with the tag running
- A consent decision and proof procedure
- An owner checklist for Clarity project setup, the cookies setting and the API token
Common Use Cases
- Adding session recordings and heatmaps to a landing page without cookies
- Proving that no analytics cookie or stored id appears on tagged pages
- Asking the agent what visitors did yesterday through Clarity’s MCP server
- Adding PostHog funnels for an anonymous landing page
What Makes It Unique
The cookieless setup has two halves and the skill tests both: the page’s code denies storage before the tag runs, and the owner switches the dashboard’s cookies off, with a screenshot as evidence. It also warns that without cookies every page view is its own session, so the data reads as pages and flows, not visitors.
Under The Hood
The skill is instructions and reference markdown, with no scripts. Following it, the agent edits the product’s code, content security policy, privacy page and tests, and runs a browser test that loads the vendor’s script, which reaches Microsoft’s analytics hosts, and reads cookies and storage. For read-back, the owner adds the vendor’s MCP server with npx and an API token in their own terminal, and that server calls Clarity’s export API under a daily request limit. The token is a secret the owner handles and the agent never sees in the session.