Skene

Skene helps teams define a launch outcome, check its tracking and read the resulting measurement. The official overview positions it alongside existing analytics rather than as a replacement dashboard. Its workflow connects the plan, required evidence and result as code changes.

Define evidence before the launch

A plan records the hypothesis, success metric, reporting window, required events and fields, and calculation. An optional target lets the team compare the measured result with its intended outcome. The initial analysis maps existing, misplaced and missing tracking.

The documented repository scan uses regular expressions across analytics platforms without a model in that first analysis. Finding an event in code is distinct from counting it in connected data. Skene also keeps unavailable measurements separate from zero.

Define the question and data requirements before shipping. The publisher explicitly says a difference between periods shows change, not causation; its illustrative activation figures are not results measured for your product.

Review permissions as well as suggestions

Skene Cloud reviews linked GitHub pull requests for removed or broken tracking. Required events that break can trigger change requests; a later passing review dismisses earlier requests. That is a tracking check, not proof that the launch achieved its business goal.

The GitHub App has read-and-write permissions for contents, pull requests and issues. A repository user can request a fix that opens a follow-up pull request; the page says Skene never pushes to the default branch. This differs from the read-only first analysis.

Cloud documentation names GitHub, Supabase and PostHog or Mixpanel. Confirm another stack before choosing a plan. Disconnecting a Skene repository is separate from uninstalling its GitHub App, and Supabase triggers deployed through read-write access remain until separately removed. Understand those permissions and cleanup steps before connecting production systems.

Choose cloud monitoring or the CLI

The free cloud offer is one audit per workspace, once, behind sign-in. Pro adds ongoing tracking checks; Enterprise is tailored to the customer's systems. A free audit is not continuous monitoring.

The features page distinguishes Skene OSS, an MIT-licensed command-line tool that needs no Skene account. It runs on your machine, but you supply the model provider. Do not equate a local CLI installation with a guarantee that every selected provider processes data locally.

Start with the source and permissions needed for one useful question, then check the evidence before adopting monitoring. This overview follows published behavior and does not report a repository connected or a production database inspected.