Skip to content
Product
Command

/skene-deploy

Deploy telemetry upstream after build. Expects skene-context/engine.yaml, skene-context/feature-registry.json (or configured output_dir; legacy skene/feature-registry.json still works), and supabase/migrations/*_skene_triggers.sql; push uploads the package to Skene Cloud.

BOOST
From plugin
skene
1266 skills6 commands
Install
$ npx -y skills add skenetechnologies/skene --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/skene-deploy

Context preview

What this command does when you run it.

Deploy telemetry upstream after build. Expects skene-context/engine.yaml, skene-context/feature-registry.json (or configured output_dir; legacy skene/feature-registry.json still works), and supabase/migrations/*_skene_triggers.sql; push uploads the package to Skene Cloud.

Command definition

skene-deploy.md
name: skene-deploy
description: Deploy telemetry upstream after build. Expects skene-context/engine.yaml, skene-context/feature-registry.json (or configured output_dir; legacy skene/feature-registry.json still works), and supabase/migrations/*_skene_triggers.sql; push uploads the package to Skene Cloud.

Deploy Telemetry

1. Invoke the `deploy-telemetry` skill. 2. Run `uvx skene push --help` first to discover available flags. 3. **Run autonomously** except: ask the user to confirm before `uvx skene push` (upstream deploy — genuine blocker). Ensure `uvx skene build` has been run so `*_skene_triggers.sql` exists. 4. Report engine, feature registry (if included), and trigger migration sent; suggest `/skene-status`.

Ships withskene

Product-Led Growth (PLG) analysis toolkit that detects tech stacks, plans growth loops and builds the loop iteratively.

Get the whole plugin

Other commands on skene.