Command Claude Code
Analyze current codebase for PLG opportunities. Scans tech stack, detects existing growth features, identifies revenue leakage, and updates the feature registry.
Product-Led Growth (PLG) analysis toolkit that detects tech stacks, plans growth loops and builds the loop iteratively.
Command Claude Code
Analyze current codebase for PLG opportunities. Scans tech stack, detects existing growth features, identifies revenue leakage, and updates the feature registry.
Command Claude Code
Build an implementation prompt for the selected growth loop. Generates context-aware instructions with code examples and testing checklists.
Command Claude Code
Deploy telemetry upstream after build. Expects skene-context/engine.yaml, skene-context/feature-registry.json (or configured outputdir; legacy skene/feature-registry.json still works), and supabase/migrations/skenetriggers.sql; push uploads the package to Skene Cloud.
Command Claude Code
Initialize Skene configuration for this project. Creates .skene.config (TOML), sets up provider and API key (or SKENEAPIKEY), and runs validation.
Command Claude Code
Generate a prioritized growth loop implementation plan. Creates a list of growth loops ranked by impact and effort, with estimated implementation time.
Command Claude Code
Check implementation status from skene-context/engine.yaml. Validates features, action vs code-only mode, and that trigger/function SQL exists in migrations; detail shows latest matching file and (+N) if duplicates.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: