Nobody lists what to measure.
The goal is set, but not the data needed to check it.
For growth teams
Skene is an AI tool between
growth and engineering
Tell it what you’re testing and your target. Skene makes sure your product tracks it, then tells you if you hit it.
Help me plan our team invitations experiment
Skene
Experiment planSkene drafts your tracking plan.
Get invited teammates active
Target: 40% of invited teammates activate
Goal defined2 events to check
Works with GitHub, Supabase, PostHog and Mixpanel.
Growth teams can’t learn from
experiments they can’t measure.
Three things usually go wrong.
Tracking waits behind features.
Engineering builds features first.
Code changes break tracking.
A later change deletes an event the experiment needs.
“Claude really loves Skene’s PR checks because it wants every check to pass. When a Skene check flags an issue, Claude notices it and works to fix it before the PR merges. That clear green-or-red signal, right in the PR, is exactly what we look for.”
Pandelis Zembashis Co-founder, Composal (YC F26)
How Skene works
01 / Plan
Describe the experiment and your target.
One sentence is enough. Skene drafts the plan.
You define the goal
Help more invited teammates become active.
Skene drafts the tracking plan
ExperimentTeam invitations
AudienceExisting customers
Target40% of invited teammates activate
Window14 days after launch
Invitation sentTeammate activated
Your draft is ready for review.
02 / Track
Skene checks your code for the data.
Missing tracking goes to your developers as a ready task.
Skene checks the required events
One requirement needs tracking.
invitation_sent Found in codeteammate_activatedMissingYour team reviews tracking changes
Engineering adds the activation event, then Skene checks again.
Tracking in the code and events received are checked separately.
03 / Result
Skene tells you if you hit the target.
If you missed, it suggests what to try next.
Skene checks the result against your plan
Teammate activation38.6%
Target 40%Below target by 1.4 percentage points.
482 of 1,248 invited teammates activatedFirst 14 days after launch
Earlier checks stay in Check history.
What it does
One plan per experiment, from goal to result.
Skene keeps all four linked.
Plan: what you’re testing and the target.
Checklist: the events needed to measure it.
Code: where Skene finds missing events.
Pull request checks: keep tracking from breaking.
From planTo result
Plan, tracking and result on one page.
Experiments / Team invitations
Results available Plan your experiment Check your data Review your results
Experiment overview
See how your experiment is doing.
Invitations sent1,248During the measurement window
Teammates activated482From invitations sent
Activation rate38.6%Target 40% · Not reached
Invited teammates becoming active Activation rate
Launch dayDay 7Day 14
Skene confirmed both required events are being received.
Start with one sentence.
Skene drafts the goal and audience. You approve.
Your next experimentA sentence starts it.
Every code change is checked.
Skene flags a removed event before it merges.
Before launch
invitation_sent Foundteammate_activatedMissingResults checked against your target.
Skene compares them when the window closes.
Activation rate38.6%Target 40%
“I developed event tracking for our experiments, then with the next pull request those went missing. Skene fixes this problem in our PRs.”
Justin Crites GTM Engineer, Dreambase
Free within a usage allowance. No card needed.
Measure your first experiment free