Skip to content

Skene OSS

Read the product through its code.

Analyze your repository and optional schema inputs. Inspect the journey milestones and their source evidence in a file you own.
Run Skene OSSRead the CLI docs
Analyse your repository
uvx skene analyse-journey .

Requires uv and a configured model provider. The command fetches the CLI without adding it to your application dependencies.

Install and open the TUI
curl -fsSL https://raw.githubusercontent.com/SkeneTechnologies/skene/main/tui/install.sh | bash
skene

The wizard guides provider configuration and analysis.

Include exported SQL
uvx skene analyse-journey . --schema-dir ./schemas

The published package supports exported SQL. Live PostgreSQL requires the source revision shown in the developer reference.

See the live database command

Use one schema input per run.

Skene OSS produces · You inspect

A journey with source evidence.

skene-context/journey.yaml

Lifecycle stages and milestones, with references to the code and schema behind them.

Code input
Your chosen repository
Optional schema input
Exported SQL; live database access with the verified source revision
Output
A local file, inspectable in your editor or the terminal UI

Local execution. Your choice of model.

Where analysis context goes depends on the provider you configure.
Your machine

Source inputs and output

The CLI reads chosen repository and schema inputs, then writes the journey artifact locally.

Provider credentials may be saved in configuration.
Chosen provider

Analysis context

Use a supported remote model or a local model service such as Ollama or LM Studio. Remote providers receive analysis context.

Your own provider does not require a Skene account.
Optional Skene Cloud

Separate authorization

The Skene provider requires authorization. When the TUI uses that provider and the linked workspace has no journey yet, it automatically publishes the first journey to Cloud.

Cloud publication is separate from writing the local file.

The database URL for schema introspection and the model API key are different credentials. Review each configuration separately.

MIT licensed

Keep the file and the tool that produced it.

Inspect and run the public source with your chosen provider. Hosted pull request reviews and the shared workspace belong to Skene Cloud, with separate account and access requirements.
Inspect the sourceOpen the reference

Bring the journey into a shared workspace.

Skene Cloud connects the team’s sources, journey context and review history. The free audit is a separate signed-in product.

See Skene Cloud