Skip to content

Integrations

Connect the evidence your release needs.

Code explains what should be tracked. Schema describes the product. Event sources show what arrived. Each connection contributes something different.
Start freeSee how it works

Skene workspace

Journey context and evidence checks

Code

GitHub

Tracking calls and changed code

Repository selection
Schema

Supabase

Tables, columns and types

OAuth and assigned projects
Event evidence

PostHog or Mixpanel

Evidence from received events

Source query credentials
Agent access

Hosted MCP

Authorized workspace tools

Credential scopes

You grant access. Skene checks the evidence each source supplies. Connected does not mean evidence available.

Code and review permissions.

Install the GitHub App on all repositories or a selected set. A workspace owner links the repository and branch, then enables reviews.
Permissions requested by the Skene GitHub App
PermissionAccessPurpose
ContentsRead & writeRead source and context files; propose updates through pull requests.
Pull requestsRead & writeRead changes, post reviews and open fix pull requests.
IssuesRead & writeRespond to /skene fix comments.
MetadataReadList repositories accessible to the installation.

Skene never pushes directly to your default branch. Your team reviews and merges proposed changes.

Read the GitHub connection guide

Source access and available evidence.

Supabase schema

Authorization

OAuth access and independently assigned production and development projects.

Supplied evidence

Schema supplies tables, columns and types. Measurement queries can read table evidence when the connected role permits it.

Review Supabase access

Event evidence

Authorization

PostHog’s HogQL query API or Mixpanel’s service account query API.

Supplied evidence

Events available through the connected source. Your application keeps sending events to its existing destination.

Event storage

Authorization

Separately configured credentials for an analytics destination in your Supabase storage.

Supplied evidence

The destination receives the skene.track() events your product sends. This is separate from read-only schema access.

Read destination setup

Agent access

Authorization

Hosted MCP credential with explicit workspace scopes.

Available work

Context and checking tools. Authorized journey write tools can save workspace definitions.

Explore the MCP server

Change access when the work requires it.

Supabase read-write access enables optional trigger deployment. Table reads depend on the connected role and the query. Upgrade through re-authorization, keeping project assignments. Returning to read-only requires disconnecting and reconnecting in that mode.

Optional deployment writes target the production project. A schema grant alone does not authorize the separate analytics destination.

Review all access boundaries

Start with one source.

Sign in, create a workspace and connect the evidence you already have. No card required.

Start with Skene