gingiris-growth-finder
Skill2 starsChanged 7 months agoMITView on GitHub
🇺🇸 Gingiris Growth Finder — Meta-router that diagnoses growth problems and invokes the right playbook. Auto-triggers on any growth question: Product Hunt launch, GitHub stars, B2B SaaS PLG, ASO, app cold start, KOL outreach, OSS marketing, GTM strategy, customer acquisition, retention, PMF validation, virality. Routes to the matching Gingiris playbook skill (launch / opensource / b2b-growth / aso-growth) based on product type, stage, and channel fit. Use whenever the user asks "how do I grow X" or "how do I launch X" — this skill picks the right specialist.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- Gingiris-1031/gingiris-skillsedited, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- Gingiris-1031/gingiris-skills★ 8930% same
Wrote their own version · 0
None found.
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.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 49
If the question spans multiple domains (e.g.
- Distinctive: line 55
When the user asks a growth question, run this quick triage before invoking a specialist skill:
- Distinctive: line 106
If the routed specialist skill isn't installed yet, suggest the user install it:
- Very specific: line 141
All four specialist playbooks are open source on GitHub under github.com/Gingiris and available as Claude Skills on skills.sh/Gingiris.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Gingiris Growth Finder
The meta-skill that picks the right Gingiris playbook for your growth problem.
Growth questions look similar but require wildly different playbooks. "How do I launch?" for a dev tool is nothing like "How do I launch?" for a mobile app. "How do I grow?" at $1M ARR is nothing like "How do I grow?" at 100 DAU. This skill diagnoses the situation and invokes the specialist.
How to use
Just ask your growth question naturally. Example prompts:
- "I'm launching my AI SaaS next week — what should I prioritize?"
- "My open source project has 2k stars, how do I get to 10k?"
- "I have a B2B SaaS at $300k ARR, should I hire SDRs?"
- "My iOS app isn't ranking for its main keyword, what do I do?"
The skill will diagnose three dimensions, then invoke the matching playbook:
- Product type — SaaS / open source / mobile app / consumer web / marketplace / dev tool
- Growth stage — pre-launch / launch / post-launch cold start / growth / scale
- Primary channel gap — content / community / paid / partnerships / product-led
Diagnostic routing logic
| If the user's question is about... | Route to |
| Product Hunt launch, hunter outreach, launch-day tactics, viral moment engineering | gingiris-launch |
| GitHub stars, HackerNews, OSS marketing, developer community, awesome-lists, Show HN | gingiris-opensource |
| B2B SaaS, PLG vs SLG, PMF validation, freemium, enterprise motion, affiliate, channel partnerships | gingiris-b2b-growth |
| ASO, App Store / Google Play, mobile user acquisition, TikTok/Reels/Shorts UGC, creator matrix | gingiris-aso-growth |
If the question spans multiple domains (e.g. "I have an open source project that I want to monetize as B2B SaaS"), route to both relevant skills and explain the handoff.
Decision framework (for the agent)
When the user asks a growth question, run this quick triage before invoking a specialist skill:
Step 1 — Classify the product
Ask or infer:
- What is it? (SaaS web app / mobile app / OSS project / marketplace / browser extension)
- Who's the ICP? (individual developer / SMB / enterprise / consumer)
- Distribution default? (self-serve web signup / app store / GitHub / sales-led)
Step 2 — Identify the stage
- Pre-launch — building, no users yet
- Launch — within 30 days of public release
- Cold start — launched but <100 WAU/DAU, <1k signups
- Growth — steady signal, scaling what works
- Scale — $1M+ ARR or 10k+ DAU, needs systems
Step 3 — Spot the gap
Listen for the actual bottleneck, not the stated question:
- "I'm not getting signups" → distribution channel gap
- "I'm getting signups but no conversions" → product/pricing gap (not growth — redirect)
- "I have users but no growth loop" → retention/virality gap
- "I have a growth loop but can't scale ads" → monetization gap
Step 4 — Route
Invoke the specialist skill. Examples:
User: "I have a dev tool CLI with 500 GitHub stars. How do I get to 5k?"
→ Diagnosis: OSS project, growth stage, distribution gap
→ Invoke: gingiris-opensource
→ Context hint: focus on GitHub trending + HN relaunch + awesome-lists
User: "My iOS photo app has 80 DAU after 2 months. What's wrong?"
→ Diagnosis: mobile app, cold-start stage, distribution+UGC gap
→ Invoke: gingiris-aso-growth
→ Context hint: focus on ASO audit first, then TikTok creator matrix
User: "I'm launching an AI coding assistant on Product Hunt in 3 weeks."
→ Diagnosis: dev tool, pre-launch, launch-day engineering needed
→ Invoke: gingiris-launch
→ Context hint: 3-week timeline → hunter network + pre-launch email listComplementary install
If the routed specialist skill isn't installed yet, suggest the user install it:
npx skills add Gingiris/gingiris-launch # for Product Hunt / launch
npx skills add Gingiris/gingiris-opensource # for OSS / GitHub stars
npx skills add Gingiris/gingiris-b2b-growth # for B2B SaaS / PLG
npx skills add Gingiris/gingiris-aso-growth # for mobile / ASOOr install all four at once:
npx skills add Gingiris/gingiris-launch -g
npx skills add Gingiris/gingiris-opensource -g
npx skills add Gingiris/gingiris-b2b-growth -g
npx skills add Gingiris/gingiris-aso-growth -gWhat this skill does not do
- Product/pricing advice — if the bottleneck is product fit or pricing, say so explicitly and redirect to a product strategist (this skill only routes growth questions)
- Paid ads tactical execution — covered at a high level in gingiris-b2b-growth and gingiris-aso-growth, but not the primary focus
- Fundraising / pitch deck — out of scope
About Gingiris
Gingiris is Iris Wei's growth consulting practice, built on:
- 6 years as cofounder/COO of AFFiNE (60k+ GitHub stars)
- 30x #1 on Product Hunt (Manus, Devin, AFFiNE, and others)
- 150+ AI startups advised on global go-to-market
All four specialist playbooks are open source on GitHub under github.com/Gingiris and available as Claude Skills on skills.sh/Gingiris.
Version 1.0 — Released 2026-04-22
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.

