Skip to content
SkillScript-led1,413 tokens in use

Growth Engine

An experiment tracker for marketing: create tests with hypotheses, log data, score winners statistically, build a playbook, and get weekly scorecards and pacing alerts.

3,862 stars on the repository MIT Licenseericosiu/ai-marketing-skills · growth-engine
npx skills add ericosiu/ai-marketing-skills -s growth-engine
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Growth Engine costs

26tokens idle
1,413tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Script-led

Script-ledMixedModel-led

Most of this skill is scripts, so it behaves much the same whichever model runs it.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: autogrowth-weekly-scorecard.py, experiment-engine.py, pacing-alert.py.

Touches

shelldetectednetworkdetectedwrites filesdetectedcredentialsdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure25/25
  • Examples12/15
  • Output10/15
  • Size15/15
  • Resources9/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Fair
  • File that was not read−15

    a file the skill ships that was not read, so what it does is unknown

    .env.example
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 12
  • Reaches the network−10

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 148
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    autogrowth-weekly-scorecard.py, line 298
  • Reads credentials−15

    does this on the machine, and the frontmatter does not say so

    pacing-alert.py, line 33

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity88
  • Maintenance44
  • Community56
  • Maturity28
  • Momentum40

Growth Engine applies Karpathy’s autoresearch pattern to marketing channels. Its experiment engine creates A/B or multivariate experiments with a hypothesis, variable, variants and primary metric, logs data points as content is published, and scores each experiment with a bootstrap confidence interval and a Mann-Whitney U test.

An experiment moves from running to trending to keep or discard. A winner needs p below 0.05 and at least a 15 percent lift, and it is promoted automatically to a living playbook that you check before creating new content. Batch mode handles up to ten variants, and the engine can suggest the next variable to test. Two more scripts produce a weekly scorecard and check campaign pacing against targets.

What You Get

  • Tracked experiments with statuses running, trending, keep and discard
  • Statistical scoring with bootstrap confidence intervals and Mann-Whitney U
  • A living playbook of proven winners per agent
  • Suggestions for the next experiments
  • A weekly scorecard in Markdown across channels
  • Pacing alerts for lead and candidate targets against pipeline, recruiting and email APIs

Common Use Cases

  • Test subject lines or hooks across several variants and keep only significant winners
  • Check the playbook for proven rules before drafting new content
  • Review a weekly scorecard across all channels
  • Watch daily lead and weekly candidate pacing and get an exit code when behind

What Makes It Unique

Winner decisions come from statistics with explicit thresholds you can tune, such as p-value, minimum lift and samples per variant, with fewer samples needed for high-volume agents like content and email. Winners flow into a playbook that is meant to be read before the next piece of content, so learning compounds.

Under The Hood

It is script-led with three Python scripts that need numpy and scipy. The experiment engine stores experiments and the playbook as files in a data folder you configure. The pacing script calls your own pipeline, recruiting and email platform APIs over HTTP using bearer tokens that you provide as environment variables. On start the instructions also call two telemetry scripts that log usage locally, with remote telemetry only by opt-in; those scripts are not in this skill folder.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers