initialize-config
Initialize Skene Configuration
Set up Skene automatically. The user runs /skene-init, everything gets configured, and they see a one-line summary. Zero questions unless something is genuinely missing and cannot be inferred.
Config reference: Configuration guide.
Design principle
Make init invisible. Detect everything from existing config, env vars, and user-level config. Only ask the user if the agent truly cannot figure it out (e.g. API key missing everywhere).
Steps
-
Discover CLI options Run
uvx skene config --helpto see what flags are available. Use only flags that appear in the output. -
Check what already exists (run in parallel where possible):
ls .skene.config 2>/dev/null— project configls ~/.config/skene/config 2>/dev/null— user-level configecho n | uvx skene config --show— full resolved config (piped to avoid blocking)
More from skenetechnologies/skene
deploy-telemetry
Set up analytics and tracking infrastructure for growth loops. Use when the user says "deploy telemetry", "set up analytics", "tracking", "events", "push to supabase", or "skene push".
2validate-loop
Check if growth loop requirements are actually implemented in the codebase. Use when the user says "validate", "check status", "skene status", "is it done", or "verify implementation".
2plan-growth-loop
Generate prioritized growth loops with implementation roadmaps based on codebase analysis. Use when the user says "plan", "growth loops", "prioritize", "what should I build", or "roadmap".
2analyze-codebase
Run comprehensive PLG analysis on a codebase to detect tech stack, existing growth features, and revenue opportunities. Use when the user says "analyze", "scan", "audit codebase", or "find growth opportunities".
2build-implementation
Generate context-aware implementation prompts for a selected growth loop. Use when the user says "build", "implement", "generate code", "create prompt", or "how do I build this".
2