Skip to content
SkillModel-led2,588 tokens in use

product-analytics

Add behaviour analytics without analytics cookies: Microsoft Clarity by default, PostHog when a question needs events, with consent tests and data the agent reads back itself.

680 stars on the repository MIT Licensephuryn/product-engineering · app-stack/skills/product-analytics
claude plugin install app-stack@product-engineering
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing product-analytics costs

37tokens idle
2,588tokens in use
4,987tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetectedcredentialsdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure19/25
  • Examples0/15
  • Output10/15
  • Size13/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance100
  • Community44
  • Maturity4
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers