deploy-telemetry
Deploy Telemetry
Set up analytics infrastructure via the Skene CLI.
Agent behavior rules
- Autonomous. Run CLI commands, report results, suggest next step. No mid-flow questions except for genuine blockers.
- CLI is the source of truth. Do NOT fabricate migration schemas or client code if the CLI fails.
- User cannot type into agent terminals. Pipe safe defaults for routine prompts. Kill stuck terminals.
- Migrations are a genuine blocker. Ask the user in chat to confirm before running
uvx skene push— it writes migration files.
Steps
-
Discover CLI options Run
uvx skene push --helpto see available flags. Use only flags that appear in the output. -
Verify prerequisites
ls skene-context/growth-loops/ 2>/dev/null— if missing: "Run/skene-planfirst." Stop.ls supabase/ 2>/dev/null— if missing: "No Supabase directory. Set up Supabase first."
More from skenetechnologies/skene
validate-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".
2initialize-config
Set up Skene configuration for a project. Use when starting a new PLG analysis, when .skene.config is missing, or when the user says "skene init", "set up skene", or "configure skene".
2