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
Most recently taken up by
- LazyIsEfficient/agentic-osedited, first seen Oct 22, 2026
- agentik-os/claude-code-skillstheir own version, first seen Sep 17, 2026
- ericosiu/ai-marketing-skillsword for word, first seen Sep 2, 2026
- KameronKales/planfi-skillstheir own version, first seen Jul 3, 2026
- varunk130/ai-marketing-claude-skillstheir own version, first seen May 18, 2026
Other versions5 projects use a version of this.
Word for word · 1
- ericosiu/ai-marketing-skills★ 3.8k100% same
Edited · 1
- LazyIsEfficient/agentic-os★ 1722% same
Wrote their own version · 3
- agentik-os/claude-code-skills★ 1same name
- varunk130/ai-marketing-claude-skills★ 1same name
- KameronKales/planfi-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- eval/CLAUDE.mdCLAUDE.md
- autoresearchSkill
- expert-panelSkill
- conversion-opsSkill
- deck-generatorSkill
- finance-opsSkill
- cold-outbound-optimizerSkill
- podcast-pipelineSkill
- revenue-intelligenceSkill
- sales-pipelineSkill
- sales-playbookSkill
- seo-opsSkill
- team-opsSkill
- x-longform-postSkill
- yt-competitive-analysisSkill
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
- Distinctive: line 21
Use this skill when:
- Distinctive: line 29
Do NOT use for:
- Very specific: line 47
Add --batch-mode for 3-10 variant tests.
- Distinctive: line 77
Always check the playbook before creating new content to apply proven best practices.
- Very specific: line 98
Before creating content: playbook → apply proven rules
- Very specific: line 99
When publishing: log → record which variant was used and its metrics
- Very specific: line 102
After completing experiments: suggest → pick the next variable to test
“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.
Files
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 || truePrivacy: 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. Seetelemetry/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 24Add --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
- Before creating content:
playbook→ apply proven rules - When publishing:
log→ record which variant was used and its metrics - Periodically:
score→ check if experiments have reached statistical significance - Weekly:
autogrowth-weekly-scorecard.py→ review all channels - 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 scipyDoes 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
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.

