CLI ToolsMay 14, 2026·3 min read

skene — PLG Tech-Stack Analyzer CLI

PLG codebase analyzer: detect stack, model user journeys, and generate implementation prompts via TUI/CLI. Verified 104★; pushed 2026-05-14.

Agent ready

Safe staging for this asset

This asset is staged first. The copied prompt tells the agent to inspect the staged files and ask before activating scripts, MCP config, or global config.

Stage only · 17/100Policy: stage
Agent surface
Any MCP/CLI agent
Kind
CLI Tool
Install
Stage only
Trust
Trust: Established
Entrypoint
Asset
Safe staging command
npx -y tokrepo@latest install 12805c07-34b4-5d3f-9b6c-5989c941dbd1 --target codex

Stages files first; activation requires review of the staged README and plan.

Intro

PLG codebase analyzer: detect stack, model user journeys, and generate implementation prompts via TUI/CLI. Verified 104★; pushed 2026-05-14.

Best for: Product and engineering teams who want codebase-driven growth-loop analysis with concrete outputs

Works with: TUI installer + Python CLI (uvx/pip); supports common LLM providers (README)

Setup time: 8-15 minutes

Key facts (verified)

  • GitHub: 104 stars · 12 forks · pushed 2026-05-14.
  • License: MIT · owner avatar + repo URL verified via GitHub API.
  • README-backed entrypoint: skene.

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_git

website docs blog reddit

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 skene from the terminal.
  • README documents running the CLI with uvx skene or installing via pip 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.
🙏

Source & Thanks

Created by SkeneTechnologies. Licensed under MIT.

SkeneTechnologies/skene — ⭐ 104

Thanks to the upstream maintainers and contributors for publishing this work under an open license.

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets