/mkt-experiment
Autonomous growth experimentation framework. Creates A/B/multivariate experiments with hypotheses, logs data points, runs statistical analysis (bootstrap CI + Mann-Whitney U), auto-promotes winners to a living playbook, and suggests next experiments. Use when creating or
$ npx -y skills add evolution-foundation/evo-nexus --skill mkt-experiment --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/mkt-experiment
Context preview
The summary Claude sees to decide when to auto-load this skill.
Autonomous growth experimentation framework. Creates A/B/multivariate experiments with hypotheses, logs data points, runs statistical analysis (bootstrap CI + Mann-Whitney U), auto-promotes winners to a living playbook, and suggests next experiments. Use when creating or
SKILL.md
mkt-experiment.SKILL.mdname: mkt-experiment
description: Autonomous growth experimentation framework. Creates A/B/multivariate experiments with hypotheses, logs data points, runs statistical analysis (bootstrap CI + Mann-Whitney U), auto-promotes winners to a living playbook, and suggests next experiments. Use when creating or managing marketing experiments, logging data points, scoring experiments, or generating weekly scorecards.
Growth Engine
Autonomous growth experimentation framework based on Karpathy's autoresearch pattern applied to marketing. Creates experiments with hypotheses, logs data points, runs statistical analysis (bootstrap CI + Mann-Whitney U), auto-promotes winners to a living playbook, and suggests next experiments. Supports batch mode (up to 10 variants simultaneously).
Usage
Use this skill when:
- Creating or managing A/B or multivariate experiments for any marketing channel
- Logging experiment data points after content is published or campaigns run
- Scoring experiments to determine statistical winners
- Checking the playbook for proven best practices before creating new content
- Generating weekly scorecards across all channels
- Monitoring campaign pacing and health
Do NOT use for:
- One-off content creation (use the playbook output as input, but don't run the engine)
- Non-experiment analytics or reporting
- Campaign setup in external platforms (this tracks experiments, not campaign config)
Commands
Create an experiment
python3 experiment-engine.py create \
--agent <agent_name> \
--hypothesis "What you expect to happen" \
--variable "<variable_name>" \
--variants '["variant_a", "variant_b"]' \
--metric "<primary_metric>" \
--cycle-hours 24
Add `--batch-mode` for 3-10 variant tests. Add `--min-samples N` to override auto-detection.
Log a data point
python3 experiment-engine.py log \
--agent <agent_name> \
--experiment-id <EXP-ID> \
--variant "<variant_name>" \
--metrics '{"metric_name": value}'Score an experiment
python3 experiment-engine.py score --agent <agent_name> --experiment-id <EXP-ID>
Statuses: `running` → `trending` → `keep` (winner) or `discard` (loser)
Winners auto-promote to the playbook. Requires p < 0.05 AND ≥ 15% lift.
List experiments
python3 experiment-engine.py list --agent <agent_name> [--status running|trending|keep|discard]
Check the playbook
python3 experiment-engine.py playbook --agent <agent_name>
Always check the playbook before creating new content to apply proven best practices.
Suggest next experiments
python3 experiment-engine.py suggest --agent <agent_name>
Generate weekly scorecard
python3 autogrowth-weekly-scorecard.py [--weeks N] [--output file.md]
Check campaign pacing
python3 pacing-alert.py [--json]
Exit code 0 = on pace, 1 = alerts present.
Workflow
1. Before creating content: `playbook` → apply proven rules 2. When publishing: `log` → record which variant was used and its metrics 3. Periodically: `score` → check if experiments have reached statistical significance 4. Weekly: `autogrowth-weekly-scorecard.py` → review all channels 5. After completing experiments: `suggest` → pick the next variable to test
Configuration
Required Environment Variables
| Variable | Description | |----------|-------------| | `GROWTH_ENGINE_DATA_DIR` | Data directory (default: `./data/experiments`) | | `GROWTH_ENGINE_AGENTS` | Comma-separated agent names (default: `content,email,linkedin,seo,blog`) |
Optional Tuning
| Variable | Default | Description | |----------|---------|-------------| | `HIGH_VOLUME_AGENTS` | `content,email` | Agents needing only 10 samples/variant | | `LOW_VOLUME_AGENTS` | `seo,linkedin,blog` | Agents needing 30 samples/variant | | `P_WINNER` | `0.05` | p-value threshold for winner | | `P_TREND` | `0.10` | p-value threshold for trending | | `LIFT_WIN` | `15.0` | Minimum % lift for keep decision | | `BOOTSTRAP_ITERATIONS` | `1000` | Bootstrap resamples for CI | | `BATCH_MODE_MAX_VARIANTS` | `10` | Max variants in batch mode |
Pacing Alert Variables
| Variable | Description | |----------|-------------| | `PIPELINE_API_URL` | Pipeline/CRM API endpoint | | `PIPELINE_AUTH_TOKEN` | Bearer token for pipeline API | | `RECRUITING_API_URL` | Recruiting API endpoint | | `RECRUITING_AUTH_TOKEN` | Bearer token for recruiting API | | `EMAIL_API_URL` | Email platform API base URL | | `EMAIL_AUTH_TOKEN` | Bearer token for email platform | | `OUTBOUND_CAMPAIGNS` | JSON: `{"name": "campaign-id"}` | | `RECRUITING_CAMPAIGNS` | JSON: `{"name": "campaign-id"}` | | `DAILY_LEAD_TARGET` | Leads/day target (default: 10) | | `WEEKLY_CANDIDATE_TARGET` | Candidates/week target (default: 400) |
Dependencies
pip install numpy scipy
Read more
name: mkt-experiment description: Autonomous growth experimentation framework. Creates A/B/multivariate experiments with hypotheses, logs data points, runs statistical analysis (bootstrap CI + Mann-Whitney U), auto-promotes winners to a living playbook, and suggests next experiments. Use when creating or managing marketing experiments, logging data points, scoring experiments, or generating weekly scorecards.
Growth Engine
Autonomous growth experimentation framework based on Karpathy's autoresearch pattern applied to marketing. Creates experiments with hypotheses, logs data points, runs statistical analysis (bootstrap CI + Mann-Whitney U), auto-promotes winners to a living playbook, and suggests next experiments. Supports batch mode (up to 10 variants simultaneously).
Usage
Use this skill when:
- Creating or managing A/B or multivariate experiments for any marketing channel
- Logging experiment data points after content is published or campaigns run
- Scoring experiments to determine statistical winners
- Checking the playbook for proven best practices before creating new content
- Generating weekly scorecards across all channels
- Monitoring campaign pacing and health
Do NOT use for:
- One-off content creation (use the playbook output as input, but don't run the engine)
- Non-experiment analytics or reporting
- Campaign setup in external platforms (this tracks experiments, not campaign config)
Commands
Create an experiment
python3 experiment-engine.py create \ --agent <agent_name> \ --hypothesis "What you expect to happen" \ --variable "<variable_name>" \ --variants '["variant_a", "variant_b"]' \ --metric "<primary_metric>" \ --cycle-hours 24
Add `--batch-mode` for 3-10 variant tests. Add `--min-samples N` to override auto-detection.
Log a data point
python3 experiment-engine.py log \
--agent <agent_name> \
--experiment-id <EXP-ID> \
--variant "<variant_name>" \
--metrics '{"metric_name": value}'Score an experiment
python3 experiment-engine.py score --agent <agent_name> --experiment-id <EXP-ID>
Statuses: `running` → `trending` → `keep` (winner) or `discard` (loser)
Winners auto-promote to the playbook. Requires p < 0.05 AND ≥ 15% lift.
List experiments
python3 experiment-engine.py list --agent <agent_name> [--status running|trending|keep|discard]
Check the playbook
python3 experiment-engine.py playbook --agent <agent_name>
Always check the playbook before creating new content to apply proven best practices.
Suggest next experiments
python3 experiment-engine.py suggest --agent <agent_name>
Generate weekly scorecard
python3 autogrowth-weekly-scorecard.py [--weeks N] [--output file.md]
Check campaign pacing
python3 pacing-alert.py [--json]
Exit code 0 = on pace, 1 = alerts present.
Workflow
1. Before creating content: `playbook` → apply proven rules 2. When publishing: `log` → record which variant was used and its metrics 3. Periodically: `score` → check if experiments have reached statistical significance 4. Weekly: `autogrowth-weekly-scorecard.py` → review all channels 5. After completing experiments: `suggest` → pick the next variable to test
Configuration
Required Environment Variables
| Variable | Description | |----------|-------------| | `GROWTH_ENGINE_DATA_DIR` | Data directory (default: `./data/experiments`) | | `GROWTH_ENGINE_AGENTS` | Comma-separated agent names (default: `content,email,linkedin,seo,blog`) |
Optional Tuning
| Variable | Default | Description | |----------|---------|-------------| | `HIGH_VOLUME_AGENTS` | `content,email` | Agents needing only 10 samples/variant | | `LOW_VOLUME_AGENTS` | `seo,linkedin,blog` | Agents needing 30 samples/variant | | `P_WINNER` | `0.05` | p-value threshold for winner | | `P_TREND` | `0.10` | p-value threshold for trending | | `LIFT_WIN` | `15.0` | Minimum % lift for keep decision | | `BOOTSTRAP_ITERATIONS` | `1000` | Bootstrap resamples for CI | | `BATCH_MODE_MAX_VARIANTS` | `10` | Max variants in batch mode |
Pacing Alert Variables
| Variable | Description | |----------|-------------| | `PIPELINE_API_URL` | Pipeline/CRM API endpoint | | `PIPELINE_AUTH_TOKEN` | Bearer token for pipeline API | | `RECRUITING_API_URL` | Recruiting API endpoint | | `RECRUITING_AUTH_TOKEN` | Bearer token for recruiting API | | `EMAIL_API_URL` | Email platform API base URL | | `EMAIL_AUTH_TOKEN` | Bearer token for email platform | | `OUTBOUND_CAMPAIGNS` | JSON: `{"name": "campaign-id"}` | | `RECRUITING_CAMPAIGNS` | JSON: `{"name": "campaign-id"}` | | `DAILY_LEAD_TARGET` | Leads/day target (default: 10) | | `WEEKLY_CANDIDATE_TARGET` | Candidates/week target (default: 400) |
Dependencies
pip install numpy scipy
Other skills on evo-nexus.
- /ai-image-creator
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, proxied through Cloudflare AI Gateway BYOK). Also analyze/describe existing images using multimodal AI vision. Use when user asks to "generate an image",
Open skill - /create-agent
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the user says 'create an agent', 'new agent', 'add an agent', 'I need a custom agent', or wants to create a specialized agent
Open skill - /create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants
Open skill - /create-goal
Create a Mission, Project, or Goal (Mission → Project → Goal → Task hierarchy) in EvoNexus. Guides the user through picking a mission, choosing or creating a project, defining a measurable goal with metric_type and target_value. Writes to the SQLite goals tables via POST
Open skill - /create-heartbeat
Create a new heartbeat (proactive agent scheduled with a decision prompt) for EvoNexus. Guides the user through picking an agent, setting interval, wake triggers, and the decision prompt that governs when the agent acts. Writes to config/heartbeats.yaml with pydantic validation.
Open skill - /create-integration
Create a new custom integration (API/service wrapper) for the workspace. Guides the user through defining the integration's slug, display name, description, category, and required env keys. Writes .claude/skills/custom-int-{slug}/SKILL.md via POST /api/integrations/custom. Use
Open skill

