Growth Lab: An Open Source AI Growth Agent Framework, With a Real Language Catch
Growth Lab is an open source AI growth agent framework for Claude Code and Codex that runs a full research-to-review loop. Its SEO growth loop genuinely transfers to English-language teams. Its second loop, and most of its underlying skill files, do not.
Most AI marketing tools solve one step of growth and leave a person to stitch the rest together: one tool for keyword research, another for drafting, another for publishing, another for reading the analytics afterward. Growth Lab is an open source AI growth agent framework built to run the whole loop, research, content, execution, and review, inside a single Claude Code or Codex session. It has climbed fast on GitHub, and the code behind it is real. It also comes with a catch worth stating plainly before anyone clones it: this is a Chinese-first project, and the language gap runs deeper than the README.
What Growth Lab actually does
Growth Lab isn't an app with a dashboard. It's a set of "Skills," in the Claude Code and Codex sense, plus supporting scripts, that turn an AI coding agent into a growth operator. The project's own framing is a repeating loop: understand the product, figure out who needs it and where, research the channel, form a strategy, create and publish, then read the real results back in before deciding the next move. That loop, and its underlying structure of a Model (the loop coordinator), a Skill (the method), a Client (the external tool access), and a filesystem-based Memory (what happened last time), is the actual product. The AI session is the control plane. Nothing runs as an unattended background job; you talk to it, it works, it reports back, you steer the next round.
Two loops are built out today. The first is an SEO page growth loop: it researches what your users are actually searching for, drafts an SEO page meant to answer that search and route to your product, submits it via IndexNow, and later reviews how it performed. The project's own logged run reports new pages getting indexed within one to two days, and a 1,000% increase in impressions and clicks on a 7-day average, alongside a 50% drop in overall CTR (expected, since the CTR base grew off a much larger pool of impressions). Read that as one recorded run and evidence for iteration, not a guaranteed outcome; the README says as much.
The second loop targets Xiaohongshu, the Chinese social platform that blends Instagram-style images with Pinterest-style discovery. It handles collecting high-performing posts, replicating a proven structure with real product content, generating images and rendering cards, running a compliance check, and reviewing results after a human publishes.
The language reality, checked directly rather than assumed
The repo's default README is Chinese, with an English translation (README.en.md) linked at the top alongside ten other languages. That translation is genuinely well done, not the stiff, half-broken English that comes out of a pure machine pass. Read on its own, it reads like it was written by someone fluent in both languages.
The catch is that the README is the only consistently bilingual layer. Below it, the actual Skill files an agent reads to execute each loop are inconsistent. The top-level SEO loop coordinator file (models/run-seo-page-loop/SKILL.md) is written in clean English. But the collector and executor Skills that do the real work underneath it, research-seo-demand, create-seo-page, review-seo-page, are Chinese-only, no English version provided. The Xiaohongshu loop's entire skill file is Chinese-only as well. So the honest picture is: the marketing pitch (README) is well translated, but a meaningful share of the operating instructions themselves are not.
In practice this matters less than it would for a human reading raw documentation, because Claude Code and Codex are fluently bilingual and will execute Chinese-language Skill instructions correctly without a person needing to translate anything by hand. What it costs an English-speaking team is auditability: if you want to actually read what a Skill tells the agent to do, verify a claim, or edit the method yourself before trusting it with a live SEO page, you're reading Chinese source files, not English ones, for most of the SEO loop's internals and effectively all of the Xiaohongshu loop.
What transfers, and what doesn't
The SEO growth loop is the part of this repo worth a look for an English-speaking small business, precisely because SEO from a Claude Code or Codex session, with demand research, page drafting, adversarial review, and post-publish measurement wired into one loop, is not something most teams have assembled themselves. The underlying four-step pattern, understand the product, research demand, act, review the real result before the next action, is also a genuinely reusable way to think about running any growth channel through an agent, independent of this specific codebase.
The Xiaohongshu loop is not useful to a reader outside that platform's market. It depends on a browser-based local MCP server for a Chinese platform with no meaningful audience outside China, and its skill file isn't translated. There's no reason to install it unless Xiaohongshu is genuinely one of your channels.
Who this fits, and who it doesn't
Growth Lab fits a technical operator, comfortable running Claude Code or Codex against their own codebase, who wants to add a real SEO research-and-publish loop rather than another AI writing prompt. It's open source under the Apache 2.0 license, stores everything (product context, memory, research, output) inside your own workspace rather than a vendor's, and the configuration for the SEO loop doesn't require touching any of the Chinese-only files at all.
It's a weaker fit for a non-technical marketer expecting a hosted tool with a UI, since setup runs entirely through natural-language prompts to a coding agent. It's also a poor fit for anyone hoping to run the Xiaohongshu loop without a China-facing product, or for anyone who wants to fully audit every Skill file the agent is following before trusting it, since roughly half of that reading will be in Chinese even after you take the English README at face value.
Traction and verification
As of today, the repository sits at 1,194 stars and 105 forks, up sharply from the 472 stars logged just days ago, a genuine and continuing acceleration rather than a one-day spike. It's owned by an organization account (tsingyuai), licensed Apache 2.0, actively pushed to (last commit within the past two days), and built on a substantial codebase (roughly 76,000 lines of Python and 33,000 lines of JavaScript). This is a real, working project, not a stub riding a trending topic.
The bottom line
Growth Lab earns its star count on substance: a working SEO research-to-review loop, a reusable "understand, research, act, review" pattern, and a codebase that holds up under inspection. The honest caveat is that inspection itself is partial for an English reader. The pitch translates well; a large share of the actual instructions the agent runs on do not. Clone it for the SEO loop and the pattern it demonstrates, skip the Xiaohongshu loop entirely unless that market is already yours, and go in knowing that verifying the Chinese-only Skill files yourself will mean reading Chinese, translation tools or not.
Join the newsletter
AI workflows and systems, straight to your inbox.
No spam. Unsubscribe anytime.