Skene is the trust layer for your product data. It runs on every pull request, reads your Supabase schema read-only, and catches when a coding agent removes, renames, or breaks the code that records events to your tables, so the metrics built on that data stay trustworthy.

Skene reads the repository and tracks every event your app writes into Supabase. When a pull request changes one of those files, Skene flags removed writes, renamed columns, and payloads your schema cannot store on the PR before the change merges.

Is Skene a coding agent?

No. Skene is not a coding agent and does not compete with Cursor, Claude Code, Codex, or Devin. It runs alongside them as an independent check that validates the event-writing code already in your repository.

What does Skene work with?

Skene reads the events your app writes to Supabase and checks them against your schema. It works alongside coding agents like Cursor, Claude Code, Codex, and Devin, and runs in CI as a GitHub Action.

Skene runs as a GitHub Action that posts a comment on every pull request, with a cloud validation API for programmatic runs and a one-time repository audit to baseline what you already have.

Trust your product data.

The signups, activations, and conversions you count on stop getting recorded, whether an agent rewrote the tracking, you changed it by hand, or never set it up. Skene stores your product metrics in your own Supabase, then runs autonomously after a one-time setup, so they're there the day you need them.

Start free

The problem

You can't get today's data back tomorrow.

Early on, analytics is handled, for now. You will get to it properly later, the product comes first, and what you already have feels like enough. Then an event quietly stops firing, from a refactor, a rename, or because no one added it. Nothing errors. The table just stops filling.

Analytics is not retroactive. Months later you raise a round, set pricing, or chase a churn spike, you reach back for the history, and it is not there. You cannot backfill an event that never fired.

Kept in your own Supabase, every event costs cents to store and almost nothing to check on a PR. Being without it costs you the decision. Skene connects in under ten minutes and runs on every pull request, so the record is already there when it matters.

Trust the data your decisions run on.

A baseline of every event write you already have.

Indexed by file, line, table, and payload
Reads your Supabase schema as the contract
Checks each PR against its preview branch, via Supabase branching
Read-only. Never writes or moves your data
Runs on every PR, before merge

Start free

Starting journey analysis…

This may take a few minutes. Stay on this page to see live pipeline updates.

Analyzing Schema

Events from codebase

Generating Journey

Discovery

From sign up to account creation

SIGNAL	TYPE	FOUND AT	STATUS
Account Created	Supabase	public.accounts	Can be tracked (DB)
Signup Page Viewed	GitHub	app/admin/(auth)/login/page.tsx	Recommended
Signup Form Submitted	GitHub	app/admin/(auth)/login/page.tsx	Recommended
Auth User Created	Supabase	auth.users	Can be tracked (DB)
auth.users.insert	GitHub	–	Can be tracked (DB)
user creates an account record	GitHub	–	Can be tracked (DB)

refactor: consolidate checkout flow tracking

Open

feat/checkout-v2→main

skenebotcommented now

Analytics diff detected

Missing callcheckout_started: not found in new state

Renamed eventpurchase_complete → order_confirmed

Payload shape changecart_viewed: field "items" removed

Conditional no longer firesupsell_shown: condition block unreachable

Caught on review. Not on a dashboard that's been wrong for weeks.

Never lose data you can't get back.

Every way an agent quietly breaks a write.

Removed or renamed writes
Wrong types, or payloads your schema cannot store
Conditional writes that stopped firing
Flagged as a PR comment, not weeks later

Start free

Report numbers you can stand behind.

Tracking that compiles is not tracking that works.

Checks every event against its Supabase table
Catches renames that still pass your tests
Names the event, column, and what stops recording

Start free

Analytics events

checkout_started

purchase_complete

cart_viewed

public·events

event_nametext

order_idint4

cart_itemsmissing

created_attimestamptz

Skene checking events against schema…

feat: add purchase_complete tracking

Open

feat/purchase-events→main

skenebotcommented now

Schema mismatch detected

purchase_complete→public.events

Type mismatchpayload.purchase_id · text → column is int4

Missing columnpayload.cart_items · column does not exist

From trustworthy tracking to revenue decisions.

A baseline of every event write you already have, with drift caught on the PR that introduced it. Then query that trusted data over MCP for the paths, cohorts, and features that drive revenue.

Start free

1. EVERY EVENT WRITE, INDEXED AGAINST YOUR SCHEMA

2. DRIFT CAUGHT ON THE PR THAT INTRODUCED IT

3. THE PATHS AND COHORTS THAT PAY, OVER MCP

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.

Start with a one-time repo audit, or wire the GitHub Action into CI. Same engine behind each.

Start free Read more

MCP server

Cursor · Claude Code

GitHub Action

Runs on every PR

Cloud API

Any script, any time

Repo audit

One-time · no commitment

MCP server

Skene runs before the agent commits. Catches analytics issues in the agent loop, not after the PR lands.

skene mcp --cursor

Separation of duties

The agent writes the tracking. It should not grade its own work.

An agent checking the tracking it just wrote is the conflict of interest the check exists to remove. Skene runs alongside Cursor, Claude Code, and Codex, not inside them. The gate sits outside the tool that made the change.

It is not a dashboard you babysit or a copy of your data. Your data stays in your database. Skene owns the gate, and the trusted record you query over MCP for what drives revenue.

119 stars

Open GitHub

See what your last 10 PRs quietly broke.

Start free, or install the open-source core. Your first repo audit runs in about as long as your CI does.

Start free

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

Start free →

Scale

$99/mo

6M monthly tokens

Local MCP server
GitHub Action with PR comments
Cloud validation API
6M monthly tokens (4x Pro)

Start free →

Ultra

$199/mo

15M monthly tokens

Local MCP server
GitHub Action with PR comments
Cloud validation API
15M monthly tokens (10x Pro)
Priority support

Start free →

Trust your product data.

SIGNAL

TYPE

FOUND AT

STATUS

Account Created

Supabase

public.accounts

Can be tracked (DB)

Signup Page Viewed

GitHub

app/admin/(auth)/login/page.tsx

Recommended

Signup Form Submitted

GitHub

app/admin/(auth)/login/page.tsx

Recommended

Auth User Created

Supabase

auth.users

Can be tracked (DB)

auth.users.insert

GitHub

–

Can be tracked (DB)

user creates an account record

GitHub

–

Can be tracked (DB)

Trust your product data.

You can't get today's data back tomorrow.

Trust the data your decisions run on.

Never lose data you can't get back.

Report numbers you can stand behind.

From trustworthy tracking to revenue decisions.

Four ways to plug Skene in.

The agent writes the tracking. It should not grade its own work.

Built in the open,
with our design partners.

See what your last 10 PRs quietly broke.

Pay for cloud validation runs.

Trust your product data.

You can't get today's data back tomorrow.

Trust the data your decisions run on.

Never lose data you can't get back.

Report numbers you can stand behind.

From trustworthy tracking to revenue decisions.

Four ways to plug Skene in.

The agent writes the tracking. It should not grade its own work.

Built in the open,
with our design partners.

See what your last 10 PRs quietly broke.

Pay for cloud validation runs.

Trust your product data.

You can't get today's data back tomorrow.

Trust the data your decisions run on.

Never lose data you can't get back.

Report numbers you can stand behind.

From trustworthy tracking to revenue decisions.

Four ways to plug Skene in.

The agent writes the tracking. It should not grade its own work.

Built in the open,with our design partners.

See what your last 10 PRs quietly broke.

Pay for cloud validation runs.

Trust your product data.

You can't get today's data back tomorrow.

Trust the data your decisions run on.

Never lose data you can't get back.

Report numbers you can stand behind.

From trustworthy tracking to revenue decisions.

Four ways to plug Skene in.

The agent writes the tracking. It should not grade its own work.

Built in the open,with our design partners.

See what your last 10 PRs quietly broke.

Pay for cloud validation runs.

Built in the open,
with our design partners.

Built in the open,
with our design partners.