INTEGRATIONS
What Skene works with.
Your Supabase database, your coding agents, your CI, and your repo host. The list is short on purpose. Skene knows the shape of the events you write and the schema they land in, instead of pretending to handle everything.
DATA STORE
Where your events land
- SupabasePostgres schema, read-only over OAuth. The tables your events land in, and the contract Skene checks against.
CODING AGENTS
Coding agents Skene watches
- CursorIDE agent
- Claude CodeCLI agent
- CodexCLI agent
- DevinAutonomous agent
CI
Where Skene runs in CI
- GitHub ActionsOfficial action, posts PR comments
- GitLab CICloud API integration
- Generic CICLI runs anywhere Node 20+ does
REPO HOSTS
Where your code lives
- GitHubFirst-class. Action and PR comments.
- GitLabCLI + MR notes.
- BitbucketCLI + pipeline integration.
Patch the code tomorrow. The data from this week is already gone.
A renamed event passes every test, ships green, and sits broken for weeks before anyone notices. Skene runs as a GitHub Action on every pull request, reads your Supabase schema read-only, and comments the moment a write breaks, while your data is still recoverable. Usage-based on tokens, with $5 of free cloud credit to start. A PR that touches none of your tracking costs nothing.
