Skene is a validation layer for agent-driven development. It runs before code merges, knows which analytics events should fire in your repo, and catches when a coding agent removes, renames, or breaks those calls.

Skene reads the repository and tracks every analytics call into PostHog, Mixpanel, Segment, Amplitude, or Heap. When a PR changes one of those files, Skene flags removed calls, renamed events, and altered payloads on the PR before the change merges.

What analytics tools does Skene work with?

Skene validates instrumentation for PostHog, Mixpanel, Segment, Amplitude, Heap, and Snowplow. It runs inside coding agents like Cursor, Claude Code, Codex, and Devin via an MCP server, and in CI as a GitHub Action.

Four surfaces: an MCP server or agent skill that runs before the coding agent commits, a GitHub Action that posts a PR comment in CI, a cloud validation API for programmatic runs, and a one-time repository audit.

Catch analytics drift

Stop your coding agent from breaking tracking.

Coding agents rewrite the lines that fire your PostHog and Mixpanel events. Skene catches it on the PR, before your dashboards break.

Runs inside the agents you already use

The problem

Event streams are how you make decisions. They break quietly.

Product, growth, and exec all run on event data. Funnels, retention, attribution, pricing experiments. The charts that drive roadmap calls and budget calls come from a stream of posthog.capture and mixpanel.track calls sitting in your repo.

That stream is fragile. A coding agent rewriting a checkout flow does not know which line in the file fires event: "checkout_completed". It changes the function, ships the PR, and your funnel goes quiet. The dashboard keeps drawing, just from worse data. Nobody notices until a number looks wrong three sprints later.

Skene reads every analytics call in your repo.

PostHog capture, Mixpanel track, Segment identify, Amplitude event, Heap track. Indexed by file, line, and payload shape.

Skene parses the codebase the way a linter does. It finds every call into your analytics library, builds an index of where each event fires, and remembers what payload it ships. That index is the baseline every PR gets checked against.

Read the docs

Open GitHub

✓Scanning repository structure

✓Detected Next.js framework

✓Found 12 growth signals

✓Identified onboarding friction points

✓Detected activation opportunities

✓Plan created

Run ↵

✓Acquisition loop

✓Activation loop

✓Retention loop

✓Expansion loop

Drop one capture call. Your dashboard goes quiet for three sprints.

Removed events. Renamed events. Moved events. Altered payloads. Conditional firing that no longer fires.

When a PR changes a file with analytics in it, Skene compares the new state against the index. Missing calls, renamed events, payload shape changes, and conditional firing that no longer fires all show up as a comment on the PR. Caught on review, not on a dashboard that has been wrong since a refactor weeks ago.

Open GitHub

Four ways to plug Skene in.

MCP server for your coding agent. GitHub Action for CI. Cloud API for custom runs. One-time repo audit.

Install the MCP server into Cursor or Claude Code and Skene runs before the agent commits. Add the GitHub Action and it runs on every PR. Hit the cloud API directly from any script. Or run a one-time audit of your current instrumentation surface before you adopt anything else.

Read the docs

Open GitHub

✓Expansion loop

From install to a clean instrumentation surface.

A baseline of every analytics call you already have, drift caught on the PR that introduced it, and an instrumentation surface that stays consistent as the codebase grows.

Read the docs

Open GitHub

1. EVERY ANALYTICS CALL IN YOUR REPO, INDEXED

2. DRIFT FLAGGED ON THE PR THAT INTRODUCED IT

3. INSTRUMENTATION SURFACE THAT STAYS CLEAN

What Skene is not

It is not a coding agent. It runs alongside one.

Skene does not write code. It does not compete with Cursor, Copilot, Claude Code, or Codex. It runs alongside them as a checkpoint that reads the analytics code already in your repo.

It is also not a product analytics tool, an instrumentation library, or a customer data platform. It validates that the calls you made into PostHog, Mixpanel, Segment, Amplitude, or Heap still fire the way you intended after the next PR.

Skene provided clear value as a C2 adoption-readiness lens: it surfaced where our operator journey is strong vs. where it will break under real mission tempo.

CurtisCTO, Aegis

"The main value for me was that it surfaces the practical, nitty-gritty product details that often get skipped when you're shipping fast."

GurdeepSenior Engineer, Revqa

"It forced me to look at the repo through the lens of 'what's the actual next step for a user,' not just features."

Guilherme MussiCTO

"The evaluation summaries, failure reports and remediation trackers were genuinely helpful. Those are the parts I'd actually use for planning."

Zakaria BelfakhirFounding AI Engineer, LivAI

"Skene became the system we used to answer one question over and over: What's the highest-leverage fix to ship next, and how do we implement it cleanly?"

Chris MarleyFounder, Celeste Technologies

“We had a completion problem. After scanning the codebase and Skene identified decision paralysis on the creation page as the #1 growth blocker. After Skene Time to Value dropped 59% and Activation rate increased by 34%”

Mari LuukkainenFounder, Pitchkit

Skene provided clear value as a C2 adoption-readiness lens: it surfaced where our operator journey is strong vs. where it will break under real mission tempo.

CurtisCTO, Aegis

"The main value for me was that it surfaces the practical, nitty-gritty product details that often get skipped when you're shipping fast."

GurdeepSenior Engineer, Revqa

"It forced me to look at the repo through the lens of 'what's the actual next step for a user,' not just features."

Guilherme MussiCTO

"The evaluation summaries, failure reports and remediation trackers were genuinely helpful. Those are the parts I'd actually use for planning."

Zakaria BelfakhirFounding AI Engineer, LivAI

"Skene became the system we used to answer one question over and over: What's the highest-leverage fix to ship next, and how do we implement it cleanly?"

Chris MarleyFounder, Celeste Technologies

“We had a completion problem. After scanning the codebase and Skene identified decision paralysis on the creation page as the #1 growth blocker. After Skene Time to Value dropped 59% and Activation rate increased by 34%”

Mari LuukkainenFounder, Pitchkit

See what your last 10 PRs quietly broke.

Install in a minute. The first repo audit runs in about as long as your CI does.

Billed monthlyBilled yearly

ProPopular

$29/mo

1.5M monthly tokens

Local MCP server
GitHub Action with PR comments
Cloud validation API
1.5M monthly tokens

Try for free →

Scale

$99/mo

6M monthly tokens

6M monthly tokens (4x Pro)

Try for free →

Ultra

$199/mo

15M monthly tokens

15M monthly tokens (10x Pro)
Priority support

Try for free →

Event streams are how you make decisions. They break quietly.

It is not a coding agent. It runs alongside one.

Skene does not write code. It does not compete with Cursor, Copilot, Claude Code, or Codex. It runs alongside them as a checkpoint that reads the analytics code already in your repo.

Stop your coding agent from breaking tracking.

Event streams are how you make decisions. They break quietly.

Skene reads every analytics call in your repo.

Drop one capture call. Your dashboard goes quiet for three sprints.

Four ways to plug Skene in.

From install to a clean instrumentation surface.

It is not a coding agent. It runs alongside one.

The new way to build growth.
Trusted by over 1000 developers.

See what your last 10 PRs quietly broke.

Pay for cloud validation runs.

Stop your coding agent from breaking tracking.

Event streams are how you make decisions. They break quietly.

Skene reads every analytics call in your repo.

Drop one capture call. Your dashboard goes quiet for three sprints.

Four ways to plug Skene in.

From install to a clean instrumentation surface.

It is not a coding agent. It runs alongside one.

The new way to build growth.
Trusted by over 1000 developers.

See what your last 10 PRs quietly broke.

Pay for cloud validation runs.

Stop your coding agent from breaking tracking.

Event streams are how you make decisions. They break quietly.

Skene reads every analytics call in your repo.

Drop one capture call. Your dashboard goes quiet for three sprints.

Four ways to plug Skene in.

From install to a clean instrumentation surface.

It is not a coding agent. It runs alongside one.

The new way to build growth.Trusted by over 1000 developers.

See what your last 10 PRs quietly broke.

Pay for cloud validation runs.

Stop your coding agent from breaking tracking.

Event streams are how you make decisions. They break quietly.

Skene reads every analytics call in your repo.

Drop one capture call. Your dashboard goes quiet for three sprints.

Four ways to plug Skene in.

From install to a clean instrumentation surface.

It is not a coding agent. It runs alongside one.

The new way to build growth.Trusted by over 1000 developers.

See what your last 10 PRs quietly broke.

Pay for cloud validation runs.

The new way to build growth.
Trusted by over 1000 developers.

The new way to build growth.
Trusted by over 1000 developers.