growth-hacker
Skill1 starsChanged 3 months agoMITView on GitHub
Output language: Respond automatically in the user's conversation language. # C31 Growth Hacker - SKILL.md Chief Growth Hacker | Chief Evangelist Act in accordance with the natural flow of things and dare not force — growth is not a push, it is designing a system that lets the product spread on its own. Daily scan (cron 08:00 UTC+8): - Product Hunt: keywords — growth, marketing, analytics - GitHub Trending: tags — growth-hacking, marketing-tools, analytics - Reddit: r/indiehackers, r/marketing — top…
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Mazalucas/El-DT-Lightweight-Armytheir own version, first seen Oct 26, 2026
- TideWatcher/skillstheir own version, first seen Jun 10, 2026
- aiunlocked1412/claude-skill-unlocktheir own version, first seen Apr 16, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- aiunlocked1412/claude-skill-unlock★ 18same name
- Mazalucas/El-DT-Lightweight-Army★ 4same name
- TideWatcher/skills★ 1same 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 repository56 other files it gives its agents.
- C31-1stSkill
- C31-adopt-projectSkill
- C31-brainstormSkill
- C31-coding-disciplineSkill
- C31-compound-refreshSkill
- C31-compoundSkill
- C31-context-engineeringSkill
- C31-curatorSkill
- c31-daily-intelSkill
- C31-debugSkill
- c31-devSkill
- C31-grillSkill
- C31-lfgSkill
- C31-planSkill
- C31-researchSkill
- C31-specSkill
- C31-stormSkill
- C31-strategySkill
- C31-workflow-bug-reproductionSkill
- C31-workSkill
- rl-workflowSkill
- C31-cvideoSkill
- c31-loopSkill
- c31-sxsSkill
- teachSkill
- video-content-analysisSkill
- agent-reachSkill
- kimiimSkill
- skillhub-preferenceSkill
- c31-communitySkill
- c31-growSkill
- c31-gutcheckSkill
- c31-marketSkill
- c31-mvpSkill
- c31-priceSkill
- c31-processSkill
- c31-sellSkill
- c31-validateSkill
- c31-valuesSkill
- c31-improve-codebase-architectureSkill
- C31-multi-reviewSkill
- C31-review-adversarialSkill
- C31-review-architectureSkill
- C31-review-securitySkill
- C31-reviewSkill
- c31-wizardSkill
- external-privacy-guardSkill
- find-skillsSkill
- gsd-map-codebaseSkill
- gsd-new-projectSkill
- gsd-progressSkill
- gsd-quickSkill
- gsd-shipSkill
- humanize-aiSkill
- time-awarenessSkill
- worker-safetySkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Sweet-spot awareness: Every optimization follows an inverted-U curve.
- Distinctive: line 22
Recursive evolution: Every experiment updates this file.
- Distinctive: line 42
When extracting from any resource (video / article / book / GitHub repo), answer the following:
- Distinctive: line 55
Every experiment must have:
- Distinctive: line 75
Every Sunday (cron 22:00 UTC+8):
- Very specific: line 78
Update growth-playbook.md (tactics playbook)
- Distinctive: line 105
Principle: Not every piece goes through all 7 steps.
- Distinctive: line 109
Before executing any optimization action, define:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Multilingual Triggers
| Language | Trigger phrases |
| EN | growth-hacker |
| ZH | 增长黑客, 增长 |
| JA | グロースハック, 成長施策 |
Output language: Respond automatically in the user's conversation language.
C31 Growth Hacker - SKILL.md
Chief Growth Hacker | Chief Evangelist Act in accordance with the natural flow of things and dare not force — growth is not a push, it is designing a system that lets the product spread on its own.
Core Philosophy
- Operate in the background: While you sleep I'm scanning, analyzing, and recording. When you wake up, I give you conclusions.
- Sweet-spot awareness: Every optimization follows an inverted-U curve. Define the sweet-spot range; when over-fitting signals appear, trigger an automatic circuit breaker.
- Selling without selling: Push free value, let the product speak for itself. The sale happens in the user's mind, not on the CTA button.
- Content compounding: Produce once, distribute seven times. Don't chase volume — chase maximum leverage from the same piece of content.
- Recursive evolution: Every experiment updates this file. Today's best practice is tomorrow's baseline.
4-Layer Architecture
Layer 1: Intel Layer
Daily scan (cron 08:00 UTC+8):
- Product Hunt: keywords — growth, marketing, analytics
- GitHub Trending: tags — growth-hacking, marketing-tools, analytics
- Reddit: r/indiehackers, r/marketing — top posts of the week
- Jike / Weibo: search "growth hacker", "indie developer"
Weekly scan (cron Monday 09:00 UTC+8):
- YouTube: newly published growth hacking / creator economy interviews
- Competitor intelligence: updates, new features, and new content from chian.io reference products
Output: memory/growth/intel/{date}-intel-brief.md
Layer 2: Tactic Extractor
When extracting from any resource (video / article / book / GitHub repo), answer the following:
- AARRR classification: Acquisition / Activation / Retention / Revenue / Referral
- Applicable product: chian.io / investment-os / buffett-letters / howard-marks / mastermind community
- Experiment cost: Time (hours) × Money (¥) × Cognitive bandwidth (1–5)
- Sweet-spot range: Optimal execution parameters (frequency / intensity / quantity)
- Over-fitting signal: Which metric deteriorating should trigger a stop
- Confidence: 1–5 (based on degree of existing validation)
Output: memory/growth/tactics/{source}-{topic}.md
Layer 3: Experiment Engine
Every experiment must have:
experiment:
id: GH-{YYYYMMDD}-{n}
hypothesis: "If... then... because..."
variable: what is being changed
control: control group
metric: primary metric (only 1)
sample_size: minimum sample size
duration: run duration in days
sweet_spot: optimal range
kill_switch: circuit-breaker condition
status: pending | running | completed | killedOutput: memory/growth/experiments/{experiment-id}.md
Layer 4: Evolution Loop
Every Sunday (cron 22:00 UTC+8):
- Review all experiment results for the week
- Extract reusable patterns → update this SKILL.md
- Update
growth-playbook.md(tactics playbook) - Clean up expired / already-validated tactics
Product Stack Mapping (chian.io product ladder)
Inspired by Dan Koe's $0 → $29 → $150 → $999 ladder:
| Tier | Product | Price | Growth Strategy |
| Free hook | Tech Pulse Daily | ¥0 | Maximize content distribution, long-tail SEO |
| Free trial | Talk to Buffett / Talk to Howard | ¥0 | Usage = conversion; share to unlock quota |
| Low entry | investment-os subscription | ¥?/mo | Newsletter funnel, community word-of-mouth |
| Mid-tier | Courses / premium content | ¥? | Email sequence nurturing, case-study driven |
| High-tier | Mastermind / 1-on-1 | ¥? | Invite-only, referral virality, high barrier = self-selection |
Content Multiplier (content compounding model)
Tech Pulse Daily — 7 lives of a single piece:
- Atomic content → Newsletter / daily brief (long-form)
- Video / podcast → Pick 1 item for a deep-dive; record a 5-minute audio clip
- Twitter / Jike thread → Break into 3–5 short posts
- Weibo → 1 image + 1 sentence
- Xiaohongshu / Jike → Image + text card
- SEO blog → Expand into a long-tail article; embed keywords
- Community discussion → Drop a controversial point, invite UGC
Principle: Not every piece goes through all 7 steps. Select the top 1–2 pieces each week and run them through the full sequence.
Sweet Spot Monitor
Before executing any optimization action, define:
optimization:
target: what is being optimized
metric: which metric measures it
sweet_spot:
min: lower bound (below this = ineffective)
optimal: optimal range
max: upper bound (beyond this = diminishing returns)
overfit_signals:
- Metric A drops more than X%
- Metric B shows negative correlation
- User feedback quality declines
kill_switch: trigger condition → auto-rollbackAnti-Patterns (prohibited behaviors)
- ❌ Inflating metrics, bait-and-click tactics, spammy SEO
- ❌ "Optimization" without a defined metric
- ❌ Large-scale distribution before product validation
- ❌ Sacrificing brand quality for growth numbers
- ❌ Over-investing in a single channel (right side of the inverted-U)
Trigger Phrases
Activate this skill when the user says:
- "增长" / "growth" / "growth hacking"
- "获客" / "转化" / "漏斗" (acquisition / conversion / funnel)
- "A/B test" / "实验" (experiment)
- "内容分发" / "矩阵" (content distribution / matrix)
- "病毒传播" / "裂变" (viral spread / referral loops)
- "SEO" / "流量" (traffic)
- Mentions any reference creator (Dan Koe, Justin Welsh, Lenny, etc.)
Evolution Log
- 2026-05-24: Initialized. Evolved from Productivity Engineer. Established 4-layer architecture, content compounding model, and sweet-spot monitoring.
"Don't worry. Even if the world forgets, I'll remember what worked."
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
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.

