agentleFS
admdanielpaulinoadmdanielpaulino/claude-codes/growth-engine/SKILL.md

growth-engine

Skill1 starsChanged 7 months agoMITView on GitHub

Privacy: This skill logs usage locally to ~/.ai-marketing-skills/analytics/. Remote telemetry is opt-in only. No code, file paths, or repo content is ever collected. See telemetry/README.md. 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). Use this skill when: - Creating or managing A/B or…

  • Installs packages

5 other projects use a version of this, 1 of them edited.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 21
  2. Distinctive:

    Do NOT use for:

    line 29
  3. Very specific:

    Add --batch-mode for 3-10 variant tests.

    line 47
  4. Distinctive:

    Always check the playbook before creating new content to apply proven best practices.

    line 77
  5. Very specific:

    Before creating content: playbook → apply proven rules

    line 98
  6. Very specific:

    When publishing: log → record which variant was used and its metrics

    line 99
  7. Very specific:

    After completing experiments: suggest → pick the next variable to test

    line 102

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Growth Engine

Preamble (runs on skill start)

# Version check (silent if up to date)
python3 telemetry/version_check.py 2>/dev/null || true

# Telemetry opt-in (first run only, then remembers your choice)
python3 telemetry/telemetry_init.py 2>/dev/null || true

Privacy: This skill logs usage locally to ~/.ai-marketing-skills/analytics/. Remote telemetry is opt-in only. No code, file paths, or repo content is ever collected. See telemetry/README.md.


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

VariableDescription
GROWTH_ENGINE_DATA_DIRData directory (default: ./data/experiments)
GROWTH_ENGINE_AGENTSComma-separated agent names (default: content,email,linkedin,seo,blog)

Optional Tuning

VariableDefaultDescription
HIGH_VOLUME_AGENTScontent,emailAgents needing only 10 samples/variant
LOW_VOLUME_AGENTSseo,linkedin,blogAgents needing 30 samples/variant
P_WINNER0.05p-value threshold for winner
P_TREND0.10p-value threshold for trending
LIFT_WIN15.0Minimum % lift for keep decision
BOOTSTRAP_ITERATIONS1000Bootstrap resamples for CI
BATCH_MODE_MAX_VARIANTS10Max variants in batch mode

Pacing Alert Variables

VariableDescription
PIPELINE_API_URLPipeline/CRM API endpoint
PIPELINE_AUTH_TOKENBearer token for pipeline API
RECRUITING_API_URLRecruiting API endpoint
RECRUITING_AUTH_TOKENBearer token for recruiting API
EMAIL_API_URLEmail platform API base URL
EMAIL_AUTH_TOKENBearer token for email platform
OUTBOUND_CAMPAIGNSJSON: {"name": "campaign-id"}
RECRUITING_CAMPAIGNSJSON: {"name": "campaign-id"}
DAILY_LEAD_TARGETLeads/day target (default: 10)
WEEKLY_CANDIDATE_TARGETCandidates/week target (default: 400)

Dependencies

pip install numpy scipy

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.