Resources / Playbooks

Analytics validation playbooks

Step-by-step playbooks for the analytics work a team running coding agents has to do. Each playbook covers problem context, what breaks, a system approach, execution steps, metrics, and failure modes.

Playbooks

Start with the audit. Then pick whichever covers your current situation.

Review your current event taxonomyStart by mapping the repository. A Skene OSS run writes a journey document that your team can inspect alongside the tracking code.

Job-to-be-done: Map the tracking calls found in your repository and review gaps in their meaning.

Open playbook

Set up Skene for a Supabase codebaseStep-by-step for repos that write events into Supabase. Covers the MCP install, the GitHub Action, and how to baseline the existing surface.

Job-to-be-done: Wire Skene up against the events your code writes into Supabase so future PRs get validated.

Open playbook

Fix dashboards that have already driftedRecovery playbook. When you discover the funnel has been wrong for weeks, here is the order of operations to get back to honest data.

Job-to-be-done: Recover from a known instrumentation drift incident: the dashboard is wrong, find out why and stop it from happening again.

Open playbook

Validate analytics in CI as part of code reviewTreat instrumentation drift like any other code regression: caught on the PR, fixed before merge, reviewed by humans on the same surface they review everything else.

Job-to-be-done: Make analytics drift a blocking signal on PRs, the same way type errors and failed tests are.

Open playbook

Catch instrumentation breakage from coding agentsWhen the agent is writing the code, the agent is the first reviewer, and the earlier Skene's signal reaches it, the cheaper the fix.

Job-to-be-done: Make sure your coding agent (Cursor, Claude Code, Codex, Devin) finds out about analytics drift before it commits.

Open playbook

Migrate from one analytics tool to another without losing fidelityMoving events from one backend to another, including into your own Supabase. The SDK swap is the easy part. The hard part is getting every event across without silently losing or renaming it.

Job-to-be-done: Move from one analytics backend (or CDP) to another while preserving the event taxonomy you already trust.

Open playbook