grow-sustainably
Skill12 starsChanged 49 days agoMITView on GitHub
Plan post-first-100-users growth without burning out the founder, the budget, or the user base. Pairs with `first-100-users` (which gets you to 100); this skill takes you from 100 to ~1000 sustainably. Activated when the user says "já tenho 100 usuários, e agora?", "como cresço sem queimar dinheiro?", "o WhatsApp 1-a-1 não escala mais".
8 other projects use a version of this.
Adopted by
Most recently taken up by
- tusshaarpd/skillstheir own version, first seen Nov 16, 2026
- scaccogatto/minimalist-entrepreneurtheir own version, first seen Oct 15, 2026
- suvimatt/agent-bootstrappertheir own version, first seen Aug 31, 2026
- kalias/OPC_starter_skillstheir own version, first seen Jul 20, 2026
- CarbeneAI/Forgetheir own version, first seen Apr 22, 2026
- keeea/minimalist-entrepreneur-skillstheir own version, first seen Apr 16, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- slavingia/skills★ 11ksame name
- keeea/minimalist-entrepreneur-skills★ 19same name
- CarbeneAI/Forge★ 9same name
- kalias/OPC_starter_skills★ 1same name
- scaccogatto/minimalist-entrepreneur★ 1same name
- suvimatt/agent-bootstrapper★ 1same name
- consubstantial-polistes407/skills★ 0same name
- tusshaarpd/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 repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- business-plan-impact-reviewSkill
- codemapSkill
- cost-watchdogSkill
- daily-standupSkill
- decision-logSkill
- deploy-vercel-supabaseSkill
- feature-scaffoldSkill
- first-100-usersSkill
- multi-ai-reviewSkill
- os-self-testSkill
- pitchSkill
- plain-portuguese-explainerSkill
- privacy-auditSkill
- processizeSkill
- product-briefSkill
- project-genesisSkill
- prototype-labSkill
- registry-pickSkill
- release-checkSkill
- research-wavesSkill
- rollback-safeSkill
- secrets-disciplineSkill
- secrets-scanSkill
- sprint-managementSkill
- sprint-roadmapSkill
- usage-monitorSkill
- verify-build-worksSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 8 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
If any pre-condition is missing, the skill stops and routes to: first-100-users (under 100), usage-monitor (no cost telemetry), or …
- Distinctive: line 37
If week-4 retention < 20%, do not scale acquisition.
- Distinctive: line 39
If retention is healthy (≥30% at week-4), proceed to Pillar 2.
- Distinctive: line 43
Look at the first 100. Where did they actually come from?
- Distinctive: line 47
Ask: what made it work? Was it the channel itself, the message, the timing, or the founder's personal voice?
- Distinctive: line 53
Only when Pillar 2 plateaus (≥4 weeks of flat or declining yield):
- Distinctive: line 58
After 30 days: keep, kill, or extend by another 30 days.
- Distinctive: line 62
Run this weekly during scaling:
- Distinctive: line 71
If any signal trips, scaling stops until it's fixed.
- Very specific: line 90
Always exhaust Tier 1 before Tier 2.
“Common” is measured: kept by at least 6 in 10 of the 7 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
Grow Sustainably
first-100-users is conversation-driven. Beyond 100, conversations alone don't scale. But the answer is NOT to dump money into ads. The answer is to compress what worked, plug retention holes, and add ONE honest distribution channel at a time.
This skill protects against the three classic post-100 failures:
- Founder burnout — trying to keep the 1-a-1 cadence past the personal limit.
- Vanity acquisition — buying signups that never activate.
- Channel diffusion — running 5 channels at 20% effort instead of 1 channel at 100%.
Pre-conditions
This skill assumes:
- ~100+ active users (active = completed the aha-moment + returned in 7d).
- Some retention data exists (week-1, week-4 returning users).
- At least one acquisition pattern that worked manually (a specific community, a specific cold outreach script, a specific content theme).
- Cost telemetry exists (
usage-monitorrunning) — otherwise scaling will quietly bankrupt the OPEX.
If any pre-condition is missing, the skill stops and routes to: first-100-users (under 100), usage-monitor (no cost telemetry), or daily-standup (no retention data captured).
The four pillars (run in order, never in parallel)
Pillar 1 — Retention before acquisition
A leaky bucket grows slower with more water. Before adding any new acquisition channel:
- Plot week-1 and week-4 retention.
- If week-4 retention < 20%, do not scale acquisition. Fix activation/onboarding first.
- Identify the top 3 reasons inactive users gave (or you suspect) for not returning. Fix the top one first.
- If retention is healthy (≥30% at week-4), proceed to Pillar 2.
Pillar 2 — Compress what already worked
Look at the first 100. Where did they actually come from?
- Tag each of the 100 with one acquisition source.
- Sort by source. Take the top source.
- Ask: what made it work? Was it the channel itself, the message, the timing, or the founder's personal voice?
- Codify the answer with
/processize— now is the right time, you have ~12+ manual reps. - The output is a documented playbook for that single source. Run it deliberately, with light AI assist, until it plateaus.
Pillar 3 — Add ONE new channel deliberately
Only when Pillar 2 plateaus (≥4 weeks of flat or declining yield):
- Pick exactly one new channel. Not two. Not "a content stack."
- Define a 30-day experiment with a single primary metric (active users from this channel by day 30).
- Cap the budget. If money is involved, set a hard ceiling and a circuit breaker.
- After 30 days: keep, kill, or extend by another 30 days. Never default-renew.
Pillar 4 — Founder bandwidth check
Run this weekly during scaling:
| Signal | Threshold |
| Hours per week on the product | < 50 |
| Manual user-touchpoints per week | < 3h |
| Days since last full day off | < 14 |
| Days since last conversation with a real user | < 7 |
If any signal trips, scaling stops until it's fixed. A burned founder kills more startups than slow growth.
Channels, in rough efficiency order
Order is the median for a B2B / B2C-prosumer SaaS in early stage. Adjust to context.
| Tier | Channel | Cost | Compounding | Best when |
| 1 | Word-of-mouth (NPS-driven invite) | ~0 | Yes | Strong activation, real value moments |
| 1 | Niche community presence | low | Yes | Persona is concentrated in <5 communities |
| 2 | Long-form content (1 channel) | low | Yes | Founder writes/records well; problem is narratable |
| 2 | Cold outreach (handcrafted, < 20/day) | low | No | Persona is on LinkedIn / X with searchable filters |
| 3 | Programmatic SEO | medium | Yes (slow) | Repeatable structured pages, query volume validated |
| 3 | Newsletter sponsorship in niche newsletters | medium | No | First channel hit a ceiling; AOV is high enough |
| 4 | Paid ads (Google, Meta, X) | high | No | Retention proven, channels above hit a ceiling, finance allows runway burn |
| 4 | Influencer placement | high | Mixed | Persona is parasocial; founder won't appear themselves |
Always exhaust Tier 1 before Tier 2. Always exhaust Tier 2 before Tier 3. Never skip to Tier 4 without a written justification reviewed via /multi-ai-review.
Hard rules
- No new paid channel without
usage-monitorrunning. Cost surprise = death. - No vanity metrics in the dashboard. Track active users, not signups. Track retention, not impressions.
- No "agência de growth" before 1k MRR or 1k active users, whichever comes first. Founder owns growth in this phase.
- Cap automated outreach at 50/day, even after
/processize. Past that, deliverability and reputation collapse. - Any pricing or packaging change triggers
business-plan-impact-review.
Output format
Generate docs/business/growth-plan-<YYYY-MM>.md:
# Growth Plan — <month>
**Active users (start of month):** <n>
**Week-4 retention:** <%>
**Top acquisition source last 30d:** <source> (<n> users)
**Founder bandwidth signals:** <green / yellow / red>
## Pillar 1 — Retention diagnosis
- Week-1 retention: <%>
- Week-4 retention: <%>
- Top 3 churn reasons: ...
- Action this month: ...
## Pillar 2 — Compress what worked
- Source: <source>
- Codified playbook: <link to docs/processes/...>
- Yield trend: ...
## Pillar 3 — New channel experiment (if any)
- Channel: <single channel>
- Hypothesis: ...
- Primary metric: ...
- Budget cap: ...
- 30-day decision date: <YYYY-MM-DD>
## Pillar 4 — Founder bandwidth
- Hours/week on product: ...
- Manual touchpoints/week: ...
- Days since full day off: ...
- Days since last user conversation: ...
## Hard rules check
- [ ] usage-monitor running
- [ ] Dashboard tracks active users + retention (not signups + impressions)
- [ ] No paid channel without justification + `/multi-ai-review`
## Decisions for next month
- ...Cross-references
- Principle:
ETHOS.mditem 14. - Predecessor skill:
first-100-users. - Pairs with:
processize,usage-monitor,cost-watchdog,business-plan-impact-review. - Inspired by:
docs/registry/packs/slavingia-skills.md,docs/registry/packs/gstack.md.
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.

