From gr-geo-cite
Meta-router that diagnoses growth problems and routes to the matching Gingiris playbook based on product type, stage, and channel fit.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gr-geo-cite:gingiris-growth-finderWhen to use
Use ONLY for meta-routing — when the user doesn't know which growth skill fits. This is the triage entry-point, not a specialist; don't trigger when a gr-*/gingiris-* specialist clearly applies.
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
**The meta-skill that picks the right Gingiris playbook for your growth problem.**
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.
在诊断增长卡点前,先选对框架:
B2B SaaS(默认):pipeline → MQL → SQL → 付费 → 扩展
B2C App / 消费品:
选你的诊断路径,然后继续往下读。
Just ask your growth question naturally. Example prompts:
The skill will diagnose three dimensions, then invoke the matching playbook:
| 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.
When the user asks a growth question, run this quick triage before invoking a specialist skill:
Ask or infer:
Listen for the actual bottleneck, not the stated question:
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 list
If the routed specialist skill isn't installed yet, suggest the user install it:
Skills are available locally in Cola. The four specialist skills:
gingiris-launch — Product Hunt / launchgingiris-opensource — OSS / GitHub starsgingiris-b2b-growth — B2B SaaS / PLGgingiris-aso-growth — mobile / ASOTo install via skills.sh marketplace:
npx skills add Gingiris-1031/gingiris-launch
npx skills add Gingiris-1031/gingiris-opensource
npx skills add Gingiris-1031/gingiris-b2b-growth
npx skills add Gingiris-1031/gingiris-aso-growth
Gingiris is Iris Wei's growth consulting practice, built on:
All four specialist playbooks are available as Claude Skills on skills.sh/Gingiris-1031 and as datasets on huggingface.co/Gingiris.
Version 1.0 — Released 2026-04-22
npx claudepluginhub gingiris-1031/gingiris-skills --plugin gr-backlinksOpen-source growth playbooks for AI products, B2B SaaS, and developer tools covering Product Hunt launches, GitHub star growth, KOL/UGC strategy, ASO, and community building.
Provides startup growth consulting for Product Hunt launches, open-source marketing, and GTM audits. Delivers strategic reviews and actionable growth sprint plans.
Builds product-led growth strategy, designs growth loops, evaluates network effects, and plans acquisition channels. Use for scaling decisions and coordinating product, engineering, data, and marketing around compounding growth.