deploy-telemetry
/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".
- Author
- skenetechnologies ↗
- Repository
- skene ↗
- Licence
- MIT
- Last repository change
- 26.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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".
Triggers from the description
Original author description
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".
How it works
- Agent behavior rules
- Steps
- Error handling
- Output
SKILL.md preview
---
name: deploy-telemetry
description: 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".
---
# 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.
- **Upstream push can be a genuine blocker.** Ask the user in chat to confirm before running `uvx skene push` — it POSTs `skene-context/engine.yaml`, `{output_dir}/feature-registry.json` when present, and the latest trigger migration to Skene Cloud (it does not generate SQL; run `uvx skene build` first if artifacts are missing).
## Steps
1. **Discover CLI options**
Run `uvx skene push --help` to see available flags. Use only flags that appear in the output.
2. **Verify prerequisites**
- `skene-context/engine.yaml` must exist; trigger SQL lives under `supabase/migrations/` as `*_skene_triggers.sql` after `uvx skene build` (older projects may use legacy `*skene_trigger*` / `*skene_telemetry*` filenames).
- Feature registry: default `skene-context/feature-registry.json` (or `{output_dir}` from config; legacy `skene/feature-registry.json` auto-detected). If missing, push still runs but omits the registry until `build` creates it.
- If engine or migrations are missing: tell the user to run `uvx skene build` first, then retry deploy.
- `ls supabase/ 2>/dev/null` — if missing: "No Supabase directory. Set up Supabase first."
3. **Ask user to confirm**
Tell the user: "`uvx skene push` uploads engine, feature-registry.json (if present), and latest `*_skene_triggers.sql` to upstream. Proceed?"
Wait for confirmation.
4. **Run push**
After user confirms, run `uvx skene push` with appropriate flags from --help output.
Report which migration file was packaged (latest eligible under `supabase/migrations/`) and that upstream received the deploy.
5. **Report result**
Engine path, registry path (if packaged), trigger migration path, next step: apply DB migrations locally if needed (`supabase db push`), then "Run `/skene-status` to verify."
6. **Privacy reminder** (one line)
"Remember GDPR/CCPA consent management before production tracking."
## Error handling
- **CLI failure**: Report error, suggest fix.
- **Permission errors**: Give user the command for their terminal.
## Output
Deploy result (or error), paths used, next step (`/skene-status`).
Versions
The database has no other skills named deploy-telemetry.
Database snapshot: 13.11.2026 · package version 4a88a2be3d80 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95product-tracking-design-tracking-plan
Design an opinionated target tracking plan and produce an explicit delta from current state to target. Combines the product model, current-state audit, and telemetry best practices to decide what events, properties, entities, and group hierarchies should exist. Outputs… - 100telemetry-standards
PostHog event tracking standards for Supabase Studio. Use when adding useTrack() calls, defining events in packages/common/telemetry-constants.ts, implementing tracking for a new feature, or reviewing PRs for telemetry compliance. Covers event naming, property conventions,… - 100api-analytics-posthog-analytics
PostHog event tracking, user identification, group analytics for B2B, GDPR consent patterns. Use when implementing product analytics, tracking user behavior, setting up funnels, or configuring privacy-compliant tracking. - 90mobile-analytics
Designs and reviews product analytics across Flutter, Android, iOS, React Native and Kotlin Multiplatform. Use for tracking plans, event names and properties, funnels and conversion events, screen tracking, analytics identity across sign-in and sign-out, consent-gated collection… - 100rawbbit-game-events
Design, document, implement, migrate, or maintain Rawbbit event tracking in a Unity or browser-JavaScript game, including existing analytics and dual-write decisions. Use when the user wants to add game analytics or telemetry, instrument or track gameplay events, design an event… - 100product-tracking-design-tracking-plan
Design an opinionated target tracking plan and produce an explicit delta from current state to target. Combines the product model, current-state audit, and telemetry best practices to decide what events, properties, entities, and group hierarchies should exist. Outputs…