Know if what you shipped actually landed.
You are the one who has to say whether activation moved, or where the funnel is leaking. Skene grades the change you shipped against your own data, and it checks first that your tracking is telling the truth, so the grade means something.
Sign in, connect one source, and the one-time analysis returns what you already collect.
See what's tracked today
Sign in and connect one source: the GitHub App or your Supabase project.
- See what's tracked
- Define landing
- Protect it
One source is enough to start
Sign in and connect one source, and the one-time analysis returns what you already collect.
Your team keeps shipping
Every release is checked against the plan, and a break is named where it happened.
Two source kinds, that's all
Today Skene connects to a GitHub repository and a Supabase project. There is no other connection yet.
Sign in and connect one source. Either is enough.
See what's tracked today.
Run the one-time analysis. Skene maps what exists, what is tracked but not placed, and what is missing.
- Regex over 16 analytics platforms, no model in it
- Finds what is tracked but not placed anywhere
Define what landing looks like.
GTM names the funnels and lifecycle moments it needs to trust. Skene derives the collection plan.
- A schema agent walks your database schema
- A code agent walks the repository
- Milestones merge by name into seven lifecycle stages
- Comparison
- Same inputs, same answer
- Fails a release
- A missing event, or a table that is not there
- Reported only
- A table that is there with no sample
- Model calls
- Separate and optional
Protect that as your team keeps shipping.
Skene checks every release against that plan and names the event, file and line where tracking went missing.
- Install the GitHub App, turn on pull request reviews
- Every pull request gets a review with comments on changed lines
trial_ended fires for a wider audience than planned at trial.ts:77See what's tracked. Define landing. Protect it as you ship.
The three steps are one loop, not a setup wizard. You run them in order once, and from then on the third one runs on every release without being asked.
See what's tracked. The one-time analysis reads the repository and the schema and returns what you already collect, what is tracked but never placed, and what is missing.
Define landing. You name the journey the business actually cares about. That definition becomes the collection plan every later check is measured against.
Protect it. Every release is checked against the plan, and a break is reported where it happened, in the pull request that caused it.