Main
Run the TUI first: it guides provider auth and produces a local analysis bundle you can review and diff over time.
Treat outputs as artifacts (
skene-context/): commit what you want to track (journey model, plan) and ignore secrets.Validate findings by linking each “growth loop” suggestion back to concrete code paths or schema elements.
Use generated prompts as starting points, then rewrite them to match your product constraints and risk profile.
README (excerpt)
Skene is a codebase analysis toolkit for product-led growth. It models your product's user journey from your schema and code, surfaces growth opportunities, and turns them into actionable implementation plans.
What It Does
- Journey-first analysis -- compiles a view of your product's user journey: lifecycle stages, milestones, and value points, derived from your schema and code
- Journey visualizer -- opens the compiled journey in a local web app, with the lifecycle stages and milestones laid out as a diagram alongside the underlying data
- Tech stack detection -- identifies frameworks, databases, auth, deployment
- Growth feature discovery -- finds existing signup flows, sharing, invites, billing
- Feature registry -- tracks features across analysis runs, links them to growth loops
- Revenue leakage analysis -- spots missing monetization and weak pricing tiers
Source-backed notes
- README Quick Start installs the TUI via a curl script and launches
skenefrom the terminal. - README documents running the CLI with
uvx skeneor installing viapip install skene. - README describes outputs written to a local bundle directory such as
./skene-context/.
FAQ
- Does it change my repo?: It primarily reads and writes analysis artifacts; review README for any optional write steps.
- Can I run without an API key?: README mentions a free local audit path; provider features depend on your setup.
- What’s a good first target?: A small service with clear signup or onboarding flow—so journey modeling is measurable.