/launch-in-app-experiments

Coordinates in-app experiments targeting activation, expansion, or monetization.

gtmagents@gtmagents

GitHub

From plugin

gtm-agents

368199 skills200 agents199 commands

Install

$ npx -y skills add gtmagents/gtm-agents --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/launch-in-app-experiments

Context preview

What this command does when you run it.

Coordinates in-app experiments targeting activation, expansion, or monetization.

Command definition

launch-in-app-experiments.md

name: launch-in-app-experiments
description: Coordinates in-app experiments targeting activation, expansion, or monetization.
usage: /product-led-growth:launch-in-app-experiments --surface dashboard --goal activation --variants 3 --guardrails churn,latency

Command: launch-in-app-experiments

Inputs

**surface** – product area (dashboard, onboarding, billing, collaboration, mobile).
**goal** – activation | engagement | monetization | retention.
**variants** – number of experiment arms (including control).
**guardrails** – comma-separated guardrail metrics to monitor.
**audience** – persona/segment targeting (role, plan, region, cohort).
**notes** – optional context or risk flags.

Workflow

1. **Hypothesis Intake** – capture hypotheses, prior learnings, and success metrics. 2. **Design Package** – define variant specs, targeting, triggers, and messaging. 3. **Instrumentation & Guardrails** – ensure events, tracking, and guardrails are wired. 4. **Launch & Monitoring** – deploy experiment, monitor metrics, trigger alerts. 5. **Readout Prep** – summarize results, decisions, and follow-up actions.