How Skene works, end to end
This page walks through the lifecycle from connecting your repository to letting Skene Agent help you design and run product-led growth loops from your IDE.
If you want in-app steps for workspaces, sources, milestones, and widgets, see the getting started guide in the Skene product docs.
From repo to growth loops in four steps
Connect
Skene links to GitHub, GitLab, or Bitbucket via read-only authorization. No SDK or code changes are required to get started.
Analyze
Skene parses your code, APIs, configurations, and docs to build a semantic understanding of your product.
Design loops
Using Skene Agent in your IDE, you prompt and refine product-led growth loops based on that understanding.
Monitor
As you ship, Skene keeps track of changes in your repository and helps you decide how to adjust the loops you run.
What Skene needs to do its job
Skene treats your repository as the source of truth for how your product actually works.
A read-only connection to the repositories that contain your core product code and configuration.
Access to the APIs, configuration files, and key docs that describe how customers use your product.
No additional tracking scripts or in-app SDKs to get started—the focus is on what your code already does.
Who this workflow is designed for
Solo founders & small teams
Shipping directly from IDEs like Cursor or Windsurf.
Developer-first SaaS
Products that want PLG loops defined from the codebase, not a separate tool.
Growth-minded teams
Teams who want to see how growth ideas behave before investing in a heavy stack.
Ready to connect your first repository?
Start designing growth loops from your codebase in minutes.